Servers for webapps

This is about programs that manage the communication for web applications. they are called "server programs" as well; they reside as it were behind the web server, which effectively functions as a kind of pass-through window. Here too we have mainly stop and (re)start functions.

Cherrypy

  • fabsrv cherrypy.restart [<name(s)>]

  • fabsrv cherrypy.start [<name(s)>]

  • fabsrv cherrypy.stop [<name(s)>]

  • fabsrv cherrypy.list-servers - this produces a list of Cherrypy server names

Django

  • fabsrv django.restart [<name(s)>]

  • fabsrv django.start [<name(s)>]

  • fabsrv django.stop [<name(s)>]

  • fabsrv django.list-servers - this produces a list of Django server names

To facilitate using the Django admin CSS I made this command:

fabsrv django.link-admin-css [<name(s)>] [--force]:

It creates a symlink to the admin directories. When moving to a different major version of Python the location changes, which is why I made the next command:

fabsrv django.check-admin-links

This checks whether the symlinks to the admin stuff need to be updated.

Hgweb

This provides the possibility to view Mercurial repositories using a web interface, comparable to gitweb or cgit - which means it can be used for the document collections in rst2html-data.

  • fabsrv hgweb.restart

  • fabsrv hgweb.start

  • fabsrv hgweb.stop

Plone

This was an experiment with a Python CMS; I don't use this anymore because I'm just not that into CMS-es anymore

  • fabsrv plone.restart

  • fabsrv plone.start

  • fabsrv plone.stop

  • fabsrv plone.buildout - for the configuration, as of Plone 5 or 6 not needed anymore

Trac

  • fabsrv trac.restart

  • fabsrv trac.start

  • fabsrv trac.stop

  • fabsrv trac.editconf - alias for fabsrv editconf trac

  • fabsrv trac.modconf - alias for fabsrv modconf trac