Deploy from GitHub to your server
Build and deploy your Git repositories on Github to one or more servers.
Sign up for free
As simple as 1-2-3
Connect your GitHub repository
Push a new commit and your changes are live with the push of a button.
Setup your build
Define commands to process your code before it's uploaded to your server.
Deploy to multiple servers
Deploy to one or more servers using a variety of delivery methods such as FTP, SFTP and SSH.
After signing up, create a new project and attach your GitHub account. All repositories available to the account will be shown and you select the one you like to deploy.
Automate tasks such as installing dependencies, transpiling code, running tests, and everything in between.
We will automatically suggest a build config according to the contents of your repository.
You’re now ready to deploy with zero-downtime and instant rollbacks.
What are the benefits?
The end of manual uploads
With a push of a button your commit is made into a build and all changes are deployed to your server. There is no need to upload files manually or to worry whether every single file is in the right place.
Deployments without stress
In case something doesn’t go exactly according to plan after deploying a new version: rolling back to a previous working version is a matter of pressing a button.
No longer run local builds
Run commands and scripts in an isolated container without any hassle; your generated, bundled or transpiled files will be uploaded along with the release. This means you don’t have to generate anything locally, and commit it to your repository unnecessarily.
Your build is completed within seconds
Our built-in caching system will save you a lot of time. Didn’t modify your composer dependencies? We’ll just grab the vendor folder from our cache in the blink of an eye.
Looking for more? Here’s more of what we can do to help you:
Zero-downtime (atomic) deployments
Your site won’t ever go down. Publishing a new version? We’ll upload the new version to a separate directory first and only then update the symlink to bring it online.
Configure build commands
Using task runners and module bundlers? No problem! Run commands such as, “composer install”, “npm install” and “gulp” in an isolated build container before uploading the resulting files.
Execute SSH commands
SSH commands are shell commands that you can run on your server before or after a deployment. These can be anything: restarting services or running database migrations.
Add configuration files
Keep sensitive information such as database credentials safely excluded from your repository by storing them in your encrypted server-specific config file pool. These files will be sent to your server as a part of each deployment.
Exclude certain files
Prevent certain files from being uploaded to your server to keep your deployments snappy. These are files in your repository or artifacts that might be generated during a build step, but not need to be uploaded to your server.
Follow the progress closely
During every step of the way, a log is synchronized to your browser in real time so you can easily keep track of the deployments to your staging, testing and production servers.
Ready to start?
Create an account and start deploying your code from GitHub to your server today - the fast and easy way.
Code monkeys by day. Superheroes by night.
Developers from the Netherlands with a mission.
Developers should get to focus entirely on their code, and on building awesome software --
our mission is to take care of the annoying and error-prone “chores” surrounding that process.
We’re developers from the Netherlands, and our goal is to introduce every developer to the power of deployment automation and to bring an end to the age of manual uploads, broken production sites and stressful maintenance.
What started as a CLI project quickly grew into a full deployment automation service. From the very start, it’s been our mission to make deployment simple, safe and fast. We’re convinced we’ve succeeded by building Launchdeck.