11–20 of 182 posts
I 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.
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 pushing new markdown to the main branch.
Over the time it indeed started to degrade. The build time takes almost a minute, but after building the website is just a bunch of static html pages.
Nowadays it is annoying to write new posts because I like to write locally and refresh to browser to check if it's looking good or not. So I would say it degraded for me but for the reader it's still as fast as it was when there was just a couple of posts.
I thought about migrating the blog to something else, but because I used some custom markdown extensions for code highlight and other things, it would be painful to migrate all the blog posts. So I've been postponing it since 2019.
I 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 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.
Nowadays I'm planning on writing again and have tried a setup that seems to be alright:
- migrate from Pelican to Hugo since the community is more vibrant, responsive and the themes much more mature and well maintained.
- Use a mature, well-maintained documentation-oriented template as base (I based https://jdsalaro.com off Pelican's bootstrap3)
- Create an Obsidian vault out of the posts/ directory to improve note-taking and editing capabilities.
- Host same as before on GitLab
- Deploy via CI/CD copying the posts/ directory to a public repository
- Probably mirroring to GitHub
I'll be able to report back once I've gotten the above fleshed-out :)
I 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 wish people would stop using github as a swiss knife CDN (free hosting, hooks, history through git repo, etc) and build higher altitude solution that could leverage git/MD/whatever but with free/opensource/selfhosted/alternative tools (like gitea instead of github and minio instead of S3 for instance).
Not that I disagree with this, but that goes almost directly against "Mak[ing] that source public via GitHub or another favorite long-lived, erosion-resistant host. Git’s portable, so copy or move repositories as you go."
Any self-hosted service or solution is going to not be erosion-resistant by virtue of not being for-profit.
I might still be able to get around it, but it's still a pain.
I 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?
Stop caring about unfinished, public wip. In the end, nobody but you is really bothered by its imperfections.
I wish people would stop using github as a swiss knife CDN (free hosting, hooks, history through git repo, etc) and build higher altitude solution that could leverage git/MD/whatever but with free/opensource/selfhosted/alternative tools (like gitea instead of github and minio instead of S3 for instance).
why?