[DiscordArchive] Ctrl+c isn't meant for production. Why change something which serves a different purpose than what t
[DiscordArchive] Ctrl+c isn't meant for production. Why change something which serves a different purpose than what t
Archived author: Honey • Posted: 2023-01-13T15:15:46.763000+00:00
Original source
Ctrl+c isn't meant for production. Why change something which serves a different purpose than what the change aims at?
Archived author: Foe • Posted: 2023-01-13T15:28:59.729000+00:00
Original source
Ctrl+c should most definitely be considered production use
Archived author: Foe • Posted: 2023-01-13T15:29:08.376000+00:00
Original source
This is industry standard
Archived author: mynameismeat • Posted: 2023-01-13T15:29:19.121000+00:00
Original source
It's not the ctrl+c that matters - it's the SIGINT that it sends
Archived author: Foe • Posted: 2023-01-13T15:29:34.009000+00:00
Original source
Sure, sigint I should say
Archived author: mynameismeat • Posted: 2023-01-13T15:29:35.995000+00:00
Original source
`docker compose down` sends a SIGTERM, as well, which would result in an unsafe shutdown
Archived author: Foe • Posted: 2023-01-13T15:29:39.685000+00:00
Original source
Which is what Ctrl c sends
Archived author: Foe • Posted: 2023-01-13T15:30:08.216000+00:00
Original source
Like you say, the default os level signaling is what's used for any production environment anywhere
Archived author: mynameismeat • Posted: 2023-01-13T15:30:16.127000+00:00
Original source
but otherwise yeah, ctrl+c is used in production pretty much universally
Archived author: Foe • Posted: 2023-01-13T15:30:35.043000+00:00
Original source
This should most definitely be safe to use without the risk of data loss