BAM! is a web-server for developers.
Heavily inspired by pow, BAM! goes further by supporting not only ruby/rack applications, but any Procfile-based application. Also, BAM! is planned to support both Linux and Mac OS X.
Download and put the binary somewhere in your path.
git clone https://github.com/jweslley/bam
make build
BAM! is composed by a reverse-proxy and an application manager. On startup, the application manager search for Procfile-based applications in a given directory (customized by configuration file) and list all applications found at address http://bam.dev . From this listing, the user can start/stop applications.
However, in order to work properly, BAM! requires a couple of firewall rules and some tricks to resolve domain names. Thus, when the user access some application, like http://myblog.dev, the host OS must be configured to resolve any request to the top-level-domain .dev to localhost. After reaching port 80, the firewall must forward the request to reverse-proxy's port (defaults to 42042). Once a request reach the proxy, it will be forwarded to the target application (myblog in this example).
Since BAM! manages start/stop of the applications, it's important the web process in the Procfile be declared with a PORT environment variable, which will be informed by BAM! during application's startup. Something like:
web: rails server -p $PORT
Please checkout the examples directory.
The applications's directory, the top-level domain and proxy's port can be customized by configuration file.
In BAM's terminology, an application is a directory in the applications's directory containing either a Procfile or a index.html file. Primarily, BAM! deals with Procfile-based applications (a directory with a Procfile). However, if a directory contains a index.html file, BAM! will serve all files inside this directory as an static server.
During application's start, BAM! will pick an unused port and start either a couple of external processes depending on Procfile or a static web server. The application will be accessible at the address: http://<application-name>.dev For example, the myblog application will be accessible at http://myblog.dev
Once a application is started, it's also automatically accessible from all subdomains.
BAM! lets you access others applications running in your machine using better names. For example, I like to use btsync to synchronize files between my computers, by default btsync start at system's boot at port 8888, using port aliases I can access btsync by typing http://btsync.dev instead of http://localhost:8888, it's easier to remember.
Sometimes you need to access your applications from another computer on your local network, but the .dev domain will only work on your local computer. In this case, you can use the special .xip.io domain to remotely access your applications.
192.168.1.15 is my current IP address in the local network!
xip.io is great, but works only on your local network. Nowadays, remote work is common and to show your application to a remote coworker or even a client your need to configure a VPS containing a configured environment. To simplify this task, BAM! lets you share/unshare your application to the Internet through localtunnel.
During application's start, BAM! will loads .env file (if available) in the application's directory and pass all environment variables to the applications's processes.
The command center is the application manager. A web application accessible at http://bam.dev from where you will list, start, stop, share and unshare your applications.
As stated before, BAM! requires a couple of firewall rules and some tricks to resolve domain names. Both of these requirements vary depending on your machine's operating system. Currently I tested BAM! in Archlinux (my beloved OS), but it should work in other Linux distributions too. Mac OSX support also must work, but not tested, configuration procedures were stolen from Pow. Feedback is welcome! ^^
First at all, we need a way to resolve domain names in top-level domain .dev to localhost. In Linux, we could run a custom DNS server (like localdns) for accomplish this, but there is a better way than running an extra process. For this, we will use localtld, a custom NSSwitch plugin to resolve domains for local applications. It's very straightforward to install, thus visit the project page and follow installation's instructions.
Since your machine is already resolving domain names to localhost, now we need forward all incoming connections from port 80 to BAM's reverse-proxy (port 42042). In Linux, the easier way is using iptables. BAM has a command to generate the iptables rules required. Thus, run the following commands:
bam -generate iptables > iptables.rules
sudo iptables-restore < iptables.rules
Depending your Linux distribution, you will need extra configuration to load these rules at system's boot.
It's done. Now, start BAM! and have fun.
In Mac OSX, we need localdns to resolve domain names in top-level domain .dev to localhost. Thus, visit the project page and follow installation's instructions.
Since your machine is already resolving domain names to localhost, now we need forward all incoming connections from port 80 to BAM's reverse-proxy (port 42042). In Mac OSX, we will use plist to setup the firewall rules for us. BAM has a command to generate the plist file. Thus, run the following commands:
bam -generate firewall > bam.firewall.plist
sudo cp bam.firewall.plist /Library/LaunchDaemons/bam.firewall.plist
sudo launchctl bootstrap system /Library/LaunchDaemons/bam.firewall.plist 2>/dev/null
sudo launchctl enable system/bam.firewall 2>/dev/null
sudo launchctl kickstart -k system/bam.firewall 2>/dev/null
It's done. Now, start BAM! and have fun.
Yeah, Windows! Why not?! Theorically, with some windows expertise, is possible to configure both a DNS server to resolve top-level domain to localhost and the required firewall rules. I tried to configure localdns as a secondary DNS on Windows, but I discovered that the Windows DNS's client does not query the secondary DNS before a 15 minute timeout. :(
If you are experienced in Windows and want to help us, please take a look this issue.
After download and put the binary somewhere in your path. Lets run BAM!, for this go to the directory containing your applications and execute it:
cd /path/to/my/apps
bam
It's it! By default, BAM! will look for applications in the current directory. To change this or some other configuration generate a configuration file and customize it.
bam -generate config > ~/.bam.conf
After edit the configuration file, run BAM! using it:
bam -config ~/.bam.conf
Please take a look at issues tracker for upcoming features.
If you discover any bugs or have some idea, feel free to create an issue on GitHub:
https://github.com/jweslley/bam/issues
MIT license. Copyright (c) 2013-2015 Jonhnny Weslley http://jonhnnyweslley.net
See the LICENSE file provided with the source distribution for full details.