Let's assume that you have your application code in an SCM (git, svn etc..) and you have the ability to build any parts, that you need, into the artifacts that will be deployed.
What directory structure is best to use for our package? With Vamos you are free to decide on this yourself. The only rule is that you have a directory called 'bin'. Vamos will give all contents execute permissions.
$ vamos application JupiterServer 1.0.0 create --directory=$HOME/JupiterServer
The above command will create the application in the Vamos database and copy the code to the local repository. It will instantly be useable on this host. File permissions will be set to be read-only with executable permissions being given to all contents of the 'bin' directory. The local repository will be at the following location:
/vamos/<our department>/applications/JupiterServer/1.0.0/
The status of this application will be 'local' and it only exists locally on the host we created it on. We can commit this application to the Vamos filestore so it can be used by other hosts. This will also change the status to 'dev':
$ vamos application JupiterServer 1.0.0 commit
We need to add a subscription to the application. More details on this in another post but they are used to specify what operating system applications were built on and hence what this application is compatible with. For now let's set to ALL to indicate it can run on any o/s:
$ vamos application JupiterServer 1.0.0 addsub ALL
Let's now see the details of what we have created:
$ vamos application JupiterServer 1.0.0 info
Application : JupiterServer 1.0.0
Status : dev
Owner group : developers
Subscription : ALL
The owner group will be set to the default group that your userid was registered with. In this case the user is in the developers group. Vamos uses a simple group ownership model for all objects it creates. If you created it then your group owns it and your group can do whatever it wants with it.
No comments:
Post a Comment