Improve (Agent) set-up for self-hosted atomic-server

[joepio]

If you want to run your own atomic-server you have to create an Agent. This involves checking logs, or worse, entering your docker volume and getting a value.

I'd rather have a simpler solution to this, but I don't know what.

Use desktop GUI

I could have a tray icon item that opens the config.toml.

Use a fully deterministic secret

Instead of

Have an 'initial setup' route + endpoint in data browser

When the server knows the initials setup has not been done, the server opens at localhost/app/setup. Here, a new Agent is created using a virtual Invite for the root Drive. This will grant all permissions.

Maybe the default_agent should not be the main agent, but the server itself. This could be a different agent from the first actual user opening the server app.

Maybte the app/setup should be a URL for the first invite. I think it would be elegant if it was simply an Invite resource - not something fancy.

Maybe the drive URL (the base URL) should be an Invite resource? That seems elegant...

[joepio]

I've opted for an easy (possibly temporary) approach: on init, create a /setup resource, which is an invite to the main Drive. This can only be used once.