inkletblot/simple-blog-api
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

updated all code formatting

Browse Source
This commit is contained in:
Solomon Laing 2021-12-21 20:36:28 +10:30
parent e4e1283466
commit 1f80db82f4
2 changed files with 106 additions and 131 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
posts/2021-07-28_work-related_Icons SVGs Fonts and Icomoon.md
View File

@ -14,7 +14,7 @@ I noticed the use of some clever CSS/font work, creating a tag and prepending it
The basics of the solution are below.
```scss
#!scss
@charset "UTF-8";
@font-face {
font-family: "icomoon";
@ -48,13 +48,10 @@ The basics of the solution are below.
.my-icons-icon-2:before {
content: "";
}
```
Then to insert the icon where it is wanted one can simply do the following
```html
<i class="my-icons-icon-1"></i>
```
`<i class="my-icons-icon-1"></i>`
And the icon specified as content in the scss above will sit in the place of the `<i>` tag.
@ -72,10 +69,6 @@ And with that, I had found our solution.
Icomoon is really a magical black box but what it produces is brilliant.
```
detail in long how solution works
```
Source controlling the processed files and building the font and css into an npm package that we store in a private registry worked great and we have been using the same solution since, approx. 8 months I think. If ever you need a simple way of producing your own set of easily usable icons for a project, I suggest Icomoon.
-ink.

46
posts/2021-08-09_servers_K3s on Odroid MC1s, a Guide.md
View File

@ -30,7 +30,7 @@ Both network and hostname can be setup by mounting rootfs and manually editing/a
Example netplan '10-config.yaml':
```yaml
#!yaml
network:
version: 2
renderer: networkd
@ -41,13 +41,10 @@ Example netplan '10-config.yaml':
nameservers:
addresses: [192.168.0.1, 1.1.1.1]
search: [mydomain]
```
Also set timezone if you want.
```shell
sudo timedatectl set-timezone Australia/Adelaide
```
`sudo timedatectl set-timezone Australia/Adelaide`
In my case the following was used:
@ -64,15 +61,13 @@ We must rebuild kernel with updated options so that cgroup_pids is enabled. Hard
note that the following tools are required for the build: bison, flex, libssl-dev, and bc
```shell
apt install bison flex libssl-dev bc -y
```
`apt install bison flex libssl-dev bc -y`
### The K3S install
Run the following on all nodes:
```shell
#!shell
iptables -F \
&& update-alternatives --set iptables /usr/sbin/iptables-legacy \
&& update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy \
@ -88,11 +83,10 @@ Run the following on all nodes:
# Be sure that the firewall is disabled for ease
ufw disable
```
Then run the following only on the master node:
```shell
#!shell
# for master
curl -sfL https://get.k3s.io | K3S_KUBECONFIG_MODE="644" sh -s - --docker
@ -102,24 +96,21 @@ Then run the following only on the master node:
# Get token from master, make sure to store it somewhere
cat /var/lib/rancher/k3s/server/node-token
```
Then run the following on the worker nodes, updating the command for each:
```shell
#!shell
# for workers
# Fill this out ...
curl -sfL http://get.k3s.io | K3S_URL=https://<master_IP>:6443 K3S_TOKEN=<join_token> K3S_NODE_NAME="odroid-mc1-X" sh -s - --docker
systemctl status k3s-agent
```
And thus you should be done, check the master node to see:
```shell
#!shell
# Check node was added on master
kubectl get nodes
```
And all should be up and running correctly, it was for me at least.
@ -137,7 +128,7 @@ Once these have been set up with ip addresses and hostnames (odroid-n2, odroid-m
Either the following to set up users and access:
```yml
#!yml
- hosts: all
become: yes
tasks:
@ -154,11 +145,11 @@ Either the following to set up users and access:
authorized_key: user=kuber key="{{item}}"
with_file:
- ~/.ssh/id_rsa.pub
```
Or if you already set up users:
```yml
#!yml
- hosts: all
become: yes
tasks:
@ -166,11 +157,9 @@ Or if you already set up users:
authorized_key: user=root key="{{item}}"
with_file:
- ~/.ssh/id_rsa.pub
```
The above can be used with a hosts file such as the following
```
[masters]
master ansible_host=192.168.0.XXX ansible_user=<user> ansible_ssh_pass=<password>
@ -181,30 +170,24 @@ The above can be used with a hosts file such as the following
[all:vars]
ansible_python_interpreter=/usr/bin/python3
```
Then the following commands:
```shell
#!shell
sudo iptables -F \
&& sudo update-alternatives --set iptables /usr/sbin/iptables-legacy \
&& sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy \
&& sudo reboot
```
useful command formatted from step 2.2.1 of reference material [here](https://learn.networkchuck.com/courses/take/ad-free-youtube-videos/lessons/26093614-i-built-a-raspberry-pi-super-computer-ft-kubernetes-k3s-cluster-w-rancher)
Then the following on the master node:
```shell
curl -sfL https://get.k3s.io | K3S_KUBECONFIG_MODE="644" sh -s -
```
`curl -sfL https://get.k3s.io | K3S_KUBECONFIG_MODE="644" sh -s -`
Then on the master node grab its node token
```shell
sudo cat /var/lib/rancher/k3s/server/node-token
```
`sudo cat /var/lib/rancher/k3s/server/node-token`
Then run the following on each of the workers:
(note in my case curl was not installed)
@ -215,11 +198,10 @@ YOURTOKEN = token from above
servername = unique name for node (I use hostname)
```shell
#!shell
curl -sfL https://get.k3s.io | K3S_TOKEN="YOURTOKEN" K3S_URL="https://[your server]:6443" K3S_NODE_NAME="servername" sh -z
# I used
apt install curl -y && curl -sfL https://get.k3s.io | K3S_TOKEN="YOURTOKEN" K3S_URL="https://[your server]:6443" K3S_NODE_NAME="servername" sh -z
```
Sadly this is where my notes ended as, although the install worked, all of the system pods were failing and thus I moved on to the method listed above.