-
Notifications
You must be signed in to change notification settings - Fork 67
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
Command to change the data directory doesn't work #674
Comments
hi!
it's because the docs explain the app provisionning, which occurs before the install/upgrade/restore scripts there is no data moving where you're changing it's path using the |
@OniriCorpe Thank you for youre answer, |
@Alexis-IMBERT there is a typo in the command: this is |
Hi @niko2 thank you for notice that, What could be the step to produce a generic script that change the data folder of Nextcloud |
And I just notice that if we do an upgrade of the app : sudo yunohost app setting nextcloud data_dir The data folder come back to the default one : sudo yunohost app setting nextcloud data_dir
/home/yunohost.app/nextcloud
|
Yes, you can refer to #675 |
I made a symbolic link and it seems to work (I could do the upgrade to the latest version of nextcloud) |
@niko2 thank you for your test ! Did you do a symbolic link (ls -s ) or a bind mount (mount --bind) ? |
as I said, a symbolic link ( |
I tested it too on my server, |
Closing because the original issue seem to be addressed and there are followup PRs |
Describe the bug
The following command to change the data directory of an app doesn't work properly :
The command was suggested in this thread to change properly the data directory of Nextcloud and not break fail2ban.
In the documentation here, it say that if the directory exist, the data are moved and if it doesn't, it will the directory is created.
But I try it on my server (new clean install) and it doesn't moved the data, the new directory still doesn't exist...
However, the result of the following command change from the default path to the new one :
Context
yunohost app info $app_id
Steps to reproduce
Expected behavior
The solution could simply be an explanation of how to change the data directory properly (it's really relevant for using get Nextcloud on an bigger drive space than the one of Yunohost is running)
The best option will be a new configuration option on the web administration
PS : With explanation on what to do, I will be pleased to help on the development of this feature
Thank you of your help and investment
The text was updated successfully, but these errors were encountered: