4 ms·
Here's my stack: I write .html files in GNU Nano, and serve them with Apache. I've done that for about 20 years (with varying editors and servers), and I don't
by encom 6y ago
Here's my stack: I write .html files in GNU Nano, and serve them with Apache. I've done that for about 20 years (with varying editors and servers), and I don't see why it needs to be any more complicated putting words on the internet.
Yes yes, old man yells at cloud etc, but I'm a strong believer in "less is more".
- Cthulhu_ 6y agoThere's nothing wrong with that approach tbh; when you think about it, the only reason to make a dynamic website is to prevent duplication, things like headers, menus, styles, etc. But there's ways around that, like frames.
- fish45 6y agoas a non web developer who needed to get a static site with a consistent header and footer up I just made a makefile which watches an src directory and cats the header and footer onto each file
- duxup 6y agoEveryone's "less" is different I think. Someone has a workflow that they know like the back of their hand and has low friction... that's less. Good for them. Folks get worked up on developer choices so much, if it's a blog and it's not doing something seriously bad ... it's their site and their call IMO. When I was into photography one of the biggest lessons I learned was you use the tool... you're going to use a lot. It doesn't matter what it is as much as the tool should allow you to do the thing and not get in the way because you think you "should" be using something else.
- dusted 6y agoHERESY! The only true path is mine, I write .htm files in vim and serve them with nginx. Yes, I agree, cloudyelling or not, no stack is better. I recall in my teenage years, I built 2 or 4 "CMS" in PHP/MySQL, at the end, added all that AJAX when browsers blessed us with the possibility of making HTTP calls from JavaScript! But in the end, migrating from server to server, learning more about everything, the only thing that seems somewhat stable are plain text or pure html. I know I can edit them in 2000 years, if I am still alive by then.
- swiley 6y agoNginx? Why not busybox httpd with OpenSSL sconnect? So much bloat. :p
- dusted 6y agoHmm, you're right, but I do use the nginx as reverse proxy for some of the other sites which are not static :P I'm also running everything in docker containers, so I'm closet-hipster I guess xD
- anderspitman 6y agobusybox and OpenSSL? So much bloat. My blog is browsable with netcat :p nc txt.anderspitman.net 3838 <<< /txt/19
- canada_dry 6y agoHad to check. +1 works like a charm. You win.
- NewEntryHN 6y agoIt becomes more complicated as soon as a you have a sidebar with "Last articles" in which case you would need to edit each single HTML files to edit the sidebar consistently. Even with a single archives page you need to think about updating the archive for each new article. Also Markdown is definitely more author-friendly than HTML, but that's more like an extra.
- frereubu 6y agoIf you're using Apache, which he said he was, you can just use server-side includes: https://httpd.apache.org/docs/current/mod/mod_include.html#element.include https://httpd.apache.org/docs/current/mod/mod_include.html#e...
- clarry 6y agoIn the distant past, we used client side includes. They were known as framesets.
- microcolonel 6y agoAnother option is to use cat and a shell script or Makefile, or I guess some people use m4.
- llimllib 6y agoI use a makefile that runs a short python script, very simple
- justinmeiners 6y agocat header > index.html cat page >> index.html cat footer >> index.html
- carapace 6y agocat header page footer > index.html ("cat" is short for "concatenate".) ;)
- adrianN 6y agoI write something like HTML and process it with m4.
- cddotdotslash 6y agoI think that personal sites are usually the ideal grounds for exploring a new technology or learning a new language/framework/cloud/fill-in-the-blank. That's why a lot of them run on often-times ridiculously over-engineered tech. If you have a site that is working for you - great! Could every developer's blog be a set of HTML files and a script? Sure. But many developers prefer to tinker and build on new technologies, and their personal site or blog is a great place for that tinkering.
- ge96 6y agoI'll make a basic UI eg. menu/side panel/body/basic write interface and then use LAMP. I can add additional capabilities eg. commenting/stats(view counting) if I want... don't think I personally need anything more than that. My stuff is dynamic eg. using TEXT for body through MySQL. I use Node now as a backend but for something quick I can still use PHP which is where I came from/started with. I can host images wherever/maybe add free CDN account.
- otter-in-a-suit 6y agoThat's what I do with my website[0] as well (just on nginx and with vim via SSH). However, something that requires more functionality - syntax highlighting, tags, version control, easier deployments - I recently switched to Markdown + Hugo. [1] I find it all to be very subjective. The above author clearly favors TypeScript and React, and for a personal blog, I see nothing wrong with slightly over-engineering it. His blog loads quickly, doesn't require an absurd number of network requests, and doesn't include any trackers. Fairly minimalist as far as the endproduct is concerned. [0] https://chollinger.com/ https://chollinger.com/ [1] https://chollinger.com/blog/ https://chollinger.com/blog/