You have a great web application that you want to deploy to AWS but you don’t want to bother spending time in the AWS console. You just want it deployed. We heard you, here’s how Stackmate deploys your infrastructure and delivers your code to instances deployed in AWS.
We start off with your application’s folder which can contain a monolithic application in a framework like Ruby on Rails for example or a single page app in React, or maybe both! Stackmate makes it easy for you to deploy your infrastructure and deliver your code on AWS, all in a few minutes.
As simple as dragging and dropping
In case you haven’t done so by this point, you should have an AWS IAM role in place. You can follow these simple instructions to do so.
Creating a project in Stackmate is really very simple, here are the few steps you need to follow:
- Go to “Create Project” at the top of the navigation menu. You’ll navigate to a page that contains a drop-area where you will need to drag your project’s folder to
- Once you do that, we pick a few configuration files from your project and perform some static analysis which will help us set up some basics for your projects such as Environment Variables, Configuration files, Dependencies and Services. You will get the option to customize some of the project’s basic parameters such as the domain name, the region to deploy to, the IAM Role to use etc. In case the project can be immediately deployed, you will be taken to the deployment list, or the project page otherwise.
The production environment
Every branch in your repository, can be deployed as a standalone, full featured environment with its own VPC, databases, caches, instances and so on. By default, your production environment is created the moment you create your project, so it should be directly available. If it’s not, or you need to create another environment, you can follow these simple instructions to do so. Once you pick a project from your dashboard, you should be able to view all environments related to it.
Choosing an environment from the list of available ones, will open the environment details page where you can manage & configure every component associated with it.
If you’re to browse around, you’ll find the following tabs:
- The Overview page, where you can find information about the environment’s deployment status, branch to be deployed and recent deployments
- The Services page, where you can add, remove and update the project’s services, such as AWS services and software dependencies
- The Pipelines page, where you can customize your deployment & rollback pipelines.
- The Configurations page, where you can manage your environment variables, your configuration files, job schedules and SSL certificates
- The Settings page, where you can manage your environment’s base settings such as domain name and branch to be deployed
Ready, set, deploy!
Once everything is set and you hit the deploy button, or in case the option “Deploy immediately after the project is created” is checked while creating the project, you will get redirected to the deployment page, where you can track the progress of your release. After the deployment is done, you will receive an email that let’s you know of the its status
Just keep developing your application
You don’t have to worry about subsequent commits and how they’re going to be deployed. All you have to do is run your
git push command or merge a pull request and our system is going to pick up the changes and trigger a new deployment.
That’s it! Time for a cup of coffee ☕️