Test-Driven Development workflow for implementing features with confidence.
Philosophy: Use unit tests to express requirements, then implement to satisfy them.
| # https://github.com/tizbac/pmoxs3backuproxy | |
| name: pmoxs3backuproxy | |
| services: | |
| pmoxs3backuproxy: | |
| image: ghcr.io/tizbac/pmoxs3backuproxy:latest | |
| command: -bind 0.0.0.0:8007 -endpoint s3.us-west-001.backblazeb2.com -usessl --debug | |
| container_name: pmoxs3backuproxy | |
| hostname: pmoxs3backuproxy | |
| restart: unless-stopped |
| export PBS_HOST="10.69.4.20" | |
| export PBS_PORT="8007" | |
| export PBS_USERNAME="root@pam" | |
| export PBS_PASSWORD="totallymyrealpassword" | |
| export PBS_DATASTORE="tank" | |
| export PBS_NAMESPACE="backups" | |
| export PBS_FINGERPRINT="fi:ng:er:pr:in:ts:ar:en:ts:ec:re:tb:ut:im:ch:an:gi:ng:it:an:yw:ay" | |
| export PBS_REPOSITORY="${PBS_USERNAME}@${PBS_HOST}:${PBS_PORT}:${PBS_DATASTORE}" |
| Create a modern, responsive to-do list web application with the following specifications: | |
| 1. Core Functionality: | |
| - Add, edit, delete, and mark tasks as complete | |
| - Categorize tasks with customizable labels, Color and emoji | |
| - Set due dates and priority levels | |
| - Filter and sort tasks by status, date, and category | |
| - Data persistence using local storage | |
| - Show statistics |
Helpful links:
We need all machines up and running. At first we will setup the loadbalancer.
| #!/bin/bash | |
| # taken from https://tailscale.com/kb/1133/proxmox | |
| NAME="$(tailscale status --json | jq '.Self.DNSName | .[:-1]' -r)" | |
| tailscale cert "${NAME}" | |
| pvenode cert set "${NAME}.crt" "${NAME}.key" --force --restart |
In the interest of complete transparency, if you follow this guide, there’s a very minuscule but non-zero chance that you may violate the Bekenstein bound, at which the resulting black hole may swallow the earth whole. You have been warned!
Find the proper driver at the NVidia website.
Note: Make sure to select "Linux 64-bit" as your OS
Hit the "Search" button.
This guide aims to take a look at a distributed, scalable SeaweedFS as a backend storage for an OwnCloud server. Why not NextCloud? Because NextCloud's S3 connector is outdated and not maintained, and won't work with SeaweedFS. Both OwnCloud and NextCloud have the same support and the same plugins. The only concern anyone has is some weird split that happened between the two years ago. It's fine.
This was a giant pain in the ass, but eventually I got it working. This is how.
All servers start from fresh, clean installs of Ubuntu 18.04.3
This guide will use three seperate boxes (one master/OwnCloud and two slaves). I'm assuming there's spare, unformatted disks attached to the slaves. If not, ignore or change the section on mounting to fit your needs.
This is an opinionated handbook on how I migrated all my Rails apps off the cloud and into VPS.
This is how I manage real production loads for my Rails apps. It assumes: