ambientlight

#!/bin/bash
echo "Creating a GPT partition on /dev/sda1"
echo -e "g\nn\n\n\n\nw" | fdisk /dev/sda

# In case you might want to create a DOS partition instead. It doesn't really matter.
#echo "Creating a DOS partition on /dev/sda1"
#echo -e "o\nn\np\n1\n\n\nw" | fdisk /dev/sda

echo "Formatting /dev/sda1 to ext4"
mkfs -t ext4 /dev/sda1

ambientlight

#!/bin/bash

if [[ -z $1 ]] ; then 
  echo "Missing swagger readme search path, usage: ./gen_all.sh SEARCH_PATH"
  echo 'Sample: ./gen_all.sh "specification/maps/data-plane/Render/readme.md"'
  exit 0
else 
  SEARCH_PATH=$1
fi

ambientlight

import React, { memo, useMemo, useState } from 'react';
import {
  AzureMap,
  AzureMapDataSourceProvider,
  AzureMapFeature,
  AzureMapLayerProvider,
  AzureMapsProvider,
  IAzureMapOptions,
  AzureMapPopup,
  IAzureMapFeature

ambientlight

import React, { memo, useContext, useEffect, useMemo, useState } from 'react';
import {
  AzureMap,
  AzureMapDataSourceProvider,
  AzureMapFeature,
  AzureMapLayerProvider,
  AzureMapsProvider,
  IAzureMapOptions,
  AzureMapPopup,
  IAzureMapFeature,

ambientlight

#!/bin/bash

if [[ -z $1 ]] ; then 
  echo "Resource path is required"
  exit 1
fi

RESOURCE=$1
# azure maps primary subscription key
SUBSCRIPTION_KEY=YOUR_KEY

ambientlight

RFC: Organic backend architecture for offline-first application via logux

Goal

Lay out the base ground-work for distributed backend system architecture designed to support offline usecases that involve synchronization of client application during the events when client applications are offline for a periods that exceed days or weeks. Additionally the architecture is meant to support easy-to-replicate offline servers, which act as ad-hoc (edge) synchronization endpoints that are capable of supporting a full range of available business-specific functionality, thus making clients unaware of unexisting internet connectivity between ad-hoc and cloud-hosted server.

Non-goal

This RFC is not meant to describe any application-specific business logic (another one for this) such as features provided by solution hosted in such backend system, entity-relationship diagrams modeled in DBs etc.

Basis

The base area of exploration / experimentation lies around Logux which conceptually can

ambientlight

var appState = 0
let reducer: (Int, Int) -> Int = { (sum, increment) in sum + increment };

class CounterViewController: UIViewController {
    @IBOutlet var inputField: UITextField!
    @IBOutlet var addButton: UIButton!
    @IBOutlet var sumLabel: UILabel!
    @IBAction func addButtonPressed(_ sender: UIButton) {
        appState = reducer(appState, Int(self.inputField.text!)!)
        self.sumLabel.text = "\(appState)"

ambientlight

let nums = [1, 2, 3, 6, 16, 4]
let reducer: (Int, Int) -> Int = { (sum, increment) in 
  sum + increment
}

let sum = nums.reduce(0, reducer);

ambientlight

let nums = [1, 2, 3, 6, 16, 4]
let accumulator: (Int, Int) -> Int = { (sum, increment) in 
  sum + increment
}

var sum = 0
for var i in (0..<nums.count) {
  sum = accumulator(sum, nums[i])
}

ambientlight

let nums = [1, 2, 3, 6, 16, 4]

var sum = 0
for var i in (0..<nums.count) {
  sum += nums[i]
}