3 ms·

It's cool that you made an experiment here, but I wanted to say that whenever I see people hosting blogs with expensive software (NodeJS with Express, or a PHP

by fiatjaf 11y ago

It's cool that you made an experiment here, but I wanted to say that whenever I see people hosting blogs with expensive software (NodeJS with Express, or a PHP CMS, or other complete stack) I think it will be complicated to host those things forever, so probably the content will vanish some time in the near future. This could apply to experimental setups also, but perhaps experimental people are totally different from people that use the same tools for all kinds of jobs and will perhaps be able to migrate their data from the experimental tools if they prove to not be as good as first imagined.

fiatjaf 11y ago
Totally forgot about my own experiment: I created this GitHub-based (somewhat similar to GitBack) blogging platform: https://github.com/fiatjaf/coisas https://github.com/fiatjaf/coisas and started my blog and my girlfriend's on it. The development of the tool proved to be complicated and I wouldn't be able to maintain it, but I have managed to migrate my blog to Jekyll and my girlfriend's to https://websitesfortrello.com/ https://websitesfortrello.com/, keeping content and URLs. Thanks to me, the internet is a better place. You can stop clapping now.
bbrennan 11y ago
Curious what you mean by "expensive"...are you talking about monetary or maintenance cost? I keep a cheap bottom-tier ec2 instance alive to run my website, stand up demos, etc. Keeping a node instance alive is pretty easy, and one of the reasons I used GitBack was so I wouldn't have to stand up a MongoDB instance...the content just lives with the code on GitHub. Given that all my content lives in Markdown files, I'm not too afraid of migrating to GitHub pages, Medium.com, etc
- fiatjaf 11y ago
  Computing cost, or maintenance, whatever. It takes a machine running a memory-intensive NodeJS process, more if it uses a memory-intensive database. It is much cheaper to host a static site, that's why GitHub offers it for free.

by fiatjaf 11y ago

fiatjaf 11y ago

Totally forgot about my own experiment: I created this GitHub-based (somewhat similar to GitBack) blogging platform: https://github.com/fiatjaf/coisas https://github.com/fiatjaf/coisas and started my blog and my girlfriend's on it. The development of the tool proved to be complicated and I wouldn't be able to maintain it, but I have managed to migrate my blog to Jekyll and my girlfriend's to https://websitesfortrello.com/ https://websitesfortrello.com/, keeping content and URLs. Thanks to me, the internet is a better place. You can stop clapping now.

bbrennan 11y ago

Curious what you mean by "expensive"...are you talking about monetary or maintenance cost? I keep a cheap bottom-tier ec2 instance alive to run my website, stand up demos, etc. Keeping a node instance alive is pretty easy, and one of the reasons I used GitBack was so I wouldn't have to stand up a MongoDB instance...the content just lives with the code on GitHub. Given that all my content lives in Markdown files, I'm not too afraid of migrating to GitHub pages, Medium.com, etc

fiatjaf 11y ago
Computing cost, or maintenance, whatever. It takes a machine running a memory-intensive NodeJS process, more if it uses a memory-intensive database. It is much cheaper to host a static site, that's why GitHub offers it for free.