Re: [dev] Anyone interested in C "blogging platform"?
On May 24, 2014 5:45:17 PM EEST, Nick wrote: >Quoth Dimitris Zervas: >> >call blog‐gen with the new name. >> Where is the source code? > >It's a shell script; download it and see. Oops sorry, my droid told me that it was binary :P
Re: [dev] Anyone interested in C "blogging platform"?
Quoth Dimitris Zervas: > >call blog‐gen with the new name. > Where is the source code? It's a shell script; download it and see.
Re: [dev] Anyone interested in C "blogging platform"?
>I am using for blogging: >[0] >[1] > >You can use whatever editor you like to create your basic raw file. >Then >copy it to your basic blog directory on the remote site using scp >and >call blog‐gen with the new name. Where is the source code?
Re: [dev] Anyone interested in C "blogging platform"?
Greetings. On Fri, 23 May 2014 20:20:53 +0200 Dimitris Zervas wrote: > 2: Blog preprocessor (bpp [2]). It's a small cgi program that just finds > keywords in the asked page and replaces them with file contents. This is used > to be able to have a navigation bar and (much later) comment system. All of this is too complex. Here is what I am using for blogging: [0] [1] You can use whatever editor you like to create your basic raw file. Then copy it to your basic blog directory on the remote site using scp and call blog‐gen with the new name. Formatting is for wimps. Sincerely, Christoph Lohmann [0] http://www.vr-55.net/ [1] http://www.vr-55.net/bin/blog-gen
Re: [dev] Anyone interested in C "blogging platform"?
>You may be interested in fugitive[0], blog >software using Git hooks. > >[0] https://gitorious.org/fugitive I'll check it, but the whole local install concept is a little strange for me. But I'll have to get a better look. >where can I get smu-smu? http://git.dzervas.gr/smu >I personally use a mix of [0] and [1]. >Investigate at your own risk. Is there anything funny in the code? :p Why "at my own risk"? Looks suspicious.. >This would potentially means lots of >vacuous commits just test out and >debug a site---just to ensure everything's >actually working During the setup, yes. But that's normal. After the setup, you just compile smu and roll your own static html. You can even have a dummy (or a full) bpp to see how the whole thing looks. >mustache[3] is essentially this same >idea. What about a pure C mustache >implementation? Or perhaps just using >their execution of the idea for some >inspiration yourself. I'll check it for sure and yes, I work with pure C and I love it (not experienced at all though...).
Re: [dev] Anyone interested in C "blogging platform"?
> On 05/23, Dimitris Zervas wrote: > > 1: I use git (for versioning and easy management). The posts are written in > markup. Once you make a new commit, a program (or a script?) is triggered and > scans the commit, finds the files altered and either interprets the markup > files (smu [1] is used) and store them as html, so you don't have to do that > on serve time, or deletes the old cached file. Also, it alters a > navigation.html file (used in the second piece) > > The git integration and the navigation altering is not done yet. Git hooks can be used to call just about anything, most existing static site generators included, and running a post-commit hook to build and push a new post isn't a bad idea. But if I'm reading this right, your plan is to not process any of the marked-up content or templates until committing it all to a Git repo. This would potentially means lots of vacuous commits just test out and debug a site---just to ensure everything's actually working. Ideally, commits would be the last thing to happen, and some means of processing a site for previewing would be desirable. I suppose this would depend on how fancy you want things to be, though; if you're just going for a minimal text-on-screen look, previews aren't really important. There are various tips floating around the web for loop-device web servers in bash that might work.[1][2] > 2: Blog preprocessor (bpp [2]). It's a small cgi program that just finds > keywords in the asked page and replaces them with file contents. This is used > to be able to have a navigation bar and (much later) comment system. > > so, if you ask for myfile.html (the post that smu has cached), bpp will scan > the file for the "==navigation" keyword and replace it with the contents of > navigation.html : mustache[3] is essentially this same idea. What about a pure C mustache implementation? Or perhaps just using their execution of the idea for some inspiration yourself. [1]: http://www.debian-administration.org/article/371/A_web_server_in_a_shell_script [2]: http://www.razvantudorica.com/08/web-server-in-one-line-of-bash/ [3]: http://mustache.gitub.io -- "A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools." - Douglas Adams
Re: [dev] Anyone interested in C "blogging platform"?
I personally use a mix of [0] and [1]. Investigate at your own risk. [0] http://git.codemadness.org/static-site-scripts/ [1] http://git.2f30.org/divzeroweb/
Re: [dev] Anyone interested in C "blogging platform"?
where can I get smu-smu?
Re: [dev] Anyone interested in C "blogging platform"?
You may be interested in fugitive[0], blog software using Git hooks. [0] https://gitorious.org/fugitive signature.asc Description: OpenPGP digital signature
Re: [dev] Anyone interested in C "blogging platform"?
On Fri, May 23, 2014 at 06:17:46PM +0300, Dimitris Zervas wrote: > In 2 weeks I will be done with my finals (yay! no more school!) and I will > concentrate on my projects. > > My main project is the C blogging platform which is, well, a blogging > platform - you didn't see that coming huh?. It's based on the suckless > ideology (or at least the way I understand it) and I would really like > someone to join me with this. > So here's the concept. It's split in to 2 pieces: > 1. Uploading and interpreting/caching a post > 2. Adding some dynamic code while serving the page (via CGI) > > 1: I use git (for versioning and easy management). The posts are written in > markup. > Once you make a new commit, a program (or a script?) is triggered and scans > the commit, finds the files altered and either interprets the markup files > (smu [1] is used) and store them as html, so you don't have to do that on > serve time, or deletes the old cached file. > Also, it alters a navigation.html file (used in the second piece) > > The git integration and the navigation altering is not done yet. > > 2: Blog preprocessor (bpp [2]). It's a small cgi program that just finds > keywords in the asked page and replaces them with file contents. This is used > to be able to have a navigation bar and (much later) comment system. > > so, if you ask for myfile.html (the post that smu has cached), bpp will scan > the file for the "==navigation" keyword and replace it with the contents of > navigation.html > > I hope that you get the whole logic. The project has some *serious* security > flaws (such as local file inclusion attack and not only), so do not use it > yet. Not that you can do anything useful right now, but just saying... :P > > [1]: http://git.dzervas.gr/smu > SMU is not mine. I just forked it from here: > https://github.com/Gottox/smu > > [2]: http://git.dzervas.gr/bpp Wrap your lines to 80 chars or less.
[dev] Anyone interested in C "blogging platform"?
In 2 weeks I will be done with my finals (yay! no more school!) and I will concentrate on my projects. My main project is the C blogging platform which is, well, a blogging platform - you didn't see that coming huh?. It's based on the suckless ideology (or at least the way I understand it) and I would really like someone to join me with this. So here's the concept. It's split in to 2 pieces: 1. Uploading and interpreting/caching a post 2. Adding some dynamic code while serving the page (via CGI) 1: I use git (for versioning and easy management). The posts are written in markup. Once you make a new commit, a program (or a script?) is triggered and scans the commit, finds the files altered and either interprets the markup files (smu [1] is used) and store them as html, so you don't have to do that on serve time, or deletes the old cached file. Also, it alters a navigation.html file (used in the second piece) The git integration and the navigation altering is not done yet. 2: Blog preprocessor (bpp [2]). It's a small cgi program that just finds keywords in the asked page and replaces them with file contents. This is used to be able to have a navigation bar and (much later) comment system. so, if you ask for myfile.html (the post that smu has cached), bpp will scan the file for the "==navigation" keyword and replace it with the contents of navigation.html I hope that you get the whole logic. The project has some *serious* security flaws (such as local file inclusion attack and not only), so do not use it yet. Not that you can do anything useful right now, but just saying... :P [1]: http://git.dzervas.gr/smu SMU is not mine. I just forked it from here: https://github.com/Gottox/smu [2]: http://git.dzervas.gr/bpp
