Congrats on the bootcamp, Larry Legend. Glad you are liking it. Google tracking uses double quotes.
Alas, we can all agree that JavaScript is a layer of hell we all have to live with until WebAssembly saves the day, that way everyone trying to make a name for themselves will flood the front-end world with Flavor-of-the-month framework in [Python, Ruby, C#, F#, PHP, ...].
*****
So, I have an infrastructure question that I'm trying to balance with a bunch of YAGNI but must-have features.
I'm running my latest project on Heroku because server admin sucks. The main downside right now is keeping up with Let's Encrypt. You can add, but renewing is a total chore. Think I'll just build a new cert every 2 months. Of course, I also need to use Cloudflare to redirect to HTTPS, which seems silly since Heroku advertises "free" TCL certs, which, for some reason, cost $15 / month or so.
The project is a bit polyglot, using Clojure and C, and I may end up dropping in Node later. This isn't exactly an issue as far as I know, but... it's sort of a worry for me moving forward.
The current problem is that I want to allow end-users to store music files on the site. Heroku has a slug-size limit of 300mb. "du -h" says I'm at 120mb, probably due the the image and audio files I have. I do know that music files can be large, so I'm thinking of using Digital Ocean's Block Storage, which is 10c / Gig, so 100gb = $10. Another option is using S3. Heroku has this thing called Bucketeer:
https://elements.heroku.com/addons/bucketeer. (I should be moving all the image and audio files off anyways, I think).
What should I be considering here? I'm half-tempted to bite the bullet and just push everything over to a DO server and add the Block Storage to the server.
The trade-off of moving to DO is obviously all the manual setup and maintenance. Heroku, while less manual, does require quite a few acrobatics to get everything functioning in the app, along with maintaining other things to keep everything cohesive.