You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I want to prevent some of the included services from restarting infinitely in case of a mis-configuration. I tried process-managers.process-compose.settings.availability.max_restarts and processes.postgres.process-compose.availability.max_restarts; but neither seem to be working... I tried loading my flake in the repl and looking at outputs.devShells.x86_64-linux.default.config.processes.postgres.process-compose.availability, but it just shows the defaults.
Is this possible? Did I misunderstand how to configure it? I asked over on discord but no answer.
To reproduce
Here's a fresh flake.nix with enough to make postgres fail infinitely.
Describe the bug
I want to prevent some of the included services from restarting infinitely in case of a mis-configuration. I tried
process-managers.process-compose.settings.availability.max_restarts
andprocesses.postgres.process-compose.availability.max_restarts
; but neither seem to be working... I tried loading my flake in the repl and looking at outputs.devShells.x86_64-linux.default.config.processes.postgres.process-compose.availability, but it just shows the defaults.Is this possible? Did I misunderstand how to configure it? I asked over on discord but no answer.
To reproduce
Here's a fresh flake.nix with enough to make postgres fail infinitely.
Version
1.1.0
The text was updated successfully, but these errors were encountered: