Create individual user accounts instead of sharing ocdskfp

[jpmckinney]

Presently, unless analysts are diligent in naming and organizing files and directories and tmux sessions to include their name, it takes some effort to determine to whom files and sessions belong. If each user had their own account, this would be easy without extra steps.

Since we changed how users interact with Scrapyd, the only remaining use case for ocdskfs is to read the Scrapyd log files from the command-line. However, the files are world readable, so any user can access these.

The ocdskfp user is presently used to activate a virtual environment and run Kingfisher Process and Views commands. We can look into a different deployment pattern so that individual users can run these commands without having multiple instances of the apps.

[jpmckinney]

• Similarly, can create individual accounts instead of sharing scrape htpasswd access.

[jpmckinney]

ocdskfs was already no longer shared (no authorized_keys argument in its create_user macro call).

[jpmckinney]

@RobHooper On the new server, Kingfisher Summarize will have a command-line tool at /home/summarize/kingfisher-summarize/manage.py

Instead of giving everyone access to the summarize user, I'd like each person to have their own accounts.

The manage.py file is world-executable by default. However, it needs to read the owner-readable-only ~/.pgpass file. It also reads the current user's ~/.config/kingfisher-summarize/logging.json file.

I don't know enough about sudo configuration, but is there a way to allow other users to run manage.py as if they were the summarize user (and read those files)?

---

Update: I guess another option is to set each user's .pgpass file (handy for the user, so they don't need to enter their password when logged in). I think the only remaining issue is that Summarize will try to read the wrong logging.json file.

I'll think about adding an option that sets a fixed path for that file.

Edit: Okay, that's what I did. Nevermind!

[jpmckinney]

Issue open as have to document how to run Kingfisher Process as a non-owner.

[jpmckinney]

Added documentation to bullet list in #402