@simong at the moment the Snipe-IT package only comes with Cloudron usermanagement integration, so it will always ensure the LDAP settings are bound to the LDAP server on your Cloudron.

If we want to support other external user-management systems, then we have to change the package to support non-Cloudron user management as well.

@hakunamatata Right, the timezone of Cloudron is not "synced" with the timezone settings of the app. The Cloudron timezone is only used for the cron jobs like backups, updates etc.

Ideally, Cloudron could setup the apps to have the cloudron timezone as well but it's very complicated because each app has it's own way of setting up the timezone. Maybe some day in the future!

@girish said in ten thousands sessions files?!:

@imc67 I moved the sessions to redis in the new package.

This seems to work!!! After update there came no more new session files, after half an hour I deleted all session files from folder and no new ons appeared. Also returned to 12000.

It all looks stable and fast!

Thanks @girish !!!

Yup, I have updated the package to 5.0.4 now.

grrr, I don't know what happened but it does work now!

This was the error this morning:

The image is a jpg. Strange to see that the log numbering restarted after this error.

There is no way to configure the backup path in the app (even in the config file). I think it's a laravel convention to use storage subdirectory as writable.

In the Cloudron package, /app/code/storage is symlinked to /app/data/storage. So it's all good. Backups will be persistent.