-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Apps should be able to register custom domain #27473
Comments
Honestly, I don't think that this feature request is feasible. |
Yeah, that's out of scope |
Hi all, Also, I forgot to say that there is also a redirect required through the update of the htaccess setup in Nextcloud also. The below is the HTACCESS update to the existing HTACCESS already available in the /nextcloud/ folder. Obviously if this solution works I am likely to take this route, but if not I might go for a headless CMS solution instead, and there are few I am testing out.
|
How to use GitHub
Is your feature request related to a problem? Please describe.
When i I use PicoCMS, I want to add a custom url (CNAME for eg) for a site using automatic configuration, means i must technically know what config in what file i must edit and i have to know if it affect any automatic (Nextcloud image based on ubuntu core/snap) updates. I feels i can't be 'just' a user, but a sysadmin.
Moreover you currently have to add the CNAME in the trusted hostname of Nextcloud while i'm sure we could dodge this.
Describe the solution you'd like
Provide for apps (in my case PicoCMS for Nextcloud) a way to add sub route of the node to be join-able by another (sub/parent)domain name; and it won't break with any update or anything unsecure would happend (it's better if it is done by upstream rather anyone do something manualy).
I didn't find another apps that need this, but i guess we could see new apps appearing such as:
share.my.dn
/fileIDlinkto.my.dn
/CustomUrlme.my.dn
/usernameBasicly the custom CNAME would be an alias to
index.php/apps/app_name/optionnal_subfolder
. The optionnal_subfolder is important for the PicoCMS app for Nextcloud.And an app could register many CNAME (especialy in the PicoCMS case, see 'additional context'), not just one, so it's not just a manifest file in the build of the app file I think, but a callable thing.
Describe alternatives you've considered
I don't have alternative, except a suggestion like it doesn't need to be working on all kind of Nextcloud installation (at least, in the beginning). for example, it could support at first, the snap/ubuntu core image since all the settings are known in the Nextcloud context.
I think apps should not themself modify the settings, but apps could ask Nextcloud to do so. Nextcloud could say no if the setting are not on its control (for eg: a custom install environment) or because it is in conflict (this app or another already registered a path with this domain).
Edit: an alternative would be (could be temporary or not) having a documentation section about how to do this manually. The snippets that can be found on this topic for nextcloud are often partial, not working, not suggesting to backup the original/current and working config file, and impacts of doing it; and moreover they do not even name the files themselves and their path. I guess having a howTo for nextcloud on snap/ubuntu core image would be a great start ?
Additional context
nextcloud.my.dn
my.dn
blog.my.dn
sudo nextcloud.enable-https lets-encrypt
and typingnextcloud.my.dn my.dn blog.my.dn
at the domain list prompt, will works. (I'm almost sure we could open a new issue feature request to have this callable from the admin panel, with hooks to apply it everytime a domain is added, or even safer, push a notification to make the admin confirm/adjust the list of domain before)PS: Thank you for all the work that has been done from all the Nextcloud and apps contributors. Really.
edit: typos
The text was updated successfully, but these errors were encountered: