Add support for external MySQL instances about oncall HOT 7 CLOSED

We added this task to the core team's backlog.

from oncall.

@Matvey-Kuk Discussed UX-side for this task with @vadimkerr. Probably will be good to provide some context in OnCall settings. Maybe just as links to documentation.

from oncall.

@raphael-batte are you talking about "Settings" page or "Env Variables"?

from oncall.

@Matvey-Kuk probably Settings is more right place for such information

from oncall.

@raphael-batte why? As well as I understand the "Settings" page is about in-app level settings. While MySQL configuration is a 100% deployment information. We cover it in our docs. We also don't share information about helm, docker, redis, rabbit, celery, engine in the "settings" page so not sure why "MySQL" is an exception.

from oncall.

I guess @WarriorXK wants to use the external database In the hobby (docker-compose) setup.
This is really easy to achieve by removing mysql service from docker-compose.yaml and adding variables MYSQL_HOST, MYSQL_USER, MYSQL_PASSWORD into .env_hobby file (step 2 of readme):

echo "DOMAIN=http://localhost:8080
MYSQL_HOST=<your host>
MYSQL_USER=<user>
MYSQL_PASSWORD=<password>
SECRET_KEY=my_random_secret_must_be_more_than_32_characters_long
RABBITMQ_PASSWORD=rabbitmq_secret_pw
MYSQL_PASSWORD=mysql_secret_pw
COMPOSE_PROFILES=with_grafana  # Remove this line if you want to use existing grafana
GRAFANA_USER=admin
GRAFANA_PASSWORD=admin" > .env_hobby

We can also make this solution more universal and move mysql service under the profile, as we do for grafana (e.g. COMPOSE_PROFILES=with_grafana, with_mysql), which will make mysql opt-in service

from oncall.

@iskhakov I think for hobby usage your answer here is a solution so closing the issue ☺️

from oncall.