|Info||Example||View files (21)||Download .zip||Reputation||Support forum||Blog||Links|
|Ratings||Unique User Downloads||Download Rankings|
|Not yet rated by the users||Total: 39||All time: 10,589 This week: 138|
|airship-barge 1.0||MIT/X Consortium ...||5||PHP 5, Content management|
Paragon Initiative Enterprises
This package can be used to build extensions for the Airship CMS.
A command line interface for developing and distributing Airship cabins, gadgets, and motifs.
First, checkout our Git repository.
git checkout https://github.com/paragonie/airship-barge.git
Next, make sure you can execute the barge command.
cd airship-barge chmod u+x barge
Make sure you install the dependencies via Composer. This will get Halite and our constant-time encoding library installed (both are libraries that barge uses extensively):
Finally, you'll want to create a symlink in
/usr/bin so you can run barge commands
by simply typing
ln -s ./barge /usr/bin/barge
Recommended: Create a workspace directory.
cd ~ mkdir barge-workspace cd barge-workspace
If you don't already have a Supplier account, register one here.
Now you're ready to run your first barge command.
If this is your first time logging in, you'll need to run
barge key twice.
(Before the final version, we intend to make this process a lot smoother.)
barge key # Follow the prompts to generate your master keypair barge key # Follow the prompts to generate your signing keypair, which you'll need to sign with your master key
Once your keypairs are generated, their public counterparts are uploaded to the server and synchronized to the entire network in an append-only data structure.
Once your keys are set up, you can begin to build CMS Airship extensions. What do you want to build?
After you follow the prompts, you should have a skeletal project directory waiting to be fleshed out.
Ready to deploy your first version? Okay, first:
This assembles a .phar or .zip of your extension. You can manually install these into a local Airship to test them out (recommended).
If you're ready to release it, first sign it with your signing key:
And then release it:
If you've followed these steps, your package should be available for install in CMS Airship. If you release an update in this manner, it should be deployed and installed on all of your users' machines automatically (typically within an hour, unless they changed their configuration).
|src (5 files, 1 directory)|
|Commands (10 files, 1 directory)|
|Proto (1 file)|
|Version Control||Unique User Downloads||Download Rankings|
|Applications that use this package|
If you know an application of this package, send a message to the author to add a link here.