logpaste
s6-overlay
Our great sponsors
logpaste | s6-overlay | |
---|---|---|
8 | 27 | |
310 | 3,515 | |
- | 1.9% | |
6.7 | 4.6 | |
27 days ago | about 1 month ago | |
Go | Shell | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
logpaste
-
Migrating from SQLite to PostgreSQL
FWIW, I've used Litestream on Google Cloud Run and never run into issues, but I haven't pushed it much:
https://github.com/mtlynch/logpaste/blob/master/docs/deploym...
-
PicoShare: A minimalist, easy-to-host service for sharing images and other files
Currently, no. I've implemented that functionality recently in my other tool, LogPaste, so it shouldn't be too hard to reproduce here.
- Log Paste
-
How Litestream Eliminated My Database Server for $0.03/month
My tool is called LogPaste. It allows users to generate shareable URLs for text files. I use it in my open-source KVM over IP device so that users can easily share diagnostic logs with me.
-
LogPaste: A self-hostable pastebin that replicates data to any S3 provider
I designed it with self-hosting in mind, so there are instructions for hosting it under Docker, as well as with several free cloud hosting providers. You can even host the data storage part yourself if you use a solution like Minio.
-
The Architecture of a One-Man SaaS
I still use GCP, but I avoid locking myself into their proprietary infrastructure when I'm writing new stuff. I feel like Google is far too cavalier about deprecating services and forcing their customers to do migration work.
It is hard to replace GCP's managed datastores because I really don't want to maintain my own database server (even if it's a managed service that someone else upgrades for me). So I've stuck to Google Cloud Datastore / Firestore, but I've been experimenting a lot with Litestream[0], and I think that might be my go-to choice in the future instead of proprietary managed datastores.
Litestream continuously streams data from a SQLite database to an S3 backend. It means that you can design your app to use SQLite and then sync the database to any S3 provider. I designed a simple pastebin clone on top of Litestream, and I use it in production for my open source KVM over IP. It's worked great so far, though I'm admittedly putting a pretty gentle workload on it (a handful of requests per day).
[0] https://litestream.io/
[1] https://github.com/mtlynch/logpaste
s6-overlay
- S6-overlay: one *thing* per Docker container
-
Backup Grafana SQLite with Litestream using s6-overlay in a container app
FROM docker.io/grafana/grafana-oss:9.5.12-ubuntu # Set USER to root escalating priviliges to perform installation of litestream and s6-overlay USER root RUN apt-get -qq update && \ apt-get -qq install -y xz-utils \ && rm -rf /var/libs/apt/lists/* # https://github.com/benbjohnson/litestream-s6-example/blob/main/Dockerfile # Download the static build of Litestream directly into the path & make it executable. ADD https://github.com/benbjohnson/litestream/releases/download/v0.3.11/litestream-v0.3.11-linux-amd64.tar.gz /tmp/litestream.tar.gz RUN tar -C / -xvzf /tmp/litestream.tar.gz ARG S6_OVERLAY_VERSION="3.1.5.0" # Download the s6-overlay for process supervision. ADD https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-noarch.tar.xz /tmp RUN tar -C / -Jxpf /tmp/s6-overlay-noarch.tar.xz ADD https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-x86_64.tar.xz /tmp RUN tar -C / -Jxpf /tmp/s6-overlay-x86_64.tar.xz # Copy s6 init & service definitions. COPY etc/s6-overlay /etc/s6-overlay # Copy Litestream configuration file. COPY etc/litestream.yml /etc/litestream.yml # The kill grace time is set to zero because our app handles shutdown through SIGTERM. ENV S6_KILL_GRACETIME=0 # Sync disks is enabled so that data is properly flushed. ENV S6_SYNC_DISKS=1 # Reset USER to 472 to reset the escalated privileges USER 472 # # Run the s6 init process on entry. ENTRYPOINT [ "/init" ]
-
Letme Dockerize for you | share your projects
Learn S6-Overlay that allows to have one docker container for multiple processes... make immich docker compose not a two page 8 containers long? But just one clean container with healthcheck. Convince the devs to switch to it.
-
Code-server : Awesome VS Code container on browser (Useful for Fast Cloud Deploy - Fix Corporate Issues)
Custom base docker image with S6 overlay (for more details : just-containers/s6-overlay)
-
xinetd/inetd/systemd socket services in Docker?
https://github.com/just-containers/s6-overlay can do what you need.
-
Alpine Linux is reducing dependencies on Busybox
Used s6-overlay[1] to start a lot daemons in a docker-image for demo purposes - postgres, tomcat, mysql, php-fpm, apache (don't ask why ;) - s6 worked really well and was reliable and stable - I enjoyed it very much. It was also possible to reliable pass SIGTERM to the daemons in the image for clean shutdown and it was easily possible to configure logging to stdout with a prefix. Modelling dependencies (waiting on database before starting app etc.pp) is possible via shell-scripts. It's super flexible but out of the box it's more like a collection of powerful tools not a complete package - but that's good. It's in the tradition of djb daemontools and is very unix - as in doesn't talk a lot and you better know how each part works but - and that's really cool - it's modular and simple and once you get a grip on it you can easily reason about it. systemd takes a completely different approach and also solves a kind of differnt problem - this is like small pieces of lego that compose well instead of one big chunk of glib/dbus/glibc only c-code.
1: https://github.com/just-containers/s6-overlay
-
Do Docker Containers go thru a Boot Process
Every container has some entrypoint, whether it launches a single binary, runs a "process supervisor" like s6, or does some pre-setup before running a service, like a database.
-
Docker and dedicated user
If you *really* want to make your own containers with PUID/PGID support checkout "S6-overlay" and the linuxserver "baseimage". Somewhere in the startup they end up running:
-
Docker Build Process: Archive Extract onto / (root), overwrites destination directories and contents
FROM ubuntu:20.04 ARG S6_OVERLAY_VERSION=3.1.0.1 ARG DEBIAN_FRONTEND=noninteractive ENV TZ="America/New_York" RUN apt-get update && apt-get install -y xz-utils ADD https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-noarch.tar.xz /tmp RUN tar -C / -Jxpf /tmp/s6-overlay-noarch.tar.xz ADD https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-x86_64.tar.xz /tmp RUN tar -C / -Jxpf /tmp/s6-overlay-x86_64.tar.xz RUN apt-get autoclean && rm -rf /tmp/* ENTRYPOINT ["/init"]
-
Starting a service in Dockerfile
Not sure about unbound or what have inside the pihole base image, you may try to run the service in foreground or use some tiny init service for that container (I just learnt that s6 may work for that, but you must be aware how it should be used)
What are some alternatives?
tinypilot - Use your Raspberry Pi as a browser-based KVM.
docker-php-nginx - Docker image with PHP-FPM 8.3 & Nginx 1.24 on Alpine Linux
litestream - Streaming replication for SQLite.
docker-restic-cron - Automated Restic backups from Docker
node-pg-migrate - Node.js database migration management for Postgresql
laravel-docker-production
pomf - Pomf is a simple lightweight file host with support for drop, paste, click and API uploading.
docker
picoshare - A minimalist, easy-to-host service for sharing images and other files
k3s - Lightweight Kubernetes
flyctl - Command line tools for fly.io services