I am currently evaluating bashblog which seems to be the perfect solution for my current use case: basically, a hand-written PHP website (please don't judge me, it was the right choice this time ;-)) which has everything but a blog section because this was still much less work than retro-fitting one of the ~ 500 available static CMSs.
While playing with the .config file, I noticed two missing features. Let me suggest them:
Configurable file extensions. My website has a PHP header which can not be used by bashblog because I can't generate PHP files. As there is no real reason for that, I would like to have a way to replace .html by (e.g.) .php.
Configurable output paths. My HTML (or PHP :-)) files are publicly readable for obvious reasons. Right now, bb.sh seems to enforce to be in the same folder as well. It should be possible to replace ./ by some/folder/ with a .config setting.
I am currently evaluating bashblog which seems to be the perfect solution for my current use case: basically, a hand-written PHP website (please don't judge me, it was the right choice this time ;-)) which has everything but a blog section because this was still much less work than retro-fitting one of the ~ 500 available static CMSs.
While playing with the
.configfile, I noticed two missing features. Let me suggest them:.htmlby (e.g.).php.bb.shseems to enforce to be in the same folder as well. It should be possible to replace./bysome/folder/with a.configsetting.What do you think?