Skip to content

Framework

Timothy O'Connell edited this page Sep 6, 2016 · 1 revision

Stack

The application stack and request workflow is simple:

  • Ubuntu LTS is the production OS, but any Debian-based Linux will do.
  • Nginx is the webserver.
  • Nginx proxies web requests to a hand-written python CGI server.
  • The CGI server routes requests to a script called index that process http POST parameters (and cookie info) according to rules laid out in a number of modules.
  • HTML views are rendered in response to POST parameters.

...and that's about it.

Why no Frameworks?

To put it simply (and maybe a little bit obnoxiously), I've worked with a lot of perl and python web frameworks and they all have the same problem: they sweep a lot of the interesting bits under the rug in the name of convenience.

Most of the time this doesn't matter, of course, and, truth be told, if this was a work or other professional project, I would almost certainly be using eve or flask (probably not Django: the maintainers have gotten sort of...off-mission in the last couple major releases, if you ask me).

But this isn't a work-related or professional project for me, and one of my personal goals in starting it was to learn more about the nuts and bolts--the interesting bits--of serving web apps and so, until I decide to change directions, the Manager is a "first principles" project, where I micromanage the tedious nuts and bolts bits.

Clone this wiki locally