I'm still working on getting authentication working. Have you succeeded in getting things working without authentication? I'd do that first to be sure you are serving files as expected.
Without authentication, my settings.json file looks like:
{
"tree": "D:/Dropbox/tw",
"bindInfo": {"http": "./https.js", "port": 8081, "bindWildcard": false, "bindAddress": ["127.0.0.1"]},
"putsaver": {"backupFolder": "./backups"},
"$schema": "./settings-2-1.schema.json"
}
That's if you just want to bind to your local network card and run the server local using
http://localhost:8081/.
If you want to run it on your pc yet connect to it from anywhere in your network then you need wildcard binding like these next settings. This one is also for HTTPS which takes even more set up because you need certificates so, while it is less secure, you could drop the "s" until you get things going.
{
"tree": "D:/Dropbox/tw",
"bindInfo": {"https": "./https.js", "port": 8081, "bindWildcard": true},
"putsaver": {"backupFolder": "./backups"},
"$schema": "./settings-2-1.schema.json"
}
Get all that working then you can start building that authentication pieces. I'm still working that out but I believe once you get the above working you next start the authentication piece by going to
http://localhost:8081/admin/authenticate/login.html and you'll be prompted with a username and password field. Just try it with whatever user name and password you'll be using later. It will fail but on the tiddlyserver console you'll see something like:
login attempted with unknown public key
M2Kl7Fp9KetobcSwA491fmmZkecXhUYH-omojNehImQ
username: skingery
timestamp: 2020-01-13T05:36:50.662Z
Given those results you then build out the client key section of settings.json like:
"clientKeys": {
"skingery": { "publicKey": "M2Kl7Fp9KetobcSwA491fmmZkecXhUYH-omojNehImQ", "cookieSalt": "1024" }
},
That's about as far as I've gotten on the authentication side so I look forward to hearing from others.