51–60 of 82 posts
[1] https://dokku.com/ - Heroku but self-hosted, deceptively complex, can be a pain
[2] https://vercel.com/ - Kind of a modern replacement, very easy, but can only really run TS/JS
[3] https://cloud.google.com/run - A nice way to run any server in a Docker container, simple but probably not suitable for a front-end
Docker containers get built with github actions and pushed to docker hub
I’ve occasionally looked into cloud stuff, but it all seems orders-of-magnitude more expensive for day-to-day use, and there’s no cost ceiling if I do something dumb and use a ton of bandwidth
Bare metal server, each side-project lives in a docker container, Traefik is set to reverse-proxy .shish.io" rel="nofollow">https:// .shish.io to the docker container named sn- Docker containers get built with github actions and pushed to docker hub I’ve occasionally looked into cloud stuff, but it all seems orders-of-magnitude more expensive for day-to-day use, and there’s no cost ceiling if I do something dumb and…
I deploy to actual VPCs, the old way. No containers. No PaaS. Just get a Linux machine with a static IP and install. I use ansible to automate the deployment. If I need some storage of undefined quantity, in the case of say image uploads, I might bring in S3 (or equivalent) service. But other than that, just a VPC.
These are downloaded via RAPID and create -with the previous shards a image of the game in the engines local install. After that its buisness as usual.
My use case is app websites (https://lunar.fyi, https://lowtechguys.com), public databases (https://db.lunar.fyi), personal APIs (for uploading files, optimizing images/videos, MQTT etc.) and websites for my relatives (https://robert.panaitiu.com)
I've had this configuration for 2 years now: https://www.hetzner.com/dedicated-rootserver/ax41-nvme
AMD Ryzen 5 3600 Hexa-Core "Matisse" (Zen2)
64 GB DDR4 RAM
2 x 512 GB NVMe SSD (Software-RAID 1)
1 Gbit/s bandwidth
I usually start a side project by simply running it in a tmux on the machine. If it becomes larger, I promote it to a docker-compose file inside Portainer.
When I find myself needing to update/re-deploy often enough, I create a repo for the compose.yaml file and create a Portainer stack with that repo. That way, a `git push` can re-deploy automatically with rollback on failure.
Sometimes I might need to run tasks like building a binary or a more advanced Docker image on `git push`, so I also self host Drone CI [2] for that.
Portainer also supports Kubernetes, but I just don't feel comfortable with its complexity. I feel more at home with running `docker ps/exec/logs` to troubleshoot possible problems, or test out some ideas quickly.
I went through Heroku, then DigitalOcean, then GCP, AWS, Hetzner Cloud, and finally landed on a dedicated Hetzner server at €45/month My use case is app websites ( https://lunar.fyi , https://lowtechguys.com ), public databases ( https://db.lunar.fyi ), personal APIs (for uploading files, optimizing images/videos, MQTT etc.) and websites for my relatives ( https://robert.panaitiu.com ) I've had this configuration for…
I've been using Render and Fly.io Render is the closest thing to Heroku's ease of deployment currently. Major disadvantage is the larger build times.
If you're interested in sharing more: What determines if you choose render or fly for a given project? What makes fly not as easy as render? (I am contemplating moving off heroku, and these seem to be the major contenders for analogous ease of operations).
Bear in mind that I'm only comparing these too in terms of their free tiers.