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
I was able to get gatling setup with little fuss (which is sweet!) but being new to Erlang, Elxir, and Phoenix I'm at a little bit of a loss for how to perform some administrative tasks on the server.
I think it'd be useful for people like me to know the how to run the Phoenix equivalents of the Rails world's:
tail -f log/production.log
rails console
rails runner "Model.long_running_command"
I'm digging around and will be happy to submit a PR to the docs once I figure this out, but some best practice guidance would be appreciated!
The text was updated successfully, but these errors were encountered:
I'm still struggling with a runner equivalent. sudo service [app_name] has a few promising-looking options: escript, rpc, eval, and command. I tried a ton of variations with these but couldn't get anything to work (e.g., command throws "shift: can't shift that many" errors for anything I throw at it). Are these supposed to be given Erlang code, not Elixir code?
echo "escript <file> # execute an escript"
echo "rpc <mod> <fun> [<args..>] # execute an RPC call using the given MFA"
echo "rpcterms <mod> <fun> [<expr>] # execute an RPC call using the given Erlang expression for args"
echo "eval <expr> # execute the given Erlang expression on the running node"
echo "command <mod> <fun> [<args..>] # execute the given MFA"
I was able to get gatling setup with little fuss (which is sweet!) but being new to Erlang, Elxir, and Phoenix I'm at a little bit of a loss for how to perform some administrative tasks on the server.
I think it'd be useful for people like me to know the how to run the Phoenix equivalents of the Rails world's:
tail -f log/production.log
rails console
rails runner "Model.long_running_command"
I'm digging around and will be happy to submit a PR to the docs once I figure this out, but some best practice guidance would be appreciated!
The text was updated successfully, but these errors were encountered: