|
30 | 30 |
|
31 | 31 | ## Version 6 |
32 | 32 |
|
| 33 | +### v6.9.2 |
| 34 | + |
| 35 | +Released on Sep 19th, 2025 |
| 36 | + |
| 37 | +#### Minor fixes |
| 38 | + |
| 39 | +Small release that should improve the handling of using Lychee in a "subfolder" setup (e.g. `example.com/lychee`). |
| 40 | +Note that this is **not a recommended setup** for security reasons as you will likely be leaking your logs _et al._ |
| 41 | +without further hardening your installation. |
| 42 | + |
| 43 | +**We strongly recommend you use a subdomain instead (e.g. `photos.example.com`).** |
| 44 | + |
| 45 | +* `new` #3673 : Add documentation on how to add Oauth providers by @ildyria. |
| 46 | + > We added a small section in our repository to explain how to add Oauth providers. |
| 47 | + > This is not something that is visible to our users, but more of a developer/contributor documentation. |
| 48 | +* `new` #3684 : Add move to S3 command by @ildyria. |
| 49 | + > A small request but with big impact. If you decide to move your photos to a S3 compatible storage, |
| 50 | + > you no longer need to re-upload all your photos/create a new Lychee instance or other work around. |
| 51 | + > You can now use the command `php artisan lychee:s3_migrate`, it will move your photos to the set up S3 storage. |
| 52 | + > Note that we do not recommend doing this if you use "live photos" as those have slightly different handling and won't be handled properly. |
| 53 | +* `new` #3694 : Allow to disable import from server from server side by @ildyria. |
| 54 | + > This is a security measure. If you do not want your users (admin & owner included) to be able to use the import from server feature, |
| 55 | + > you can now disable it via the `.env` file by setting `DISABLE_IMPORT_FROM_SERVER=true`. To preserve backward behaviour, this is set to `false` by default. |
| 56 | +* `fix` #3696 : Fix subfolder duplicate path behaviour by @ildyria. |
| 57 | + > When using Lychee in a subfolder setup (e.g. `example.com/lychee`), we had feedback that the setup was no longer working as expected. |
| 58 | + > While we do not recommend this setup, we still aim to help our users. This fix should improve the handling of this setup. |
| 59 | + > As a reminder, you will need to set the `.env` variables `APP_DIR` and `APP_URL` accordingly: for `example.com/lychee/public`, it should be |
| 60 | + > `APP_DIR=/lychee/public` and `APP_URL=https://example.com`. |
| 61 | +
|
| 62 | + |
33 | 63 | ### v6.9.1 |
34 | 64 |
|
35 | 65 | Released on Aug 31, 2025 |
|
0 commit comments