What if you started blogging in 2000? Or even in 2005, when git and Markdown existed, but were still not popular? Would you say... HTML and subversion/CVS is appropriate for long-term blog storage?
Blog with Markdown and Git, and degrade gracefully through time
111–120 of 182 posts
Re: Blog with Markdown and Git, and degrade gracefully through time
#112Earlier quoted context omitted.
Setting aside how weary I am of "M$" (it's just about tied with using "sheep" to describe Apple users), what on God's green earth does Microsoft have to do with the OP's point? GitHub itself is not and was never open source. It's not like Microsoft bought it and closed off the source. Do you think using Microsoft tools demonically injects anti-FSF sentiment into your work? ("I started using VS Code, and now whenever…
github seems to have a nicer flavor markdown. Maybe it's just because github is code oriented.
Yes, it's named GFM (github flavored markdown). See https://guides.github.com/features/mastering-markdown/ and https://github.github.com/gfm/#what-is-github-flavored-markd... (full specs).
Re: Blog with Markdown and Git, and degrade gracefully through time
#113Earlier quoted context omitted.
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…
Are you referring to LayerCI, possibly?
Must be, since algolia shows me questions from 8 days ago that sound familiar.
Re: Blog with Markdown and Git, and degrade gracefully through time
#114Earlier quoted context omitted.
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.
I've evaluated Netlify for my blog at https://jdsalaro.com and I'd advise against that unless you're missing a CMS on your static site generator. Other than that I personally felt it didn't bring much to the table. I do admit that their CMS is slick, but it wasn't really a feature I needed. Of course I'm not sure what other people are using them for, but in my case GitLab/GitHub covered all my bases pretty well since…
Github's main business is not Github Pages or be a CDN.
Netlify's main business is.
Netlify also provides deployment previews for commits and PRs, and a complete CI/CD pipeline that you would have to implement yourself with Github Actions or something else.
The CMS isn't what I need either, but there is so much more than just hosting.
Re: Blog with Markdown and Git, and degrade gracefully through time
#115Earlier quoted context omitted.
yes because of a bad design decision I made to create a custom "related posts", which is a code that searches all my markdowns to pick the best pages and add to the current page. so even with `--incremental` it take quite some time to regenerate
Not really fair to blame the performance on Jekyll, then. Presumably you could build yourself to the same issue with any other generator.
that's a good point and I agree with you
to be honest jekyll still serves the purpose really well (especially for the reader)
the site is still sitting on an inexpensive entry-level cloud server, it's relatively fast, serves 300k+ page views every month and it give me some passive income
i'm pretty sure that if one uses the framework properly it can still hold on very well
i think what left me with a mixed feeling about static site generators is that it is constantly holding you back whenever you think about growing your website. i ended up building a django api that runs on the same vpc as the blog itself, and i used it to expand some features, like reading from google analytics the total page views for a given blog post, or consuming the disqus api to list the latest comments on the home page. this kind of thing.
managing the posts in static files is quite challenging as the number of posts grows. at some point you will want to change some info, or add a certain metadata and you will need to write a script to walk the _posts dir and edit the files (maybe there's a better way of doing that :P)
Re: Blog with Markdown and Git, and degrade gracefully through time
#116Earlier quoted context omitted.
Is it slow to regenerate a single post even with Jekyll’s ‘—incremental’ mode?
yes because of a bad design decision I made to create a custom "related posts", which is a code that searches all my markdowns to pick the best pages and add to the current page. so even with `--incremental` it take quite some time to regenerate
I wonder if you could save some time with some caching?
Find all posts related to "django", select the top 3, pin them as the related posts for all django entries? You'd trade out some uniqueness and slightly increased memory usage to gain speed.
(I just got started blogging and found https://github.com/sunainapai/makesite python static site generator worked well for me. Obviously you're probably a bit far in to switch horses by now.)
Re: Blog with Markdown and Git, and degrade gracefully through time
#117I 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…
Something similar happened to me when I was using static site generators. In fact one that I was really enjoying even switched programming languages between 1.x and 2.0. Since that time I look for the people and community behind the project, and try to find signs of stability and long-term care. After that I look at open formats rather than open and flexible architecture-chains. For example, I'd rather use my LibreOf…
> I'd rather use my LibreOffice HTML template and simple PHP controller
Could you tell me more about this? I've had a similar idea but the HTML that LibreOffice generates is very gross
Re: Blog with Markdown and Git, and degrade gracefully through time
#118The thing about the net is that it's free to go viewing it. It costs money to put something up _that you control_. For example you have to buy the DNS name. You have to get a host, etc.. I know there are IPFS folks out there but I just don't know if there's anything there yet.
Normal people need a way to have a permanent place that can't be taken down and doesn't auto-expire with your credit card.
Re: Blog with Markdown and Git, and degrade gracefully through time
#119I 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).
> build higher altitude solution that could leverage git/MD/whatever but with free/opensource/selfhosted/alternative tools 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…
> Any self-hosted service or solution is going to not be erosion-resistant by virtue of not being for-profit.
And for-profit services are? Often enough it's the VCs which ruin a service by pressing out money before it inevitably dies because the experience has been degraded to an extreme degree.
Re: Blog with Markdown and Git, and degrade gracefully through time
#120I was thinking of using Markdown and Git for a static website (not a blog). Is this a good idea?