1. Install nginx
2. Install minio
3. Install mc client
- Add Minio
mc config host add <ALIAS> <YOUR-S3-ENDPOINT> <YOUR-ACCESS-KEY> <YOUR-SECRET-KEY>
mc config host list
.table-view-table { | |
width: 100%; | |
} | |
.table-view-table td:not(:first-child) { | |
white-space: nowrap; | |
} | |
.table-view-table tr td:first-child, tr th:first-child { | |
overflow: hidden; |
I started with a basic Ubuntu 22.10 installation, where I chose in the installer to use ZFS as my volume manager.
I wanted to encrypt my home folder.
I followed the article (and comments, including Christoph Hagemann's) from:
https://talldanestale.dk/2020/04/06/zfs-and-homedir-encryption/
To achieve:
pages: | |
image: ghcr.io/pengx17/logseq-base:master | |
stage: deploy | |
script: | |
- mkdir public | |
- mv publish.mjs /home/logseq/publish.mjs | |
- cd /home/logseq | |
- "xvfb-run node /home/logseq/publish.mjs -p $CI_PROJECT_DIR -t $CI_PROJECT_DIR/public/build_trace.txt -o $CI_PROJECT_DIR/public" | |
artifacts: | |
paths: |
permissions: | |
contents: 'read' | |
id-token: 'write' | |
steps: | |
- name: Checkout | |
uses: actions/checkout@v2 | |
- id: auth | |
uses: google-github-actions/[email protected] |
python3 main.py data.json
import { serve } from "https://deno.land/[email protected]/http/server.ts"; | |
serve(async (request) => { | |
const worker = new Worker(new URL("./worker.ts", import.meta.url).href, { | |
type: "module", | |
name: "worker-" + (100 * Math.random()).toFixed(), | |
}); | |
const data = await request.json(); |
This is an example guide how to deploy Authentik with Traefik in forward auth proxy mode - that means that any application behind the proxy will be automatically authenticated by Traefik. This allows better reuse of code and completely moves user management to Traefik & Authentik.
In this guide we use custom DNS to make the requests nicer and to show that it works with DNS. So step #1 is to put following records to
your /etc/hosts
(for example by sudo nano /etc/hosts
and adding these values)
Start by checking that there aren't any previous ssh keys inside the FIDO2 authenticator of your YubiKey. You can check if they exist by running the command below:
nix shell nixpkgs#yubikey-manager -c ykman fido credentials list
If the command above outputs a string mentioning "ssh" or "openssh", then you have already got a key generated and store on your YubiKey.
Before generating a new ssh key to store on your YubiKey you must consider which additional required authentication factors you want to use. Below you can see a table with the available factors and their corresponding command:
# You need to set PROVIDERS_GOOGLE_CLIENT_ID, PROVIDERS_GOOGLE_CLIENT_SECRET, | |
# and to set DOMAIN and EMAIL in environment | |
# (e.g. DOMAIN=selfhosted.example.com [email protected] docker compose up) | |
# The EMAIL will be used in a letsencrypt certificate, and will be the only user able to log in initially. | |
version: '3' | |
services: | |
reverse-proxy: | |
# Use Traefik for routing and certificate handling. |