Menu

SN

SnapDeploy

Author Profile

Claim This Author Profile

Prove ownership by publishing #HashtagPLUS and this profile link on your author page or an article under your byline. A moderator or admin will review the request before it merges into your real HashtagPLUS username.

Sign In To Claim
0 karma0 postsjoined 27 days ago

🌐 dev.toSource

TL;DR: A net/http service with a health endpoint, graceful shutdown and the port read from the environment, built by a two-stage Dockerfile into a 7 MB binary and an image around 15 MB. What it uses at runtime on 512 MB and a quarter of a CPU, how to add a database without adding

about 14 hours ago

🌐 dev.toSource

TL;DR: By default the JVM takes only a quarter of a container's memory limit for the heap, and a small Boot app can take half a minute to start on a quarter of a CPU. Telling the JVM how much it may use, trimming what Boot starts, and building a layered image on Java 21 fixes mos

4 days ago

🌐 dev.toSource

TL;DR: Render's free tier is the right place to stay if you run one service that should be reachable most of the time, want a free custom domain, or host a static site. When you outgrow 750 shared hours, a tenth of a CPU or the 30-day database, this is the move: turn the Render c

6 days ago

🌐 dev.toSource

TL;DR: A standard Django project taken to a live URL on a free container tier: Gunicorn, WhiteNoise for static files, settings read from environment variables, and a real PostgreSQL instead of a SQLite file that vanishes on the next deploy. Tested with Django 5.2 LTS on Python 3.

9 days ago

🌐 dev.toSource

TL;DR: A step-by-step walkthrough from an empty folder to a live HTTPS URL: a small Express app, a Dockerfile and a .dockerignore, a local test, a push to GitHub, the deploy itself, environment variables, an optional $1 managed database, and the checks that tell you it worked. No

11 days ago

🌐 dev.toSource

TL;DR: Moving off Heroku is mostly two files and one export: pull your config vars and a database dump, turn the Procfile into a Dockerfile (Node, Python, Java and Rails examples below), deploy the repo, restore the database into a managed add-on, and fix the three things that br

17 days ago

🌐 dev.toSource

TL;DR: docker compose up is a development command; there is no compose-to-cloud button, and service names like http://api:8080 only resolve on the machine running Compose. Four honest ways to get a multi-container app into production: split the services onto a container PaaS (wha

25 days ago

🌐 dev.toSource

TL;DR: We put the same Flask, Django and FastAPI apps on six places that host Python for free (SnapDeploy, Render, Railway, PythonAnywhere, Google Cloud Run, Vercel) with production Dockerfiles. Below: which framework to pick, what each host actually gives you free and where it s

27 days ago