$DEPLOYIT_HOME/deployit-3.8.4-cli/bin/cli.sh -username admin -password admin -f $DEPLOYIT_HOME/DeployitBlogs/tools/deploy.cli - $DEPLOYIT_HOME/DeployitBlogs/tools/src/test/deps.dar localenv
After some command line input checking all they do is call one of the functions defined in utils.py. The scripts in cleanup.cli and deploy.cli are no more than convenience wrappers that make it easier to test new versions of the plugin. It should exist though, so in my case Deployit just connects to localhost as user ‘deployit’ to run the scripts. I defined both hosts with default settings and a username of ‘deployit’, but the username doesn’t (yet) matter for the examples. They should contain a overthere.SshHost named ‘local’ and ‘AnotherLocalHost’ respectively. Open the Deployit client interface and create two environments named ‘localenv’ and ‘AnotherLocalEnv’. One more piece of setup is necessary: create two test environments that are required by the scripts in examples I hope to discuss later. Ln -s $DEPLOYIT_HOME/DeployitBlogs/tools/utils.py utils.py It is supposed to be placed in $DEPLOYIT_HOME/cli/ext, but that can become rather tedious very quickly if you’re going through lots of versions, so I left the script in the tools directory and created a symbolic link to it so the cli will pick up new versions when it is restarted. Utils.py isn’t really a script but a plugin. In src/test you’ll find a dar file I’m using to try out my scripts and plugins (deps.dar was build from another example I hope to explain later, for now it’s not important all it does is copy some files and print a message to the console). After checking out the sources and installing Deployit, $DEPLOYIT_HOME should contain the following folders:ĭeployitBlogs contains a directory named tools that for now holds no more than a couple of scripts, most notably three scripts named utils.py, cleanup.cli and deploy.cli.
DEPLOYIT TOOL DOWNLOAD
If you insist on using Microsoft you can always download Cygwin or change the examples yourself. I’m using *nix style variable and scripts in my examples. I’ve installed the server and cli in a directory referenced by an environment variable $DEPLOYIT_HOME. To try out the examples you’ll need Deployit 3.8.4 (the version I used, but I’m quite sure it’ll work fine with other versions as well).
DEPLOYIT TOOL CODE
I’ve placed my code on Github (git clone git:///jvermeir/DeployitBlogs.git).
DEPLOYIT TOOL SERIES
While working on examples I was frustrated by having to clean up remainders of previous attempts, so following in the footsteps of greater men than my humble self (most notably professor Knuth who created TeX so he could finish writing a series of books on computer science) I first wrote a script to create junk in the Deployit repository and then get rid of it in one sweeping go. All I wanted to do was create a number of plugins and examples for Deployit using the different techniques available.
0 kommentar(er)
