search

SchokkerIT / GameDash

Official repository for the GameDash project
21 stars 0 forks source link

Allow Use of Own Databases #6

Open aleforge opened 4 years ago

aleforge commented 4 years ago

As a GameDash customer, I do not want to be locked into using a database container and be able to utilize the database infrastructure I already have.

Solution: During setup ask if customers want to use their own Database then collect the following information: Hostname/IP Port Direct all Gamedash backend SQL queries to this endpoint.

imtomjorge commented 4 years ago

+1, so useful for load-balanced services

Jesse-Schokker commented 4 years ago

You can already add your own databases by editing the backend config file. Will add it to the setup procedure at some point as a QOL.

AlthalusAvan commented 4 years ago

I'd suggest that adding it to the setup procedure may not be necessary. Those using their own databases aren't likely to be the same people using a one-click setup for the main panel anyway - particularly when load balancing / HA is the objective.

If it's trivial to add the info to the install script it may make sense just as a QOL thing (as long as you then don't run the database container, otherwise resources are being waster), but it may be a better use of time to instead document a manual (or at least not one-line) setup method.

For HA / load balancing, a concern is going to be that there are several micro-services running here - the load balancer, frontend, backend, relay, Redis layer and database are all separate items - so any HA setup will have a lot more to consider than just custom databases.