What is Invoker?
Invoker is a utility belt for managing processes in development environment. Use it for managing multiple processes with ease.
Use it for developing web applications on different local domains without
Invoker supports DNS and proxying of HTTP/HTTPS/WebSocket applications over a
like local TLD.
A brief overview of Invoker features are:
- Manage multiple dependent processes using Invoker. You can use Procfile or a INI file to define multiple processes managed by Invoker.
- Invoker supports proxying to your HTTP application via a locally defined TLD like
- Invoker automatically supports HTTPS, Websocket for your application.
- Any externally running HTTP application can use HTTP proxy of Invoker for access via
How to use it?
First we need to install invoker gem to get command line utility called invoker, we can do that via:
Currently it only works with Ruby >= 1.9.3.
You need to start by creating a
ini file which will define processes you want to manage using invoker. An example
ini file is included in the repo.
After that you can start process manager via:
Above command will start all your processes in one terminal with their stdout/stderr merged and labelled. You
can also start
Invoker by daeomonizing it, via:
.local TLD support for OSX and Linux.
You can access http services managed by invoker via
command_label.local domain locally.
To make it work though, you need to run following command, just once from anywhere:
This feature has been well tested to work on both
Linux. You can additionally
run above command with:
If you decide to remove Invoker, you can remove things installed by Invoker using command
Now because invoker is making your app server available on a domain. It requires
control over port(or needs to know the port) on which your applications will be listening. This can be simply done by replacing specific port number in
ini file with
$PORT or by specifying
a port key. For example:
Now these services can be accessed via
http://typo.local. You can also access them via wildcard subdomains such as
You can also access any external http process via
.local DNS by running
Above command will make wordpress available on
wordpress.local even if
wordpress was original not started by Invoker. You can access any randomly
started process via Invoker like this.
Invoker uses a self-signed certificate to make all your web applications available via
https as well. You absolutely don’t have to do anything. Access your webapps on
Invoker is 100% compatbile with
Procfile format used by Heroku. If you
have been using a
Procfile to bootstrap your development stack, you can
keep using it with
The only thing to remember is, your
$PORT in command - for
.local domain feature to work
Additionally Invoker allows you to manage individual processes. You can start/stop/restart
different processes managed by invoker without affecting others. Following commands work
for processes started by
Procfile as well.
You can also enable OSX notifications for crashed processes by installing terminal-notifier gem. It is not a dependency, but can be useful if something crashed and you weren’t paying attention.
Migrating from Pow
If you are migrating from Pow then first step before running
invoker setup is to uninstall Pow:
After that you should run
as usual. If for some reason you can’t uninstall Pow via above
command (in case you installed Pow using homebrew), then you
should remove Pow daemon manually.
invoker setup you will
have to switch off wi-fi and then switch it on for
resettng OSX network configuration.