acrolink
What is the best way to stop a Pheonix application from within a bash script? I have the PID of the process, how to stop it in a safe manner (i.e. giving it the time it needs to process fully current requests / database transactions)?
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
bryanhuntesl
You could try integrating this : GitHub - lyokato/the_end: Elixir Library: provides a graceful shutdown support for your Phoenix, or plain Plug application · GitHub
Build a release using distillery
Create a custom handler script - and configure for the release
Then invoke the handler script when you want to achieve a graceful shutdown.
For bonus points you could implement a POSIX signal handler using something like tsutsu/signal_handler - or roll your own - and have it invoke your hander - this would also have the advantage you could just send a kill signal to the Elixir process (in the operating system sense of the word).
acrolink
@bryanhuntesl Thank you, I appreciate your suggestion and I will try to implement it later. In the meantime, I am doing it like this:
kill -s TERM $(lsof -t -i :4060 -s TCP:LISTEN)where4060is the port used by thePhoenixapplication.bryanhuntesl
Ah that’s much easier - just create a release using distillery (or whatever) and execute it’s stop / start commands - things get weird between the different operating system flavors - and distillery does not just send an OS signal - it actually connects to the node and invokes a purpose built shut-down command -
bryanhuntesl
Here’s the top level implementation of what it does - i.e. it does all that stuff - then finally invokes the OS level kill - distillery/priv/libexec/commands/stop.sh at b945641ebbc17848378f4cd0f1c116ec78326ad4 · bitwalker/distillery · GitHub
Really building releases is the way to go