I’m sure I’ve blogged about this before but deploying Micro.blog is like a hilarious 15-step process. So dumb! And yet I do it at least once a day usually. Eventually it’ll be worth burning a couple days to automate it.
@manton I assumed you just had makefiles making makefiles for all that. I can’t stand the 4-5 step process to deploy my academic page (which has me thinking about switching that to Micro Blog too).
@lukemperez Cool, let us know if you have any questions. I think some folks have used MathJax on blogs hosted on Micro.blog.
@manton how long does it usually take you to deploy? How many hours do you think it would take to automate?
@JonLillie Not long to deploy, a few minutes usually. Will take a day or so to fully automate, mostly playing nicely with the load balancers.
@manton so ROI won’t be seen for a few months? I sometimes find my self also putting off automation because it only takes me a few minutes. Need to get out of that mindset for somethings.
@manton Here’s a random question about that. What would be the best practice for hosting files like my CV or articles that I make available for download. On Hugo, I just throw them in the static folder. My hunch is that I could throw them up on Dropbox, or even Github, and link them. But maybe there’s a better way for efficiency, or whatever?
@lukemperez You can upload PDFs and things like that in Micro.blog’s Uploads section and link to them. That’s the easiest way. Another option, if the files don’t change often, is to put them in a Micro.blog plug-in which does use Hugo’s static folder. I wrote a help post about it here.
@manton I usually take an incremental process for automating stuff like this. Step 1 is just writing out all of the steps in a text file. Step 2 is to rename that file as a script in, say, bash, with those steps converted to comments. Step 3..n: automate a little piece each time.
