Refactor supervisor config

[leepeuker]

No description provided.

[leepeuker]

@JVT038 I made a few adjustments extending your proposal. what do you think?

[JVT038]

I looked at your changes and they seem fine to me.

The only thing I'm concerned about is the order of the supervisor processes; If there's a job schedules which depends on a migration, then we have to make sure that the migration is ran before the job processor starts running.

I just pushed a commit which sets the priority and ensures that the migrations are executed before the jobs.

[leepeuker]

I looked at your changes and they seem fine to me.

The only thing I'm concerned about is the order of the supervisor processes; If there's a job schedules which depends on a migration, then we have to make sure that the migration is ran before the job processor starts running.

I just pushed a commit which sets the priority and ensures that the migrations are executed before the jobs.

hm, the priority only decides the order of starting the processes, so this does not really solve the issue in general, especially if the migrations takes a few seconds or longer. but I do not think we can solve this issue really via supervisor, this is not what supervisor was meant to do.

[JVT038]

You might be right, but I'm pretty sure that if a job fails, the job will just be restarted 15 seconds later right? So we can also just keep it the way it is, and hopefully no issues regarding the process order will occur lol.

[JVT038]

I think we should just YOLO merge this and we'll eventually find out if something is wrong lol