NodeJS v.11.0 +
$ npm install -g sundry
Sundry relies on several configuration values, all of which can be provided in two ways.
You can generate a skeleton config by running...
$ sundry config build
This will create ~/.sundry/, ~/.sundry/ssl and ~/.sundry/config.json
Sundry uses some generic files for its default host, 404 and 500 error pages.
You can override any of these by placing the correctly named file in
~/.sundry/html/<index/404/5xx>.html
$ sudo adduser --disabled-password sundry
$ sudo su -- sundry
$ sundry config build
$ sudo apt-get install authbind
$ sudo touch /etc/authbind/byport/80 /etc/authbind/byport/443
$ sudo chown sundry:sundry /etc/authbind/byport/80 /etc/authbind/byport/443
$ sudo chmod 755 /etc/authbind/byport/80 /etc/authbind/byport/443
$ sudo touch /etc/init/sundry.conf
$ sudo <vi/emacs/nano/ed> /etc/init/sundry.conf
# no flame wars here
description "Sundry Dynamic Router"
author "PaperElectron"
start on (local-filesystems and net-device-up IFACE=eth0)
stop on shutdown
# Automatically Respawn:
respawn
respawn limit 5 60
script
export HOME=/home/sundry
export NODE_ENV=production
exec start-stop-daemon --start -u sundry --exec /usr/bin/authbind sundry start
end script
Browsers will flag this as an insecure certificate.
$ cd ~/.sundry/ssl
$ openssl genrsa -out key.pem 2048
$ openssl req -new -key key.pem -out server.csr
$ openssl x509 -req -days 365 -in server.csr -signkey key.pem -out cert.pem
$ claude mcp add Sundry \
-- python -m otcore.mcp_server <graph>