Whales has a new look and a faster base image! Here are some instructions for updating your local Whales install and your project (if you didn't already clone from Whales Snap).
Run the following command in your Terminal/Powershell:
npm install --production -g @calblueprint/whales
Run the following command in your Terminal/Powershell (please add and commit your work before running — this command will not work if you have uncommitted work).
You should be inside of a Whales project to update.
whales update
Whales will attempt to set your upstream remote to Whales Snap (the newer, faster base image), pull down changes, and run whales bootstrap.
If you notice missing Gem errors after, you can add them back to your Gemfile and use whales run bundle install.
Whales 0.2 replaces the terminal-based interface with a more intuitive browser interface that began with the introduction of the Web Console.
The Web Console is still there, now with a requests log that you can use to examine the controller/method responsible for responding to a request and any params passed in!
A screenshot of http://localhost:7331 — the new home for Whales
Click the View logs button to see every log printed from your Whales containers. It may be a bit hard to sort through, but you can use it to see the output of puts, which you can use to print values.
Whales now runs independently of your Rails server — which means that you can restart it from within localhost:7331. This might help to cover problems and edge cases that may occur when installing Gems.
whales update: Checks for updates to the Whales base image and attempts to pull them into your project.whales killall: Shut down all Docker containers. This can be helpful if you're having trouble starting up your server due to Whales running somewhere else.