Configure Index Backend and Tracker from Frontend

[BelieveInBunny]

(edit @da2ce7)

• Prompt for creating a new administrator account, if missing.
• Prompt to review and change the backend and tracker configuration on first load.

(original: @BelieveInBunny ):
Torrust needs at least one administrator account. On first boot it should show an install wizard to create an admin account and to set the tracker/website config.

[josecelano]

(edit @da2ce7)

• Prompt for creating a new administrator account, if missing.
• Prompt to review and change the backend and tracker configuration on first load.

(original: @BelieveInBunny ): Torrust needs at least one administrator account. On first boot it should show an install wizard to create an admin account and to set the tracker/website config.

Hi @BelieveInBunny , right now, this is what's implemented:

• The first registered used is an amdin
• There is only one admin
• There are only two roles: admin and the standard user. And guests (unauthenticated users).

Regarding the tracker and website config, you can change the settings on the admin panel:

But it's something I do not like because of the following:

• Potential inconsistencies updating settings torrust-index#161
• Configuration is read-only when env var is used torrust-index#144

I would add a new table, settings with all the configuration the admin can update.

Regarding changing the tracker configuration from the frontend, first we should decide which is the role of the tracker. See torrust/torrust-index#186

Is the tracker only an associated/linked tracker to the index, or it's an independent service
e you can connect to from the index? Are we going to have more than one tracker in the future?

I think we have to answer all those questions before implementing a solution to make installation and configuration easier.