4 ms·

Um... No, it doesn't. > I write a post in markdown, commit and run a pelican-provided script that uploads the generated site to the hosting server. The script-

Um... No, it doesn't. > I write a post in markdown, commit and run a pelican-provided script that uploads the generated site to the hosting server. The script-running could be done with a hook. This is exactly what I don't want to deal with. Sure, I could use a ci service but this is a typical case of over-engineering a simple problem.

rhn_mk1 6y ago
Something must turn the .md into HTML, and something must also publish it. You end up with 2 choices: the above one, or sth like GitLab pages, where you need to provide a CI script but then can just commit & push.
- axegon_ 6y ago
  Yep, you're right, something must turn the markdown into an html. In my case, I let the browser do that and by doing so, I avoid the hassle around builds, cis which is what I didn't want to deal with. For something so brutally simple anyway.
iamacyborg 6y ago
I use Pelican with hosting on Netlify. On my end I write a new markdown post and push it to Github. At that point Netlify takes over to rebuild and redeploy my site including the new post. It's pretty trivial to do. https://github.com/jacquescorbytuech/Blog https://github.com/jacquescorbytuech/Blog https://www.jacquescorbytuech.com/ https://www.jacquescorbytuech.com/
- axegon_ 6y ago
  Trivial? Totally. Self-contained? Absolutely no. Say Microsoft decides to kill github pages. OK, fine, next. Now picture Netlify changing some policy, adding some pricing or killing off a service which you need(unlikely but not entirely impossible). You have to setup the whole thing all over again with someone else, be it circleci, jenkins, gitlab, etc. Though in different contexts, I've been in similar situations and by the third time I usually want to murder someone.
  - onion2k 6y ago
    You're overestimating Netlify's build tooling. It literally just spins up a virtual machine with Node on it, clones your repo, and does an `npm install && npm build`. When that finishes it copies the output directory to a server to host. Moving to a different host is a case of finding something that will let you do the `npm install && npm build` bit, which practically every modern hosting company does these days. Netlify's automated builds aren't even close to the complexity of running a CI process. If you wanted to you could run the build process locally and commit the output HTML and CSS files to the repo, and the build process wouldn't even be necessary. You'd just need to copy the output files to a server using a git commit hook.
    - axegon_ 6y ago
      Which brings us back to my original question: Why????? Why bother doing all that and relying on third party tooling, regardless of how simple it is to run a command? If this is what I wanted, I could write a 5 line shell script on a raspberry pi which can do just that. I DON'T want to do either of that. Add a file, push it and know everything has worked.
      - onion2k 6y ago
        The reason I have things set up to deploy from github to Netlify is mainly because I'm not the only contributor to things I work on. As soon as you work in a team it's far simpler to have a central service that people push to doing the builds, especially if you don't want contributors to have access to the host server.
        axegon_ 6y ago
        I'm not questioning the scenario where you have multiple contributors. This is one of the major reasons why the concept of ci/cd exists. The topic of the thread is __specifically__ personal blogs/pages and my point is as strong as ever: having to deal with builds, cis, for your personal page is pure bs.
      - 6y ago
deleted 6y ago
[deleted]
deleted 6y ago
[deleted]

rhn_mk1 6y ago

Something must turn the .md into HTML, and something must also publish it. You end up with 2 choices: the above one, or sth like GitLab pages, where you need to provide a CI script but then can just commit & push.

axegon_ 6y ago
Yep, you're right, something must turn the markdown into an html. In my case, I let the browser do that and by doing so, I avoid the hassle around builds, cis which is what I didn't want to deal with. For something so brutally simple anyway.

iamacyborg 6y ago

I use Pelican with hosting on Netlify. On my end I write a new markdown post and push it to Github. At that point Netlify takes over to rebuild and redeploy my site including the new post. It's pretty trivial to do. https://github.com/jacquescorbytuech/Blog https://github.com/jacquescorbytuech/Blog https://www.jacquescorbytuech.com/ https://www.jacquescorbytuech.com/

axegon_ 6y ago
Trivial? Totally. Self-contained? Absolutely no. Say Microsoft decides to kill github pages. OK, fine, next. Now picture Netlify changing some policy, adding some pricing or killing off a service which you need(unlikely but not entirely impossible). You have to setup the whole thing all over again with someone else, be it circleci, jenkins, gitlab, etc. Though in different contexts, I've been in similar situations and by the third time I usually want to murder someone.
- onion2k 6y ago
  You're overestimating Netlify's build tooling. It literally just spins up a virtual machine with Node on it, clones your repo, and does an `npm install && npm build`. When that finishes it copies the output directory to a server to host. Moving to a different host is a case of finding something that will let you do the `npm install && npm build` bit, which practically every modern hosting company does these days. Netlify's automated builds aren't even close to the complexity of running a CI process. If you wanted to you could run the build process locally and commit the output HTML and CSS files to the repo, and the build process wouldn't even be necessary. You'd just need to copy the output files to a server using a git commit hook.
  - axegon_ 6y ago
    Which brings us back to my original question: Why????? Why bother doing all that and relying on third party tooling, regardless of how simple it is to run a command? If this is what I wanted, I could write a 5 line shell script on a raspberry pi which can do just that. I DON'T want to do either of that. Add a file, push it and know everything has worked.
    - onion2k 6y ago
      The reason I have things set up to deploy from github to Netlify is mainly because I'm not the only contributor to things I work on. As soon as you work in a team it's far simpler to have a central service that people push to doing the builds, especially if you don't want contributors to have access to the host server.
      - axegon_ 6y ago
        I'm not questioning the scenario where you have multiple contributors. This is one of the major reasons why the concept of ci/cd exists. The topic of the thread is __specifically__ personal blogs/pages and my point is as strong as ever: having to deal with builds, cis, for your personal page is pure bs.
    - 6y ago

deleted 6y ago

[deleted]

deleted 6y ago

[deleted]