3 ms·

If I were ever going to blog I’d do something like this with Cloudflare perhaps in front: https://docs.replit.com/tutorials/build-host-company-blog-on-replit-w

If I were ever going to blog I’d do something like this with Cloudflare perhaps in front: https://docs.replit.com/tutorials/build-host-company-blog-on-replit-with-hugo-nix https://docs.replit.com/tutorials/build-host-company-blog-on... Love the idea of just using Replit or similar web-based/cloud editor/IDE to create the content. And I also like the idea of having Replit control/host the content/files whilst also pushed to a GH repo. So far I’ve been too lazy to attempt it though. Have just had that tab open in my browser for months as a reminder/todo to friggin do it but hasn’t happened yet..

dangus 4y ago
If you are stuck on completing this long-ass tutorial that you linked, I’d suggest not overcomplicating it and just launching a VM, droplet, or even just paying a provider for blog hosting. For me Ghost worked very well for this purpose. I’ve had this happen to me far too many times: my engineering sensibilities get in the way of just putting the stuff out there. My suggestion is to off the engineering cap and pretend like your blog or website is a business. What return on investment do you get out of all the time spent writing configuration/code, figuring out your deployment scheme, and standing up infrastructure? For me, I didn’t get any, so I decided to scrap my overcomplicated nonsense and spin up a DigitalOcean droplet with a few clicks. Another few clicks to dump it behind Clpudflare, enable some basic VM backups, and add a basic DO firewall and I was done.
- indigodaddy 4y ago
  I think you’re probably right. All the searching and researching for the exact perfect way to deploy/infra it is likely just part of procrastination in general of the writing and getting down to it. Probably should just throw something on one my 2 or 3 long-idling VMs or one of my OCI free tier instances..
dizhn 4y ago
I use the gitlab web ide which also has basic preview support for markdown. I ensure that I keep the markup to a minimum. I don't even use pictures. When I commit cloudflare (whose build/publish process went from 3-5 minues to seconds) makes it available almost instantly. It's a hugo site which I created by taking a theme I like and gutting unneccessary things. I don't update the code or theme at all and the hugo version is fixed in the cloudflare pages settings. I do not use the hugo tooling at all anymore. You could also write your own script like a lot of people on HN seemt to be doing and configure the build step to do nothing but take whatever is in your web directory and publish it. (Obviously the same is possible with github. I actually migrated from there. Gitlab can import github repos, and the only change needed on the cloudflare side was change where the repo points to and set up the new token)

dangus 4y ago

If you are stuck on completing this long-ass tutorial that you linked, I’d suggest not overcomplicating it and just launching a VM, droplet, or even just paying a provider for blog hosting. For me Ghost worked very well for this purpose. I’ve had this happen to me far too many times: my engineering sensibilities get in the way of just putting the stuff out there. My suggestion is to off the engineering cap and pretend like your blog or website is a business. What return on investment do you get out of all the time spent writing configuration/code, figuring out your deployment scheme, and standing up infrastructure? For me, I didn’t get any, so I decided to scrap my overcomplicated nonsense and spin up a DigitalOcean droplet with a few clicks. Another few clicks to dump it behind Clpudflare, enable some basic VM backups, and add a basic DO firewall and I was done.

indigodaddy 4y ago
I think you’re probably right. All the searching and researching for the exact perfect way to deploy/infra it is likely just part of procrastination in general of the writing and getting down to it. Probably should just throw something on one my 2 or 3 long-idling VMs or one of my OCI free tier instances..

dizhn 4y ago

I use the gitlab web ide which also has basic preview support for markdown. I ensure that I keep the markup to a minimum. I don't even use pictures. When I commit cloudflare (whose build/publish process went from 3-5 minues to seconds) makes it available almost instantly. It's a hugo site which I created by taking a theme I like and gutting unneccessary things. I don't update the code or theme at all and the hugo version is fixed in the cloudflare pages settings. I do not use the hugo tooling at all anymore. You could also write your own script like a lot of people on HN seemt to be doing and configure the build step to do nothing but take whatever is in your web directory and publish it. (Obviously the same is possible with github. I actually migrated from there. Gitlab can import github repos, and the only change needed on the cloudflare side was change where the repo points to and set up the new token)