"onboarding" process - Githubissues

ccs-amsterdam / amcat4

API server for AmCAT4 Text Analysis

GNU Affero General Public License v3.0

4 stars 2 forks source link

Closed vanatteveldt closed 1 year ago

vanatteveldt commented 1 year ago

Currently the new user experience is a bit disappointing, requiring command line action to create an admin user and getting a 404 on the / endpoint.

It would be great to:

Store some basic config (where is my elastic? what authentication scheme do we use?) in a config file
Have some sort of onboarding to fill in the config details in the web browser if it doesn't exist
Have a somewhat informative / endpoint, at least to acknowledge that it exists and a link to a hosted client?

vanatteveldt commented 1 year ago

Current proposal:

Configuration, including an optional special admin password, is in environment variables / a .env file
We add a simple /admin web interface for managing the config
on first launch of an amcat instance, unless disabled in the config, the user is greeted by the admin screen to setup e.g. elastic host, authentication model, etc

vanatteveldt commented 1 year ago

We decided to use the CLI config command, and with default no_auth it should be a lot easier.