Add installation flow

[rijkvanzanten]

This can be done in either of two ways:

Create installation endpoints

The API has an endpoint that can be POST-ed to to create a (new) config file. This means the application can have an installation flow build in that can be used for any api.

Add GUI in the API

When trying to use the api from the browser when there is no config file setup redirects to the install wizard.

There are a few unanswered questions:

• Do we only allow the install wizard for "fresh" installations? E.g. the first config file
• How would the user create additional config files? Manually?
• In case we allow the user to use the same wizard for multiple envs, how do we secure this flow?

[benhaynes]

I prefer option 1... I think it's nice to keep the views and interfacing in the app and allow remote setup of envs. Although, I DO think it's nice to be able to setup a vanilla API without the app (still, that has CLI, right?).

Additional API envs should not require manual configuration. I think there could be a global INSTALL LOCK that prohibits new env installs. Either a _ DB value, or a dedicated file. Any other issues/roadblocks we need to consider?

Definitely need to discuss this one more... warrants a dedicated Meet.

[wellingguzman]

Comment from previous ticket:

A new endpoint for install the API. Allowing the user to set the database, default user and project information.

This endpoint like the install wizard has to be disabled after a successful installation.

In addition to this, I think the API needs to have an endpoint that returns "system status"; e.g. whether or not it has been installed, so the app can render the installation flow accordingly

Note: Throw multiple errors on each installation step. Example, empty database, username and password.

[wellingguzman]

Closed by a1a17f9 and 9220b83

[rijkvanzanten]

Can you add this to the docs @wellingguzman? Just input / output is fine for now, I can write the descriptions later

[wellingguzman]

added here: 805f926