Stacks autostart, order and delay

[lordraiden]

Is your feature request related to a problem? Please describe

If a VM or a machine is booted for whatever reason, portainer requires manual intervention to run the stacks.
Some staks may require a delay for the autostart and a order to autostart since the stacks might be related to each other.

Describe the solution you'd like

Portainer needs a feature to autostart a stack automatically, if portainer is started and the selected stacks are not. For example in case of machine reboot.
Autostart delay in seconds
Autostart order

Is the only way to properly manage multiple stack that have some relationship between them.

Describe alternatives you've considered

Manually with cron jobs and docker compose commands.

Additional context

No response

[TheMrAnderson]

Most of my stacks have IP addresses set in the env file, but some are temporary stacks for testing different containers I'm developing. When the server is restarted, these temp stacks a lot of times start up before the stacks I want running and consume an IP that another container in another stack is configured to use. I have to login in after a reboot, manually stop stacks and restart containers until everything is happy again.