You can have your first application up and running on Cloud 66 in under 5 mins. Follow the steps below to see how easy it is to get your app configured, built, and deployed.
What you’ll need
Before you start, please check you have the following:
- A Cloud 66 Account — If you don’t already have one, sign up for a Cloud 66 account. You’ll get free unlimited access to all products for 4 weeks.
- Application code and/or pre-built images — Application code should be hosted in a (secure) publicly accessible git repository and pre-built images should be hosted in image publicly accessible repositories.
- An account with a supported cloud provider or your own servers set up — Cloud 66 supports a range of cloud providers. Select your preferred provider from the dropdown under Step 4 below.
Once you're ready, click the green New Application button to start the process.
Step 1: Choose a source
The first thing we need is access to your code, so that we can build and deploy it for you. Click the tab below which best suits your needs:
The easiest option is to give us (read-only) access to a Github repo. To do this:
- Click Get Started
- On the next page click Link with Github
- We’ll send you to our app on Github (you’ll need to sign in)
- Once you’re signed in, click Configure & then select the Github account you wish to link to Cloud 66
- Install and authorize our Github app (you can restrict our access to specific repos if needed)
- You will be redirected back to your Cloud 66 dashboard and you can move on to Step 2.
Step 2: Define your application
Now that we have access to your git host, you can tell us which repo you want to deploy:
- Choose the repo you want to deploy and set the branch
- Choose an environment for your application
- Give your application a name (this will be used to label your application throughout the Cloud 66 dashboard, and will not be visible to public users.)
- Click Analyze - we will now scan your repo and suggest the optimal settings
Step 3: Configure and build
Step 4: Add a cloud provider
A. Configure access to your cloud provider
B. Add your cloud provider as a deployment target
To add your cloud credentials click the Add a Deployment Target button. This will open a panel that will enable you to grant Cloud 66 access to your provider.
Click the green Add Deployment Target button once complete.
C. Specify servers
Next you need to specify where your servers will be situated, how large they should be, and where your data will be stored:
- Choose a Server Region
- We will suggest a size for your application server - you can change it as needed
- Specify whether your datastore will share the app server (not recommended for Production), or have its own server. You can also use an existing external database server if you prefer.
Our customization section has more details on the available options.
Step 5: Deploy your app
When you’re satisfied with your servers, click the Start Deployment button. During the build and deployment process you can view the log to see what’s happening behind the scenes.
You can also close the window and come back later. We will email you once the application is deployed (or if it fails).
Initial build may take some time
The full build and deployment process may take 15 minutes or more because Cloud 66 needs to provision the new servers from the ground up. You can close the window and we will send you an email when the deployment is complete.
Server build states
In order to allow you to start working with your new app as soon as possible, there are two build states (or stages) for application servers:
- Ready - server is available to use, with the minimum required configuration
- Optimized - all the latest packages are installed & optimized
Customizing your app
If your application relies on specific components or non-standard settings or package versions then you can easily customize your configuration to match your requirements.
The method you use to configure a component depends on the nature of the customization. The table below will help you find the right tool:
|Customization required||Configuration tool|
|Specific versions of a framework or package||Manifest file|
|Cloud-provider-specific settings for servers (e.g. security groups, subnets)||Manifest file|
|Component configuration (e.g. database engine config files)||CustomConfig|
|Environment Variables||Dashboard or Toolbelt|
|Non-standard Linux packages or libraries||Deploy hooks|
|Running multiple database types or versions (groups)||Manifest file or Dashboard|
- Containers can also serve non-HTTP traffic. TCP and UDP protocols are also supported. Learn more about Container Port Mapping in our detailed tutorial