2013-04-24 21:24:51 +00:00
|
|
|
Abuse the Force
|
2013-04-18 16:09:05 +00:00
|
|
|
===============
|
|
|
|
|
|
|
|
|
|
A tool expanding upon [Metaforce](https://github.com/ejholmes/metaforce) for deploying to
|
|
|
|
|
multiple orgs as well as simpler setup for use as a pseudo compiler
|
|
|
|
|
|
|
|
|
|
Features
|
2013-04-18 17:55:25 +00:00
|
|
|
--------
|
2013-04-24 21:24:51 +00:00
|
|
|
* Store orgs config file for easy switching between deploy targets
|
|
|
|
|
* Familiar command sub-command interface (think git)
|
|
|
|
|
* Deploy single files without deploying the entire project
|
|
|
|
|
* [Vim plugin](https://github.com/ViViDboarder/vim-abuse-the-force)
|
2013-04-18 16:09:05 +00:00
|
|
|
|
2013-04-18 17:45:59 +00:00
|
|
|
Usage
|
2013-04-18 17:55:25 +00:00
|
|
|
-----
|
2013-04-24 21:24:51 +00:00
|
|
|
Much like git, you initialize your project directory by adding your deploy targets first.
|
|
|
|
|
Once you have one set you can view the active target with `atf target`. If you want to deploy
|
|
|
|
|
from there you just execute one of the deploy commands.
|
|
|
|
|
|
|
|
|
|
**Simple Setup Example**
|
|
|
|
|
|
|
|
|
|
# Add production
|
|
|
|
|
atf target add production vividboarder@mycompany.com MY_SECURITY_TOKEN
|
|
|
|
|
# Deploy to production
|
|
|
|
|
atf deploy project
|
|
|
|
|
# Add a sandbox
|
|
|
|
|
atf target add sandbox vividboarder@mycompany.com.sandbox MY_SECURITY_TOKEN --sandbox
|
|
|
|
|
# Switch active targets
|
|
|
|
|
atf target activate sandbox
|
|
|
|
|
# Deploy to sandbox
|
|
|
|
|
atf deploy project
|
|
|
|
|
|
|
|
|
|
More advanced documentation can be found by running any of the `help` commands.
|
|
|
|
|
|
|
|
|
|
atf help
|
|
|
|
|
atf deploy help
|
|
|
|
|
atf retrieve help
|
|
|
|
|
atf target help
|
2013-04-18 17:45:59 +00:00
|
|
|
|
2013-05-09 21:55:55 +00:00
|
|
|
Deploy List
|
|
|
|
|
-----------
|
|
|
|
|
Deploy list gives you an easy way to only deploy files that have changed. This works really well if you are
|
|
|
|
|
using some kind of version control.
|
|
|
|
|
|
|
|
|
|
It takes a file of the format:
|
|
|
|
|
|
|
|
|
|
src/classes/MyClass.cls
|
|
|
|
|
src/triggers/MyTrigger.trigger
|
|
|
|
|
|
|
|
|
|
You can generate a file like this using `git diff --no-commit-id --name-only` or possibly the script included
|
|
|
|
|
in the `examples` directory.
|
|
|
|
|
|
2013-04-18 17:45:59 +00:00
|
|
|
Why This Over Metaforce?
|
2013-04-18 17:55:25 +00:00
|
|
|
------------------------
|
2013-04-18 16:09:05 +00:00
|
|
|
* Vim and Sublime plugins (coming soon...)
|
|
|
|
|
* Command line configuration management
|
2013-04-24 21:24:51 +00:00
|
|
|
* Options for deploying or retrieving a single file
|
2013-04-18 16:09:05 +00:00
|
|
|
* Encrypted Passwords coming soon
|
|
|
|
|
|
2013-04-18 17:45:59 +00:00
|
|
|
Installation
|
2013-04-18 17:55:25 +00:00
|
|
|
------------
|
2013-04-18 17:45:59 +00:00
|
|
|
Must have ruby 1.9 and gem installed
|
|
|
|
|
|
|
|
|
|
git clone git://github.com/ViViDboarder/abuse-the-force.git
|
|
|
|
|
cd abuse-the-force
|
|
|
|
|
gem build abusetheforce.gemspec
|
|
|
|
|
gem install abusetheforce-X.X.X.gem # make sure the proper version is present
|
|
|
|
|
|
2013-04-28 01:02:07 +00:00
|
|
|
Todo
|
|
|
|
|
----
|
|
|
|
|
* See Issues tab
|
