aws-upload is a CLI Tool to rapid deploy files on your server over ssh. Unlike other scripts or tools, aws-upload is designed to maximize efficiency, speed, and automation.
The core functionality is based on rsync to deploy only what you need. It will automatically compress and upload only the files you change it.
The project was born because a frustration I got at work. We had a lot of small projects in place and no deploy system.
At the beginning, I was using just standard FTP clients (eg. FileZilla). But this process was just tedious and full of errors.
There are at least two main issues:
Find the file: this process probably was the most time consuming and frustrating. You have to click through all the tree on each folder till you reach the file you want to upload. And then repeat the process for each file you want to upload. Not efficient at all.
Upload only the correct file: sometimes for laziness, you may be tempted to drag and drop a full folder. Big mistake, chances are you are uploading as well some file you may not want to upload. Think about of your
.git folder for example.
Later on, I start using
I believe that when you reach a critical amount of data on your .rc file (
.aliases), the full experience with
alias is broken.
There are at least three main issues:
Setup: when you setup an alias is tedious. Long strings are risky to edit and manipulate. Reload the shell all the time you edit it's quite frustrating. It's better in real time.
Debug: if you make a mistake in your alias you won't receive specific error messages to help you and make the process painless. It's better with some check.
Structure: crawl a huge file and edit a three line command without any structure it's not fun. It's better to edit with scope and focus.
At the end, I finished writing a PHP script with some json files to fix the problem: aws-upload was born.
aws-upload does just one thing, deploy.
I think if you are playing with a huge project in which you need to automate a little bit more (eg. testing before deploy, building systems, versioning for each server) aws-upload is not for you.
In these cases, you should have a proper deployment automation in place, maybe with some CI system.
This guide assumes you are already familiar with composer and you have it installed on your machine. If you don't have composer follow the guide here to install it.
To install aws-upload we will use Composer.
Run this in your terminal to get the latest aws-upload version:
When the procedure is completed you can verify that all is good by typing:
The tab completion is done by the shell you are using.
Right now the only shell supported is zsh in combination with oh-my-zsh.
The auto-complete function is done with an oh-my-zsh plugin. To enable the autocomplete you can type:
This command will download, install and enable the oh-my-zsh plugin for you.
The auto-complete function relies on a specific set of your system. In particular, it expects your system to have the following software already installed :
The auto-complete is an oh-my-zsh plugin as said before. If you want to install the plugin manually, follow the instructions on the aws-upload-zsh documentation.
aws-upload to the latest version, run the
self-update command. It will replace your
aws-upload with the latest version.
If you have the tab-completion enabled run
autocomplete to update the zsh plugin as well.
There are some concept that you have to be aware if you want to use properly aws-upload.
Project: the project is a label to identify a project you are working on.
You can not use a
. in the project label.
Examples: [blog, client-name].
Environments: the environment is a label to identify a specific environment or setup.
You can not use a
. in the environment label.
Examples: [dev, stag, prod].
Keys: the key is a shortcut to identify a project in combination with an environment.
The syntax is:
Before to deploy with aws-upload you have to create a setting file. To create a setting file:
This command will generate a setting file for this key. Now you have to edit it.
To edit you can type:
Now you are ready to deploy.
To deploy edit:
This is the structure of a setting file.
As you can see there are 4 main parts:
pem | string: it contains the path to your pem key.
local | string: it contains the path to the directory you want to upload to your ec2 server.
exclude | array: it contains the list of files or folders you DO NOT want to upload.
remote | string: it contains the information of your server.
In particular [user]@[host]:[remotePath] where: