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

make server/client modularity #5057

Closed
Tracked by #5069
darkskygit opened this issue Nov 24, 2023 · 0 comments
Closed
Tracked by #5069

make server/client modularity #5057

darkskygit opened this issue Nov 24, 2023 · 0 comments

Comments

@darkskygit
Copy link
Member

In different environments, we need different server components. For example, in self-hosted environments, we don't need a payment component but do need a sync component, but in the server environment, we only need the sync component in the synchronization server. Currently, we distinguish loading by server flavor.
A better strategy is to make our server components configurable for loading and be able to tell the front-end what components are enabled on the server. The front end also needs to enable/disable corresponding components based on the configuration of the server to avoid errors caused by requesting unloaded components from the server.
A typical real-world example is Gitlab and Bitwarden; for instance, Bitwarden allows different servers to load different components:
image

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

No branches or pull requests

2 participants