Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Ask HN: What is your go-to stack for the web?.
UI: Django templates, htmx, tailwind, vanilla js or hypersceript, no build, no node, no npm. Avoiding writing js as much as possible.
Background workers: RQ with 3 priority queues
Deployment: Kamal one command deployment with underlying docker
Hosting: Linode server with backups
Storage: Mounted volume on the machine (maybe s3 eventually).
Benefits:
* High speed of iteration
* No boilerplate mess
* No build therefore no dealing with dependencies and npm rabbithole
* Fast deployment with Kamal (a bit of learning curve but once up just works)
* Much cheaper compared to PaaS. At least 50%.
* Multiple websites on the same instance
Of course I know django quite well so the goal is to remove as much friction as possible.
There are no comments on this comment yet.
UI: Django templates, htmx, tailwind, vanilla js or hypersceript, no build, no node, no npm. Avoiding writing js as much as possible.
Background workers: RQ with 3 priority queues
Deployment: Kamal one command deployment with underlying docker
Hosting: Linode server with backups
Storage: Mounted volume on the machine (maybe s3 eventually).
Benefits:
* High speed of iteration
* No boilerplate mess
* No build therefore no dealing with dependencies and npm rabbithole
* Fast deployment with Kamal (a bit of learning curve but once up just works)
* Much cheaper compared to PaaS. At least 50%.
* Multiple websites on the same instance
Of course I know django quite well so the goal is to remove as much friction as possible.