Retro/pcjs
Watch
1
0
Fork
You've already forked pcjs
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update READMEs

Browse source
This commit is contained in:
Jeff Parsons 2014-10-12 10:29:03 -07:00 • committed by jeffpar
commit d375d63646
3 changed files with 8 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

1
logs/.gitignore vendored
View file

@ -1,5 +1,4 @@
*.json *.json
*.log *.log
bugs.html bugs.html
bugs/
users/ users/

21
logs/README.md
View file

@ -1,20 +1,9 @@
Logs Logs
--- ---
This is where Node website activity is logged, and where per-user data is stored (temporarily). This is where Node web server activity is logged, where bug reports are saved, and where per-user data is stored.
Copies of the remote AWS server logs are saved here as well, whenever you run [awsget.sh](../bin/awsget.sh) Per-user data is still in the experimental phase, and is enabled ONLY for users that have requested and received
or [awspush.sh](../bin/awspush.sh). See the [Bin](../bin/) directory for details. their own per-user directory.
Also, to minimize the number of random root directories, I've moved all the per-user data into this folder The website does not use cookies or any other form of user tracking, and Express server logs are maintained only to
as well. [users.log]() contains all the user IDs that are allowed to have per-user machine states and disk help identify problems with the web server.
images on the server.
Per-user support is still in the experimental phase, and security is woefully inadequate. At the very least,
every user should also have a "secret key" (the hash of which would also be stored in users.log), not to mention
login and logout pages, key request and recovery pages, https support, and so on. That's an entire infrastructure
I'm not interested in supporting yet, so for now, the integrity of per-user support relies on the use of
obscure user IDs, and the users of those IDs avoiding open, unencrypted networks.
Storing user data on the same server as the web server is also temporary, because this (or any other folder)
can be completely wiped out every time a new version is pushed to AWS. So we will need a completely different
strategy for preserving per-user data.

3
logs/bugs/README.md Normal file
View file

@ -0,0 +1,3 @@
Bugs
---
This is where the server stores [bug reports](../bugs.html) and machine state files that users have agreed to submit.