| # github.com/rafi i3status config | |
| # i3status configuration file | |
| # see "man i3status" for documentation. | |
| # It is important that this file is edited as UTF-8. | |
| # The following line should contain a sharp s: | |
| # ß | |
| # If the above line is not correctly displayed, fix your editor first! |
| Code | Message | Description |
|---|---|---|
| 100 | Continue | The server has received the request headers, and the client should proceed to send the request body |
| 101 | Switching Protocols | The requester has asked the server to switch protocols |
| 103 | Checkpoint | Used in the resumable requests proposal to resume aborted PUT or POST requests |
| Code | Message | Description |
|---|
Services declared as oneshot are expected to take some action and exit immediatelly (thus, they are not really services,
no running processes remain). A common pattern for these type of service is to be defined by a setup and a teardown action.
Let's create a example foo service that when started creates a file, and when stopped it deletes it.
Create executable file /opt/foo/setup-foo.sh:
So, with credit to the Factorio wiki and cbednarski's helpful gist, I managed to eventually setup a Factorio headless server. Although, I thought the process could be nailed down/simplified to be a bit more 'tutorialised' and also to document how I got it all working for my future records.
The specific distro/version I'm using for this guide being Ubuntu Server 16.04.1 LTS. Although, that shouldn't matter, as long as your distro supports systemd (just for this guide, not a Factorio headless requirement, although most distros use it as standard now).
The version of Factorio I shall be using is 0.14.20, although should work for any version of Factorio 0.14.12 and higher.
If you prefer a simple, automated setup, [Bisa has a really handy init script that will do most of the work for
| #!/usr/bin/env bash | |
| MCU=atmega32u4 | |
| if grep -q -s Microsoft /proc/version; then | |
| echo 'ERROR: Pro Micros can not be flashed within the Windows Subsystem for Linux (WSL) currently. Instead, take the .hex file generated and flash it using AVRDUDE, AVRDUDESS, or XLoader.' | |
| exit 1 | |
| fi | |
| if [ "$#" -ne 1 ]; then |
The following sample codes are not valid for the listed services but should allow basic testing of an authenticator application. Clicking on a QR code image will display just that code so it is easier to scan without interference from the other codes.
You can use this site to generate more QR codes as needed. It will also let you verify the produced codes against its own calculated code.
