docker-volume-backup
runlike
docker-volume-backup | runlike | |
---|---|---|
3 | 14 | |
584 | 1,810 | |
- | - | |
4.1 | 0.0 | |
9 months ago | about 1 year ago | |
Shell | Python | |
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.
docker-volume-backup
-
Self-hosted app resiliency with focus on docker imgs
I was having a hard time with this myself until I came across this. Hope this points you in the right direction. I use Veeam to back up my host. The backup utility I use for my persistent Docker volumes.
-
Vaultwarden backup
this might help
-
Self-Hosting Dozens of Web Applications and Services on a Single Server
Echoing the sentiment here, this is a great way to host smaller projects on the cheap, without adding the complexity/price of k8s, Nomad et al!
I do the same, and have spent some time automating the backup of such a set of standalone containers [0], in case others also find it useful.
[0] https://github.com/jareware/docker-volume-backup
runlike
-
Pharo 11
You can use this tool to figure out how to run again any currently running container https://github.com/lavie/runlike
- [Help] Change Directory Bindings for a "--restart=always" Container
- View the commands used to create a docker container
- FLiP Stack Weekly 28 Jan 2023
- FLiP Stack Weekly 28-Jan-2023
-
Runlike: Given an existing Docker container, prints the command line to run it
Issue for podman support: https://github.com/lavie/runlike/issues/71
-
Self-Hosting Dozens of Web Applications and Services on a Single Server
I had started out the same way, especially if it was a new app and I wasn't familiar with how I really wanted to run it. Some containers expect a fair number of environment variables and multiple mounts. Once I got everything working, I would create a script /svcs with the corresponding docker run command. There's even a cool tool called "runlike" which can create a well formatted command for any running container.
https://github.com/lavie/runlike/
But I've got those migrated to docker-compose files these days and I try to start with the docker-compose file instead of going directly into testing out docker run commands.
What are some alternatives?
crowdsec - CrowdSec - the open-source and participative security solution offering crowdsourced protection against malicious IPs and access to the most advanced real-world CTI.
docker-autocompose - Generate a docker-compose yaml definition from a running container
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
docker-qnap-pushover - Pushover notifications for QNAP NAS system events 🔔
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
Docker Compose - Define and run multi-container applications with Docker
yunohost - YunoHost is an operating system aiming to simplify as much as possible the administration of a server. This repository corresponds to the core code, written mostly in Python and Bash.
carbonyl - Chromium running inside your terminal
cert-manager - Automatically provision and manage TLS certificates in Kubernetes
SirTunnel - Minimal, self-hosted, 0-config alternative to ngrok. Caddy+OpenSSH+50 lines of Python.
piku - The tiniest PaaS you've ever seen. Piku allows you to do git push deployments to your own servers.
streamnative-rest-stocks