This guide walks through a first deployment from start to finish. By the end you will have deployed a package to a server, with a setup that already looks like a production one.
What you need
- A Jaws Deploy Cloud account. The free plan needs no card.
- One target: a Windows or Linux machine you can install the agent on, or an Azure Web App.
- A package to deploy, such as a zip, a tarball or a NuGet package.
1. Look around the workspace
A workspace holds your projects, environments, lifecycles, feeds, machines, variables and step templates. A new workspace starts with two environments, Staging and Production. Add more under Environments if you need them.
2. Add a target
// Option A
Install the agent
Open Machines, choose Add machine and download the install script for Windows or Linux. Run it on the machine. The agent connects outbound and sends a handshake, and you approve it in the workspace.
// Option B
Add an Azure Web App
Add an Azure cloud account, then add the Web App as a cloud target. No agent is needed, because Jaws Deploy deploys through Azure.
Assign the target to an environment, for example Staging.
3. Create a project
Create a new project and give it a name. It starts with an empty deployment process. Upload your package to the built-in feed in the Package Store, then add a Deploy package step that uses it and save.
4. Create and deploy a release
On the project page, create a release. Jaws Deploy stores the deployment process, the package version and the variables in it under a version number, and the release doesn't change after that. Then deploy it to Staging.
The live log shows the agent receive the work, extract the package and report the result.
Next steps
You now have an environment, a target, a deployment process, a release and a deployment. From here:
- Connect your CI server so it creates releases after each build.
- Add a lifecycle and promote the same release from Staging to Production.
- Move settings into variables scoped per environment, so one process serves every environment.