Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE REQUEST] Support Multi Instanced Server Configuration #447

Open
stephentoth opened this issue Jan 16, 2024 · 0 comments
Open

[FEATURE REQUEST] Support Multi Instanced Server Configuration #447

stephentoth opened this issue Jan 16, 2024 · 0 comments

Comments

@stephentoth
Copy link

Title's not great.

Personally I have a two server setup with both acting as front ends both syncing with each other to stay current with apps and bookmarks. The way I am doing this right now is super jank. Some of the complexity has to do with flame running in a docker container for convenience (ik, ik).

I think it would be super nice to have at some level support for a configuration as such.

Easiest way I can see to support it is to make the db.sqlite file in its own folder so that that folder can be mounted as a network share without changing anything else about the container configuration.
While this works, it does limit each instance to use the same weather data as its not tagged with location in the db.

For that solution I would say that the db_backups folder should not be in the share, just in case.
About sharing the config.json as well, I would say that that would probably not be practical when differentiating the servers at a glance.

I might make a fork and work out that stuff, but I do want just some thoughts on that idea and if anyone else would like it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant