Deploy Directly from an Archive
One way to deploy your application is to directly create a deployment from a code archive. This article explains how to use this feature using Scalingo command line tool.
Usage of the deploy Command
To deploy an application without Git or GitHub, you need to archive your
application code in a tar.gz archive format. The archive must contain the
source code in a subfolder at the root of the archive.
For example, if your archive is named my-app.tar.gz, its content should look
like:
$ tar -ztvf my-app.tar.gz
drwxrwxr-x root/root 0 2019-12-02 18:26 master/
-rw-rw-r-- root/root 277 2019-12-02 18:26 master/README.md
-rw-rw-r-- root/root 167 2019-12-02 18:26 master/composer.json
-rw-rw-r-- root/root 3 2019-12-02 18:26 master/composer.lock
-rw-rw-r-- root/root 19 2019-12-02 18:26 master/index.php
And you can deploy it using Scalingo CLI:
$ scalingo --app my-app deploy my-app.tar.gz
-----> Deploying tarball archive: master.tar.gz
-----> Uploading archive…
Deployment started, streaming output:
[LOG] <-- Start deployment of my-app -->
[LOG] Fetching source code
[...]
[STATUS] New status: pushing
[LOG] Build complete, shipping your container...
[STATUS] New status: pushing → starting
[LOG] Waiting for your application to boot...
[LOG] <-- https://my-app.osc-fr1.scalingo.io -->
[STATUS] New status: starting → success
And After?
See Deployment Environment to configure your application and Procfile.
Last update: 18 Feb 2020
Suggest edits