-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Custom location for themes #4137
Comments
@LukasReschke @nickvergessen @icewind1991 @rullzer @karlitschek Do we want this? Generally speaking I don't like to add yet another tweak able folder location. This only leads to more complex testing scenarios and possible corner cases |
I'll try to provide some motivation here. I need to be able to have all the files and directories that are modified by the Nextcloud process itself elsewhere. That is Keeping the Nextcloud installation immutable has some beneftis:
I'm currently writing packaging/configuration for Nextcloud in NixOS which stores package installations as immutable. I want to use the nix package manager for managing the Nextcloud installation/upgrading, thus i need to be able to locate all mutable directories elsewhere. |
Hmm. Well the theme directory is actually not changed by Nextcloud itself. So not sure why this is a critical feature. Saying that: Making a config.php option that enabled to overwrite the theme folder shouldn't be super hard or risky. Pull requests welcome from my perspective :-) |
Yes, the directory isn't changed by Nextcloud itself, true, I was a bit sloppy in my wording. The problem is that it is "mutable": it is modified in order to use new themes, so it's not really part of the core Nextcloud package, which I'd like to keep immutable. Just wanted to know if you supported or were against having a customizable theme location (or if it happened to be possible already). Probably relatively easy task for someone (including me) to tackle and create a pull request. |
You shouldn't really do that..... Anyway, the request sounds fine to me and I tend to agree that there shouldn't be a lot wrong with it. |
As this sounds like a nice feature, the requests for this are quite low. Currently there are no plans to implement such a feature. Thus I will close this ticket for now. This does not mean we don't want this feature, but it is simply not on our roadmap for the near future. If somebody wants to implement this feature nevertheless we are happy to assist and help out. If you wish to have this feature implemented by the Nextcloud GmbH there is the option for consulting work on top of your Nextcloud Enterprise subscription to get your features implemented. |
Currently,
data/
,apps/
andassets/
directories can be given custom locations (datadirectory
,apps_paths
andassetdirectory
). This is good because these locations are mutable, so one might want to keep them outside the actual Nextcloud installation. However, I couldn't find similar configuration forthemes/
directory. It says on the docs:But I couldn't find how to change this default. Perhaps, Nextcloud could support
themedirectory
config value (or, if necessary, an array of paths)?The text was updated successfully, but these errors were encountered: