Admin: Deploy
From Resin 3.0
The Deploy /resin-admin page is used to deploy new web applications and upgrade existing ones. It deploys applications throughout a cluster in a single step, using versioning and staged deployment.
- Deploy new applications
- Deploy new versions of existing applications
- Deploy applications across a cluster
- Deploy applications for testing
Deploy form
The basic deploy form allows you to deploy an application war file to a specified context path. You may also specify optional version and commit message fields.
- Application archive file
- The .war file to upload
- Name
- The name of the application, which is also its context path. For example, a name "foo" would correspond to the URL http://www.example.com/foo. The special names "/", "/ROOT", and "ROOT" are reserved for the root context path and would correspond to the URL http://www.example.com/
- Version
- An optional version for the application in the format <major>.<minor>.<micro>.<qualifier>. The <major>, <minor>, and <micro> fields are numbers, but the <qualifier> field can uses numbers and letters. If no version (or 0.0.0) is specified, Resin will assign the current time and date as an implicit version. When deploying an application, the newest version will handle all new sessions while any users with sessions on previous versions will continue to use those until the session expires or is invalidated.
- Commit message
- An optional message that is saved along with this deployed version of the application.
- Advanced options: Host
- The virtual host to which the application will be deployed. By default, applications are deployed to the "default" host. An application deployed to the "default" host will be served for any host requested by the client. To deploy an application so that it is only served on a specific host, select "Deploy to another host" and enter the host name in the text field.
- Advanced options: Stage
- The stage to which the application will be deployed. By default, applications are deployed to the "production" stage. An application will only be run on servers whose stage matches their own. Resin servers are started with a stage -- by default they run in the "production" stage. To deploy an application to another stage (e.g. "preview"), select "Deploy to another stage" and enter the stage in the text field.
Updating previously deployed applications
The form will notify you if you are upgrading an existing application. If you are upgrading an application that was previously deployed via this form, an informational message such as the one below will appear. It lists the current state of the application before your update, showing the name, current version, when the application was deployed, and the commit message.
Updating applications deployed via the file system
If you are upgrading an application that was previously deployed via the file system, an informational message such as the one below will appear. This message warns you that when you deploy an application via the deploy form, it will overwrite any existing application deployed via the file system. In some cases, such as the one in the screenshot below, this behavior is desired, but care should be taken to ensure that this is the behavior you want.
