You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
:description: First steps for developers using Deis to deploy and scale applications.
2
+
:description: First steps for developers using Deis to deploy and manage applications
3
+
4
+
.. _deploy-application:
3
5
4
6
Deploy an Application
5
7
=====================
8
+
An :ref:`Application` is deployed to Deis using ``git push`` or the ``deis`` client.
9
+
10
+
Supported Applications
11
+
----------------------
12
+
Deis can deploy any application or service that can run inside a Docker container. In order to be scaled horizontally, applications must follow Heroku's `twelve-factor methodology`_ and store state in external backing services.
6
13
7
-
An :ref:`Application` is typically deployed to Deis by pushing source code using the deis
8
-
client or other clients that communicate with Deis' API endpoints. Deploying
9
-
applications will be different depending on the source code and its requirements.
14
+
For example, if your application persists state to the local filesystem -- common with content management systems like Wordpress and Drupal -- it cannot be scaled horizonally using ``deis scale``.
10
15
11
-
Authenticating with the API
12
-
---------------------------
16
+
Fortunately, most modern applications feature a stateless application tier that can scale horizontally inside Deis.
13
17
14
-
Before deploying an application, all users must first authenticate against the Deis
15
-
:ref:`Controller`. For example:
18
+
Login to the Controller
19
+
-----------------------
20
+
Before deploying an application, users must first authenticate against the Deis :ref:`Controller`.
16
21
17
22
.. code-block:: console
18
23
@@ -21,113 +26,28 @@ Before deploying an application, all users must first authenticate against the D
21
26
password:
22
27
Logged in as deis
23
28
24
-
Create an Application
25
-
---------------------
26
-
27
-
Change to the root directory of your project you'd like to deploy, then use the ``deis
28
-
create`` command to create a remote repository for you to push your application to.
29
-
30
-
.. code-block:: console
29
+
Select a Build Process
30
+
----------------------
31
+
Deis supports three different ways of building applications:
31
32
32
-
$ cd example-java-jetty # change into your application's git root
33
-
$ deis create --cluster=dev
34
-
Creating application... done, created peachy-waxworks
35
-
Git remote deis added
33
+
1. `Heroku Buildpacks`_
34
+
2. `Dockerfiles`_
35
+
3. `Docker Image`_ (coming soon)
36
36
37
-
Deploy the Application
38
-
----------------------
37
+
Buildpacks
38
+
^^^^^^^^^^
39
+
Heroku buildpacks are useful if you want to follow Heroku's best practices for building applications or if you are porting an application from Heroku.
39
40
40
-
With the application created and associated with the SSH :ref:`Key` on your account,
41
-
deploy it with ``git push deis master``. If you don't have an application to test with,
42
-
you can use `our Dockerfile example`_.
41
+
Learn how to use deploy applications on Deis :ref:`using-buildpacks`.
43
42
44
-
.. code-block:: console
43
+
Dockerfiles
44
+
^^^^^^^^^^^
45
+
Dockerfiles are a powerful way to define a portable execution environment built on a base OS of your choosing.
45
46
46
-
><> deis create --cluster=dev
47
-
Creating application... done, created owlish-huntress
0 commit comments