shoe-string-server
ansible-eksctl
shoe-string-server | ansible-eksctl | |
---|---|---|
4 | 1 | |
13 | 3 | |
- | - | |
4.3 | 5.8 | |
7 months ago | 8 days ago | |
JavaScript | Shell | |
MIT License | MIT License |
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.
shoe-string-server
-
My deployment platform is a shell script
I have a very similar system[1] for my personal projects, only I use GitHub actions to push a docker image to ECR and a commit to a config repo bumping the tag. I then have a cronjob to pull the config repo and reconcile using docker compose.
I wouldn't use it for serious stuff, but it's been working great for my random personal projects (biggest gap is if something crashes it'll stay crashed until manual intervention currently)
- [1] https://github.com/mnahkies/shoe-string-server/pull/2
-
Majority of web apps could just run on a single server
For my personal stuff that doesn't get any traffic I cobbled together some scripts to manage containers / SSL here https://github.com/mnahkies/shoe-string-server
I don't think I ever got around to making it self healing if a container dies, but it does support gitops style deployments through a cronjob / conf repo similar to argocd
It's been running happily on a <$10 / month aws lightsail instance for a few years now, though tbh I'd still reach for k8s for anything serious
-
Harbormaster: The anti-Kubernetes for your personal server
Interestingly this seems like a pretty popular problem to solve.
I made a similar thing recently as well, although with the goal to handle ingress and monitoring out the box as well, whilst still able to run comfortably on a small box.
I took a fairly similar approach, leveraging docker-compose files, and using a single data directory for ease of backup (although it's on my to-do list to split out conf/data).
If there was a way to get a truly slim and easy to setup k8s compatible environment I'd probably prefer that, but I couldn't find anything that wouldn't eat most of my small servers ram
https://github.com/mnahkies/shoe-string-server if you're interested
- Show HN: Shoe String Server
ansible-eksctl
-
My deployment platform is a shell script
- a few desktop files, they come with my dotfiles git repo, no need to "declare them"
Also Ansible is probably the worst example as it is an half assed declarative language that doesn't even encourage idempotence. Basically it is made by and for old unix guys who want to continue writing sequencial scripts the old and crappy way while pretending they do things in a modern way. And it is the reason it has become so popular against cfengine, puppet, chef and salt. I don't see the point of using ansible if it is to have the same low standard of quality as plain old scripts and my experience working with teams using ansible has only reinforced my view that this language is for people who like to do things the dirtiest way.
[1] https://github.com/andrewrothstein/ansible-eksctl/tree/main
What are some alternatives?
watchtower - A process for automating Docker container base image updates.
hcl - HCL is the HashiCorp configuration language.
dokku-scheduler-nomad - Scheduler plugin for deploying applications to nomad
hashi-ui - A modern user interface for @hashicorp Consul & Nomad
harbormaster
git-pipe - Hassle-free minimal CI/CD for git repositories with docker or docker-compose projects.
https-portal - A fully automated HTTPS server powered by Nginx, Let's Encrypt and Docker.
docker-box - A lightweight docker application platform for single servers.