31–40 of 569 posts
Frontend will either be React or plain ol' JS depending on how complex the idea is.
Heroku is still a great choice if you're willing to pay to never think about infrastructure. On the other hand if you're willing to ask for help there are plenty of freelance IT admins who would set up a digital ocean box with the DIY equivalent of Heroku.
If you only need a static site though I have used Cactus but Jekyll could work.
Heroku is still a great choice if you're willing to pay to never think about infrastructure. On the other hand if you're willing to ask for help there are plenty of freelance IT admins who would set up a digital ocean box with the DIY equivalent of Heroku.
Not trying to be snarky but... how is it cheaper to hire a freelance IT person to set up something for you, and help you when it breaks/changes, than $7/mo for Heroku?
I write the server-side in Go, cross-compile to a Linux binary, and set that up as a service on a vanilla Ubuntu box (usually Digital Ocean). Deploying a new version is a matter of sftp'ing the new binary (and any templates, images, etc) over the top of the old one and restarting the service. If I need a database then I use Postgres, and the setup for that can be a pain, so I get it documented/scripted using Ansible.…
I second this; Go + React.js (Vue.js in my case) I talked about it just a couple of hours ago [1]. [1] https://news.ycombinator.com/item?id=17215658