Open ericgaspar opened 3 months ago
!testme
!testme
!testme
!testme
!testme
We're getting there: the LDAP plugin configuration is fixed, and there's a last remaining problem in the upgrade with the files-keeping mechanism...
!testme
@ericgaspar I don't understand why the saved _data
is not a directory in the CI. Installing manually creates a populated _data
directory, and force-upgrading does work...
EDIT: OK, I missed that the upgrade works, and only upgrade from older versions fails (hence my irrelevant tests).
Just tried installing the 13.1.0 commit, and the _data
directory is a symbolic link to /home/yunohost.app/piwigo/_data
, hence the error...
In my understanding:
So... in any way, the data directories are kept during the upgrade, so we shouldn't need to preserve the corresponding ones in the install dir (not used) during the upstream source uncompressing (revert from that change). And it should also fix the remaining "upgrade from older version" tests
@ericgaspar Does that sound legit...?
To be honest, I don't remember exactly what the issue was on the Master branch... something to do with images not showing up due to symlinks not working.
This PR removes the use of data_dir
in favor of the install_dir/(_data, galleries, uploads)
location.
That being said, I'm not sure if this is the right strategy and if upgrading won't wipe out existing data...
Ah I see the analysis in https://github.com/YunoHost-Apps/piwigo_ynh/issues/128#issuecomment-2156085035
Then, a potentially simpler/less risky solution couldn't be to configure the data_location
and upload_dir
settings in the app with a relative path (i.e. ../../..__DATA_DIR__
)...?
EDIT: ah ok. I understand. I commited #142. the _data, galleries, uploads
files were created in the data_dir
location and $conf['data_location'] = '../../..__DATA_DIR__/_data/';
is added to the config file. Let's see if that does the trick
!testme
Is that branch ready for larger testing (I have no personal instance using piwigo)...?
I haven't installed Piwigo myself, but yes, it's ready for worldwide testing!
Problem
Solution
PR Status
Automatic tests
Automatic tests can be triggered on https://ci-apps-dev.yunohost.org/ after creating the PR, by commenting "!testme", "!gogogadgetoci" or "By the power of systemd, I invoke The Great App CI to test this Pull Request!". (N.B. : for this to work you need to be a member of the Yunohost-Apps organization)