Workbench 24.0.0 Beta 1 Now Available for Download

[Ryan Brainard]

This is a relatively minor release for Workbench, but in keeping up
with the latest Salesforce API 24.0, this updates all the WSDLs and
API clients, adds limited support for running Workbench on Heroku
(http://www.heroku.com/), and includes minor bug fixes. Support for
running on Heroku includes:

- Phing (http://www.phing.info/) based build for source code
generation. Currently there is still an Ant build for some tasks, but
this should be phased out in a future release.
- Environment variable based configuration. This is used the same as
the configOverrides.php file, but allows configuration to be changed
at runtime and without changing source files. This release also
includes a script file for converting your current configOverrides.php
to `export` or `heroku config:add` commands for easy transition.
- Proxy forwarded SSL detection
- This does not yet include support for distributed session
management, so it will currently only work with one Heroku web dyno

To download Workbench 24.0.0 Beta 1, go to:
http://code.google.com/p/forceworkbench/downloads/list

Installation installation instructions can be found here:
http://wiki.developerforce.com/page/Workbench#Installation

Full change list:
http://wiki.developerforce.com/page/Workbench#Version_History


Support for running Workbench on Heroku is still limited and
experimental, but it can be great way to get an instance up and
running quickly or staging changes from a fork. This will
automatically download and install Apache, PHP, and Phing on Heroku
and publish your instance of Workbench to the world. As mentioned
above, support for scaling more than one web dyno is not yet
supported. Once Workbench supports distributed session management,
this should be possible. To get started, first follow the Heroku
Quickstart (http://devcenter.heroku.com/articles/quickstart). For
"Step 4: Deploy An Application," follow these steps:

1. Clone the Workbench repo:
git clone https://code.google.com/p/forceworkbench/ --branch release/
24.0.0

2. Go into the directory:
cd forceworkbench

3. Create a new app on Heroku with the Phing buildpack:
heroku create --stack cedar --buildpack git://github.com/rbrainard/heroku-buildpack-phing.git

4. Push to Heroku:
git push heroku release/24.0.0:master

5. View in your browser:
heroku open

6. To configure Workbench, instead of using the configOverrides.php
file to override settings, which would require a source code commit
and push to Heroku, it is recommended to use environment variables.
Workbench 24.0.0 supports environment variable based configuration in
a flattened version of the configOverrides.php format. For example:
$config['configKey]['default'] = 'configValue'

would be set on Heroku with:
heroku config:add "forceworkbench__configKey__default=configValue"

This release includes a script that can be used to convert an existing
configOverrides.php format into local export or heroku config:add
commands. The script is located at build/
ConvertConfigFileToEnvVars.php when you clone the repo.

Please let me know if you have any feedback on this new Heroku support
or anything about the new version.

Enjoy,
Ryan

[Ryan Brainard]

Anyone try deploying to Heroku? Any problems?

> git clonehttps://code.google.com/p/forceworkbench/--branch release/