Worker - Unraid

[blaine07]

How would I add this new worker to an instance of PasswordPusher on Unraid? Just add another container that is the worker or is there anything else special I would need to take into consideration ?

[pglombardo]

Hi @blaine07 - that's correct. Just run it with the same environment settings as the pwpush container. There are no exposed ports required.

Note though that this worker only functions with a shared database (Postgres, MySQL or MariaDB). If using ephemeral, it's no use in that setup.

The worker just runs these periodic background jobs right now.

I'll have documentation in the next week or so.

[blaine07]

Hi @blaine07 - that's correct. Just run it with the same environment settings as the pwpush container. There are no exposed ports required.

Note though that this worker only functions with a shared database (Postgres, MySQL or MariaDB). If using ephemeral, it's no use in that setup.

The worker just runs these periodic background jobs right now.

I'll have documentation in the next week or so.

So, I legitimately shouldn't see any ill effects if I don't immediately spin this up?

[pglombardo]

So, I legitimately shouldn't see any ill effects if I don't immediately spin this up?

Definitely not. It just runs periodic jobs to find pushes to expire.

But also these are the initial releases so there might be occasional errors etc.. but you can watch the output with docker log.

[blaine07]

So, I legitimately shouldn't see any ill effects if I don't immediately spin this up?

Definitely not. It just runs periodic jobs to find pushes to expire.

But also these are the initial releases so there might be occasional errors etc.. but you can watch the output with docker log.

Before this worker how were pushes getting expired and cleaned up?

[pglombardo]

The original design was that people add a cron to run the background tasks.

If those didn't run - then it was lazy deletion. When a push is requested, it's expiration limits are checked before serving. If duration or views are eaten up, then the push is expired and data is deleted there - then you get the "this link has expired" page.

[pglombardo]

Did you have any problems deploying @blaine07? Soon I'll have a dashboard where you can view job executions.

[pglombardo]

A couple of screenshots in #2638

[blaine07]

Did you have any problems deploying @blaine07? Soon I'll have a dashboard where you can view job executions.

I just added it as another container; so far seems fine. It keeps wanting to exit itself/stop itself from running in the middle of the night though for some weird reason; not seeing any errors or anything. Maybe I need to add a "--restart unless-stopped"

[pglombardo]

Ok - yeah that's a good idea. I'll figure out why the workers are dying.

[blaine07]

Ok - yeah that's a good idea. I'll figure out why the workers are dying.

Does this tell you anything?

[pglombardo]

I believe this means that the database container was restarted. Not sure about this one.

The --restart unless-stopped probably would be a good first step and then looking into if the db container was restarted/why.