Actually, you can start a smisk process as a stand-alone (FastCGI)
server. Create this file and save it as process.py:
from smisk.core import *
from smisk.util.main import main
Now, try running the script with --help:
$ python process.py --help
Usage: process.py [options]
-h, --help show this help message and exit
-d PATH, --appdir=PATH
Set the application directory. Not set by default.
-b ADDR, --bind=ADDR Start a stand-alone process, listening for FastCGI
connection on ADD, which can be a TCP/IP address with
out without host or a UNIX socket (named pipe on
Windows). For example "localhost:5000",
"/tmp/my_process.sock" or ":5000". Not set by default.
-c N, --forks=N Set number of childs to fork. Not set by default.
--debug sets log level to DEBUG
You want to start your process.py with at least the --bind argument:
$ python process.py --bind=127.0.0.1:5000
In production, it's a good idea to have your Smisk server(s) managed
by a process manager. If you're on Debian, that means an
init.d-script. On OS X it's a launchd-script, and so on.