What prevents those users from doing a ./bin/myapp stop? I mean you can prevent typos by letting the user use distilleries custom commands, which you created. You can obscure the actual shell command from the user by wrapping the distillery commands further into custom shell commands. In the end you still need to send rpc commands to the running erlang vm.
LostKobrakai
1
Mooodi
That’s not. What if I have a user whom I delegate this job and whom I don’t want to call anything else but a certain module#method? What will prevent him from calling something else? Even by making a typo.
What if I accidentally call “MyModule#reset_db2” instead of “MyModule#reset_db1”? Assuming that “MyModule#reset_db2” has no task associated with it – it’s merely a module and function, whereas “MyModule#reset_db1” does.
console won’t prevent such type of mistakes.
0
OvermindDL1
Not even remotely, that ‘is’ the way to call something in a running system from the system shell.
0
gregvaughn
No, it’s not hackish. It’s functionally equivalent to doing the remote console approach and typing the command, but it just does it all in one from the unix shell.
Mooodi, I see you have a rails background. As superficially similar as the syntax of Elixir may look to Ruby, things are a whole lot different under the hood. In a distillery release on a server, bin/yourappname is the closest thing to rake you’re going to get. Distillery’s hexdocs are very good and will show you how you can write custom commands for your release (https://hexdocs.pm/distillery/custom-commands.html)
1
Mooodi
That’s a semi-hackery approach, the one similar to editing data directly in database or running REPL on server to patch something in a dirty and fast way, isn’t it?
0
Mooodi
OvermindDL1
Your server like bin/<name> has an RPC command for calling functions straight, like bin/<name> rpc The.Module function_to_call args....
So you make the function in your system, then you can call it like that. Quite simple and easily wrappable into single-line scripts. 
2
NobbZ
rake is a ruby tool and independant from phoenix, elixir or whatnot. If you want to use rake you need to install it.
If though you want to run maintanance functions, then just create them in your application, eg:
defmodule MyApp.Maintanance do
def foo(), do: :bar
end
Remote-Shell into your app:
$ iex --remsh your@node --cookie $your_cookie --name your@ip
[elixir header]
iex(1)> MyApp.Maintanace.foo()
:bar
Well, at least roughly. Can’t test right now, since I’ve no elixir machine, but thats the rough theory.
If you use destillery, you can use this example from the docs, explaining how to run migrations and change it that it suites your needs.
Basically it involves these steps:
- Write maintance functionality in your app
- write a shell script which wraps your command
- register a subcommand in your release config
Also as far as I remember, destillery has a command for a shell built-in: myapp shell (after SSHing into your server) should open up an iex prompt which runs in the context of your application.
edit
It’s not shell, it’s remote_console:
Once started, you can connect a shell to the running release with
bin/<name> remote_consoleorbin/<name> attach, though I would avoid the latter unless you have good reason to use it, as exiting with CTRL+C will kill the running node, while doing so withremote_consolewill simply exit the shell.
From https://github.com/bitwalker/distillery/blob/master/docs/Walkthrough.md
edit2
And if you are not using distillery, but something else to build your release, you should tell, then we can answer more tailored to your release tool.
2
PatNowak
It was an example 
You can do it as we already explained you how, just make sure that any part of your app that you want to use, it’s started.
0
Mooodi
I didn’t say “migrations”. I said - task. I want to login to my server via ssh and run a task in the terminal, the same way I’d do in ruby – “rake my_task”
0