Question about background tasks workers

[TomHeim29]

Hi !
Until now, I was running clean background tasks with a cron job to run these commands :

/opt/PasswordPusher/bin/pwpush daily_expiration
/opt/PasswordPusher/bin/pwpush delete_expired_and_anonymous

I've just seen the new 1.53.0 release, what does it really change to that ? I did not really understand. Thanks for infos !

[pglombardo]

Hi @TomHeim29 - the latest release just automates the periodic job executions for you. If you don't want the new functionality, you can set PWP__NO_WORKER=true for the pwpush container and no workers will be booted.

[TomHeim29]

Great ! What is the scheduled for the workers to delete pushes ?

[pglombardo]

If you don't have logins enabled, you can't access the admin dashboard. :-( If you do, log in as admin and navigate to /admin/jobs.

The schedule isn't configurable currently. Maybe someday.

[TomHeim29]

Okay, I won't allow login, so workers does not runs for me ? In that case I can let my cron job doing his job ahah

[pglombardo]

No my fault on not being clear. The worker/jobs will run anyways. If you don't have logins, you just can't access the UI - that's all.

So you have the workers/jobs running even without logins.

[TomHeim29]

Okay thanks, np its better in my head now

[TomHeim29]

I have another question, is it possible to disable this button ?

I dont want users to use it because it redirects on a login page, but signups is disable for everyone

[TomHeim29]

Oh nice, thanks :)

[TomHeim29]

Will it be possble to display the "print and share" without being authenticated then ?
I don't really need this button but we never know

[pglombardo]

Yeah I'll just fix the bug. That button will be available to anonymous users.

[TomHeim29]

Okay thanks for your fast reply !

[pglombardo]

Just an update for others coming to this discussion that the fix for this has been released in v1.53.6