Note: This guide assumes you are running a standard Debian or Ubuntu Linux distribution on the machine on which you'll be hosting the SNApp. This guide also assumes you are relatively familiar with using the command line.
lokinet.inifile and adding a path to where your SNApp key files will be stored.
lokinet.inifile in the
nanotext editor with the following command:
lokinet.inifile will be in the folder
~/.lokinet/lokinet.ini, and can be opened in
nanowith the following command:
lokinet.iniopen in the text editor, scroll down to your
[network]section and add the following line:
<user>with your computer username. Alternatively, you can set the filepath to wherever you want your SNApp private key to be stored.
snappkey.privatefile in the directory you have set.
hostcommand (the .loki address to query is the same, but the resolver uses the address
127.3.2.1as to not conflict with other resolvers you may have installed):
nginxto run only on the lokinet interface (in
listendirectives to use the lokinet IP, and remove any IPV6
/var/www/htmlto serve them as a SNApp. Make sure they are accessable via the
www-datauser (or whichever user
nginxgenerate a directory listing by adding
autoindex on;into the
locationblock in the nginx config file.
[network]add one or more entries with the following format:
mylokiaddress.lokiat port 1234.
.), which means "this SNApp does NOT have that service available"