This is a story about how I tried to use Go for scripting. In this story, I’ll discuss the need for a Go script, how we would expect it to behave and the possible implementations; During the discussion I’ll deep dive to scripts, shells, and shebangs. Finally, we’ll discuss solutions that will make Go scripts work.
While python and bash are popular scripting languages, C, C++ and Java are not used for scripts at all, and some languages are somewhere in between.
Europe
| $ sudo sysctl net.bridge.bridge-nf-call-iptables=1 | |
| $ sudo sysctl net.bridge.bridge-nf-call-ip6tables=1 |
relates to moby/moby#32507, moby/buildkit#442
Doing some silly experimenting with RUN --mount:
# syntax=docker/dockerfile:1
FROM alpine AS stage1
| # syntax = tonistiigi/dockerfile:runmount20180618 | |
| # | |
| # `RUN --mount` example. Requires Docker v18.06 with `DOCKER_BUILDKIT=1`. | |
| # | |
| # `RUN --mount=... apt install <PKGS>` should finish immediately even when some packages are added to <PKGS> or built with `docker build --no-cache`. | |
| FROM ubuntu | |
| RUN rm -f /etc/apt/apt.conf.d/docker-clean; echo 'Binary::apt::APT::Keep-Downloaded-Packages "true";' > /etc/apt/apt.conf.d/keep-cache | |
| RUN --mount=type=cache,target=/var/cache/apt,sharing=locked --mount=type=cache,target=/var/lib/apt,sharing=locked \ | |
| apt update && apt install -y gcc |
| <?xml version="1.0" encoding="UTF-8"?> | |
| <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> | |
| <fontconfig> | |
| <!-- Add generic family. --> | |
| <match target="pattern"> | |
| <test qual="any" name="family"><string>emoji</string></test> | |
| <edit name="family" mode="assign" binding="same"><string>Noto Color Emoji</string></edit> | |
| </match> |
| Convert PCF and BDF files to bitmap only OpenType (.otb) using fontforge | |
| If you have a new enough fontforge, the python version of this script can | |
| optionally read filenames from standard input, generating multiple .otb | |
| font files as it finds new families. It also handles gzipped PCF and BDF | |
| files. |
| yourhost.com { | |
| redir / https://cloud.yourhost.com 301 | |
| } | |
| cloud.yourhost.com { | |
| tls admin@yourhost.com | |
| header / Strict-Transport-Security "max-age=31536000;" | |
| root /var/www/html | |
| fastcgi / nextcloud:9000 php { | |
| connect_timeout 1h |
ENCRYPTING YOUR DRIVE(S) CAN RESULT IN PERMANENT DATA LOSS IF YOU DON'T KNOW WHAT YOU ARE DOING OR YOU FORGET THE PASSWORD. IT IS YOUR (THE READER'S) RESPONSIBILITY TO HAVE BACKUPS SHOULD ANYTHING GO WRONG. Additionally, I am not responsible for any damage you cause to your system by following this guide. You are completely and solely responsible for any changes made and potential damage caused.
I am not an expert on this topic in any way! I just read some wiki pages, had done a dual-boot Arch install before, got inspired by
Note that is a draft post. NOT checked by the full Routify team yet. Any feedback welcome! (You are looking at a major rewrite, this used to be more about Routify vs Sapper)
We are getting got a lot of questions about how Routify is different than Sapper. Rather than going into long comparisons about the differences with Sapper, I would like to explain the project goals of the Routify and Roxi projects. I hope this will make it clearer where things are going.
Now that we have released Routify 1.5, it's time to talk about Roxi.
In any non-trivial project, there is a need for a project structure. You've got routing, asset pipeline (CSS, images), data handling issues and more to deal with.
