A request to /someboard/ will have nginx try to read the cache in /data/html/someboard/index and if doesn't exist, the backend will generate it from scheme code in /data/sexp/someboard/index
So if you want to have board1 and board2 in your textboard, you need to (manually) create those directories
/data/sexp/board1/
/data/html/board1/
/data/sexp/board2/
/data/html/board2/There's no automated index of boards but that's trivial to implement. Neither is there an automated procedure to generate those directories. I had a very short time ahead of me to finish the program and really halted the development as soon as I had something working. (I'm living a weird life right now, with very few opportunities to use an internet connection at all)
The relevant parts of nginx.conf would be:
upstream http_backend {
keepalive 20;
server 127.0.0.1:8080;
} server {
listen 80;
server_name textboard.org www.textboard.org;
location / {
root $prefix/data/html;
default_type text/html;
index index;
try_files $uri $uri/index @schemebbs;
location @schemebbs {
proxy_pass http://http_backend;
}