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

Change configuration hint on admin page #25963

Closed
tflidd opened this issue Aug 29, 2016 · 5 comments
Closed

Change configuration hint on admin page #25963

tflidd opened this issue Aug 29, 2016 · 5 comments

Comments

@tflidd
Copy link
Contributor

tflidd commented Aug 29, 2016

If the data/-directory is accessible, the admin page will show this advice:

We strongly suggest that you configure your web server in a way that the data directory is no longer accessible or you move the data directory outside the web server document root.

The problem is that we do not support moving the data directory:
owncloud-archive/documentation#2303

@PVince81
Copy link
Contributor

Right... the only moment when it's ok to move the data directory is directly after the install, before any user data has been written.

@tflidd
Copy link
Contributor Author

tflidd commented Aug 29, 2016

Unfortunately, it is quite popular to change the data-directory and many point like this indicate that it is possible. Is there a way to make it possible? We could check in database, which apps use the absolute path so it can be fixed there (either don't use it from the database at all or provide an occ-command to allow a migration).

@PVince81
Copy link
Contributor

It is not directly possible, because after moving the data folder, ownCloud has no way to know what the old folder was. And oc_storages is a big mess, we can't directly trust which paths it uses.

Now thinking of it, maybe if there was an "occ" command "occ maintenance:migrate-data-folder /path/to/target" it could take care of changing everything that's needed.

@PVince81
Copy link
Contributor

Closing in favor of #25970

@lock
Copy link

lock bot commented Aug 3, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants