Your favorite static site generator can be used with free, no-ads hosting at indie https://neocities.org. Their $5/mo plan adds custom domains and higher disk/traffic quotas.
Blog with Markdown and Git, and degrade gracefully through time
41–50 of 182 posts
Re: Blog with Markdown and Git, and degrade gracefully through time
#42For all the (deserved) complaints people have about wordpress, it's been around since before git or markdown was even a thing. For all its faults, its been pretty resilient to time. The real reason most websites disappear is a much more human one.
> The real reason most websites disappear is a much more human one.
So true.
I have had a blog running since 2006, all was php based back then with (html) posts inside a database. The tooling shouldn't be a problem, I switched systems several times (once every few years).
Currently on Hugo with markdown posts. As long as you treat your migration carefully and take some time to migrate, every tool should suffice. It's mostly about human effort and human error when things get lost.
Re: Blog with Markdown and Git, and degrade gracefully through time
#43I am using Gatsby for my site https://www.bobbydreamer.com and saving the markdowns at git here https://github.com/bobbydreamer/bdv32 I haven't setup CI pipeline yet. It true whats said in the post, I used to save links thinking it won't disappear. But most the links, I had saved, it's no more.
How does having the "BSD Zero Clause" with your content work? I open sourced my blog's software, but I still keep all the actual content in a separate private repo, since I don't want my written content distributed under the same license. Also works out well, since I have the github action automation in the private content repo.
I can still easily change the private flag down the road if I were to decommission it (though, unlikely -- I'd just archive it somewhere).
I'm also using Gatsby if anyone is curious (https://github.com/cbeley/beleyblog & https://chrisbeley.com).
Re: Blog with Markdown and Git, and degrade gracefully through time
#44Earlier quoted context omitted.
I have a similar setup for my blog and I'm using Netlify for both CI and hosting (free). It's been great! GitHub Actions could probably work well for you if you already have decent hosting.
Any particular guide or set of docs you recommend for that? I've heard a lot of good things about Netlify as far as hosting, and I've been wanting to set up a blog; seems like as good a time as ever to start learning.
https://blog.aawadia.dev/2021/02/08/where-is-this-blog-hoste...
Lmk if you need any extra details
Re: Blog with Markdown and Git, and degrade gracefully through time
#45I actually follow this sentiment with my resume andyhablewitz.com
Re: Blog with Markdown and Git, and degrade gracefully through time
#46I started my blog about python/django ( https://simpleisbetterthancomplex.com ) using Jekyll and hosting on Github Pages and it was pretty good to get started because back then I wasn't sure if I would keep it up or not. After a year or so I migrated to a 5 USD droplet on Digital Ocean (back then GH Pages didn't offer https for custom domains) and integrated with Github webhooks to automate the deployment when pushin…
There was a company on here the other day talking about their product, built on top of Docker. I wish I'd bookmarked it.
Their secret sauce is, effectively, partial evaluation in Docker images. They run the code to detect if any of the changes in a layer have side effects that require that layer to be rebuilt (which invariably causes every layer after to be rebuilt)
I mention this because if I'm editing a single page, I would like to be able to test that edit in log(n) time worst case. I can justify that desire. If I'm editing a cross-cutting concern, I'm altering the very fabric of the site and now nlogn seems unavoidable. Also less problematic because hopefully I've learned what works and what doesn't before the cost of failure gets too large. It would be good if these publishing tools had a cause-and-effect map of my code that can avoid boiling the ocean every time.
Re: Blog with Markdown and Git, and degrade gracefully through time
#47I used to have my blog source on GitHub, but then it turned out I didn't want my half-finished works-in-progress public. To use a private repository would rather defeat the point; using a private repo and a public fork is inviting confusion. Now I just use a private repo on my own server, cloned to my dev machine. Does anyone have a usable solution for that problem?
I've been thinking about this a lot. I created Ponder so that I could quickly create drafts in my browser. Then I planned to move them to my blog (Markdown on GitHub) when I'm done.
I need more than 10 drafts (the current limit in Ponder), but I feel like I'm getting close to a solution that works better for me. I also want to be able to edit across machines (Mac, Chromebook, Phone), so I need to make the app work online.
Anyway...
Re: Blog with Markdown and Git, and degrade gracefully through time
#48I used to have my blog source on GitHub, but then it turned out I didn't want my half-finished works-in-progress public. To use a private repository would rather defeat the point; using a private repo and a public fork is inviting confusion. Now I just use a private repo on my own server, cloned to my dev machine. Does anyone have a usable solution for that problem?
I put my drafts in branches and only push the main branch to GitHub.
going to start doing this!
Re: Blog with Markdown and Git, and degrade gracefully through time
#49I started my blog about python/django ( https://simpleisbetterthancomplex.com ) using Jekyll and hosting on Github Pages and it was pretty good to get started because back then I wasn't sure if I would keep it up or not. After a year or so I migrated to a 5 USD droplet on Digital Ocean (back then GH Pages didn't offer https for custom domains) and integrated with Github webhooks to automate the deployment when pushin…
Don’t know about Jekyll but with Hugo you just run hugo server in the Git repo and it will give a a live preview that you can view in the browser, served locally.
It’s very fast.
I have a mockup blog with ~90 pages and it takes 190 ms to generate the whole site.
Re: Blog with Markdown and Git, and degrade gracefully through time
#50A bit morbid I know, but I've been thinking I would like my blog to outlive me. I have my blog on blogger.com, and while I've been tempted to switch to something more modern and fun in a container on a VPS, I've resisted, because I think blogger.com is not going away in my lifetime. A VPS and a personal domain on the other hand is going to get shutdown when someday I die and my credit card gets closed. At this stage Github Pages is probably also as likely to stick around as Blogger though.