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

Cluster config.php flag #16372

Open
rullzer opened this issue Jul 12, 2019 · 3 comments
Open

Cluster config.php flag #16372

rullzer opened this issue Jul 12, 2019 · 3 comments
Labels
1. to develop Accepted and waiting to be taken care of enhancement

Comments

@rullzer
Copy link
Member

rullzer commented Jul 12, 2019

I ran into this several times. But if you have a cluster of Nextcloud nodes it would be good if we could set a config.php setting for this.

This could then disable installing apps from the appstore for example (it could still check for updates just not allow you to install anything).

It might be usefull in other places as well but this is the most prominent place.

@skjnldsv skjnldsv added the 0. Needs triage Pending check for reproducibility or if it fits our roadmap label Aug 20, 2020
@szaimen
Copy link
Contributor

szaimen commented Jun 8, 2021

I thought multiple config.php files are already possible? Or is this something else?
cc @kesselb on this

@ghost ghost added the stale Ticket or PR with no recent activity label Jul 8, 2021
@kesselb
Copy link
Contributor

kesselb commented Jul 8, 2021

I guess it's about a flag for config.php like:

'cluster' => true,

To disable some features if Nextcloud is running as cluster (=> more than one application server). In such a configuration the database is usually shared but the application code not. Each node runs a own copy of Nextcloud and apps. If you trigger an app update the app code is updated on the application server your are currently using. As the database is shared the other application servers run an outdated app which might be incompatible due changes to the database.

@ghost ghost removed the stale Ticket or PR with no recent activity label Jul 8, 2021
@szaimen
Copy link
Contributor

szaimen commented Jul 14, 2021

Thanks for the explanation!
And is this feasible so that I should add 1. to develop to this ticket?

@ghost ghost added the stale Ticket or PR with no recent activity label Aug 13, 2021
@ghost ghost closed this as completed Aug 27, 2021
@kesselb kesselb removed the needs info label Sep 8, 2021
@kesselb kesselb reopened this Sep 8, 2021
@ghost ghost removed the stale Ticket or PR with no recent activity label Sep 8, 2021
@nextcloud nextcloud deleted a comment Sep 8, 2021
@nextcloud nextcloud deleted a comment Sep 8, 2021
@szaimen szaimen added 1. to develop Accepted and waiting to be taken care of and removed 0. Needs triage Pending check for reproducibility or if it fits our roadmap labels Sep 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. to develop Accepted and waiting to be taken care of enhancement
Projects
None yet
Development

No branches or pull requests

4 participants