mk-fg
/
blog
1
0
Fork 0
Code Issues Pull Requests Releases Activity
Source for blog.fraggod.net https://blog.fraggod.net/
204 Commits
1 Branch
0 Tags
5.6 MiB
Python 46.6%
CSS 23.7%
HTML 17.7%
Go 7.4%
Makefile 4.6%
 
 
 
 
 
Go to file
Mike Kazantsev 178538c4e0
LESSOUTPUT-filter: add note on +1 fix for unicode hyphens 		2023-09-10 22:32:15 +05:00
content LESSOUTPUT-filter: add note on +1 fix for unicode hyphens 2023-09-10 22:32:15 +05:00
plugins Add obsoletion note for not-too-old-ish entry on tmux rate-limiting 2015-11-08 02:52:18 +05:00
themes/mockingbird css: up the contrast for most text, fix standalone link underlines 2023-01-09 18:02:53 +05:00
.gitignore Add legacy-redirects.py for simple nginx/uwsgi setup with "error_page 404 = @uwsgi" 2019-11-27 17:43:46 +05:00
COPYING Added some repo metadata files 2013-01-24 13:48:16 +06:00
Makefile +entry 2019-12-30 18:32:49 +05:00
README.rst README: add repo alt-links 2022-10-18 09:22:20 +05:00
legacy-redirects.py conf: put favicon/robots to output root 2019-12-03 18:29:36 +05:00
pelicanconf.py conf: put favicon/robots to output root 2019-12-03 18:29:36 +05:00
publishconf.py +pelican 2013-01-24 04:50:01 +06:00
uwsgi.ini Add legacy-redirects.py for simple nginx/uwsgi setup with "error_page 404 = @uwsgi" 2019-11-27 17:43:46 +05:00

README.rst

Sources for my blog (blog.fraggod.net)

It was based on bloog engine in the past (not present in this repo history), but it was a bad choice for a platform - inconvenient to update, data not versioned properly and generally hard-to-access, not to mention numerous minor issues.

Not a bad platform in general, just very poorly suited for my "rare hacks and edits by poweruser" use-case.

Currently it's a pelican-based static blog, generated from ReST (.rst) sources in "content" dir.

Blog instance is deployed at: https://blog.fraggod.net/

Repository URLs:

Feel free to re-use any original content under WTFPL license as you see fit.