Introduction to Cloud 66
- What is Cloud 66?
- What you'll need
- Step 1: Build your stack
- Step 2: Service configurations
- Step 3: Define deployment properties
- Step 4: Review the deployment logs
- What's next?
What is Cloud 66?
Cloud 66 builds your full stack on either your own servers or cloud servers, deploys your application to them, and manages it for you. Whether you are a running a small hobby project or work in a large team of developers, Cloud 66 helps you focus on what you do best.
Because Cloud 66 is provided as a service, you don’t need to install anything on your local machine. Some of the features we provide include:
- Deploying your application to your cloud or your own servers
- Backing up your databases at set intervals
- Scaling your web, database, and process servers with the click of a button
- Securing your servers with features such as intruder detection and firewall
- Monitoring your servers
To get started, you just have to provide us with a Git URL to your repository or your own Docker image(s). We’ll then build a stack based on it.
Before you get get started, you may want to look at our Technical specifications to determine if you’re ready for Cloud 66.
What you’ll need
- Cloud 66 account
- A source for your service(s)
- Pull your code from Git (with a Dockerfile)
- Provide an existing Docker image
- Deployment credentials
Step 1: Build your stack
Before you can deploy your applications to a server with Cloud 66, you must build a stack of the components your application needs to run. To build your first stack, complete steps below.
- Sign in to Cloud 66.
- On the Cloud 66 dashboard, click Build a Docker stack.
Step 2: Service configuration
Now provide a stack name, and the environment you would like to deploy in. Next up is configuring your Docker services - for example web, api, worker and so on. You can add as many services to your stack as you need. These are the available fields (for the basic tab):
- What's the service name?
- How shall we build this service?
- Pull code from Git: Cloud 66 builds your Docker images for you using BuildGrid, which requires that you place a Dockerfile in your repository.
- Build from Docker image: Specify your own Docker image repository for us to pull your image from.
This page has basic and advanced configurations, designated by the tabs at the top of the form. Switching between the tabs will retain any previous information provided. The advanced tab allows you to input more detailed settings, which you can learn about in Docker service configuration.
Step 3: Define deployment properties
Complete the following steps to define the properties that determine how to deploy your application.
If deploying to a cloud server, you must know the API key for your cloud provider. If deploying to your server, you must have (or generate) a SSH key for the server. For instructions on generating an SSH key, refer to Setting up SSH keys.
- In the Where are you deploying to dialog box, select the deployment target to use.
- Perform one of the following actions, depending on your deployment configuration:
- If deploying to a cloud, select the cloud provider, server region and server size.
- If deploying to a server, enter your username and IP address.
- In the Deployment details dialog box, select the database option to use.
- Click Deploy.
This page has also has basic and advanced configurations, designated by the tabs at the top of the form. Switching between the tabs will retain any previous information provided. The advanced tab allows you to input more detailed settings, which you can learn about in Getting started with manifest files.
Step 4: Review the deployment logs
After your stack builds successfully, you can view the log generated by the deployment.
Your stack is up and running - you now have:
- Docker servers with automated deployment and lifecycle management
- Networking and DNS layer across your stack
- Database layer
- Load balancing layer
- All other Cloud 66 features, such as security, managed Nginx, team management and so on.
You can now start customizing by: