Cloudron Forum

Thanks, on it!

Oh while I see your package @girish
We fixed the cron issue and you can use the following command now (rather than calling that http endpoint:

php /var/www/html/bin/leantime schedule:work

This is the long running php process so if you have supervisor running that would be better.
Alternatively you can run the following command in a crontab which will execute and exit:

php /var/www/html/bin/leantime schedule:run

Awesome, that was quick!

Hey,
Yeah Leantime 3.4.x requires PHP 8.2

Some more info:
With 3.4 we updated and hardened our dockerfile and docker compose config. Not sure if you all run the docker containers as root or not but if not you can pass in pgid and uid now.

Inside the container Leantime is listening on port 8080 so if the docker compose file still maps to 80 internally that would need to change (external doesn’t matter). The user inside of the docker image is www-data:www-data

With that said old volumes may have the wrong permissions depending on the set up. We added a docker startup script to handle that for most cases but if permissions are off that may not work.

Lastly we tested the setup with various reverse proxy’s and it works in most environnents just make sure that:
A. LEAN_APP_URL is set correctly
B. The host server var is forwarded (ideally just forward any standard host variables)

More on that here https://github.com/Leantime/docker-leantime
And here
https://github.com/Leantime/leantime/releases/tag/v3.4.0

There was an issue with BASE_URL in 3.3.0 but fixed in 3.3.1. Just make sure that LEAN_APP_URL is set as environment variable and that it contains "https://"

@nebulon can you send me an email at marcel [at] leantime.io so I can provide you with some test licenses.

Hi All
Marcel here with Leantime.

I can understand the frustration and I wanted to bring some background on our support abilities:

• 3.2.1 does fix all the plugin issues that were introduced with 3.2. There were several breaking changes that we outlined in our release notes: https://github.com/Leantime/leantime/releases/tag/v3.2.0 one of them requiring the disablement of all plugins before updates.
• We test our releases and offer support for our provided docker-compose environment and "bare-metal installs" on linux. Due to our small size we cannot offer support for installations that fall outside of these 2 scenarios.

Now to the bugs above:

• With 3.2 we moved all of our home grown session management to the much more stable and sophisticted Laravel's handler. With that comes a custom "session" folder that lives in the root of the leantime application. The session folder needs to be accessible by the php executing user of the system.

• Plugins and plugin versions have compatibility listings for each plugin. We know that we need to clean up the validation process so that "Cross version compatibility issues" are caught before installation.
  Please make sure to review the plugin versions before installing.

• Plugins are installed inside of the app/Plugins directory. That folder needs to be mounted to the host so that plugins don't get deleted after a restart.

@nebulon I'll take a look at the command line tool. Which command were you trying to run that caused the error?

Thank you all for your patience as the cloudron team and us will figure out how to improve testing processes.

Hey, Leantime maintainer here. Thought it might be a good time to chime in.
Leantime doesn't do anything special for session handling. So it appears that this would be related to the php config. More than likely it is the combination of.

session.gc_lifetime
session.gc_divisor
session.gc_probability

https://www.php.net/manual/en/session.configuration.php