@@ -8,21 +8,19 @@ This step-by-step cookbook describes how to deploy a Symfony web application to
88`Platform.sh `_. You can read more about using Symfony with Platform.sh on the
99official `Platform.sh documentation `_.
1010
11- Deploy anexisting site
11+ Deploy anExisting Site
1212-----------------------
1313
14- In this guide,we assume your codebase is already versioned with Git.
14+ In this guide,it is assumed your codebase is already versioned with Git.
1515
16- Get aproject on Platform.sh
16+ Get aProject on Platform.sh
1717~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1818
1919You need to subscribe to a `Platform.sh project `_. Choose the development plan
20- and go through the checkout process.
20+ and go through the checkout process. Once your project is ready, give it a name
21+ and choose: **Import an existing site **.
2122
22- Once your project is ready, give it a name and choose: **Import an existing
23- site **.
24-
25- Prepare your Application
23+ Prepare Your Application
2624~~~~~~~~~~~~~~~~~~~~~~~~
2725
2826To deploy your Symfony application on Platform.sh, you simply need to add a
@@ -32,6 +30,7 @@ configuration files`_).
3230
3331..code-block ::yaml
3432
33+ # .platform.app.yaml
3534# This file describes an application. You can have multiple applications
3635# in the same project.
3736
@@ -71,13 +70,6 @@ configuration files`_).
7170deploy :|
7271 app/console --env=prod cache:clear
7372
74- # The configuration of scheduled execution.
75- # see http://symfony.com/doc/current/components/console/introduction.html
76- # crons:
77- # symfony:
78- # spec: "*/20 * * * *"
79- # cmd: "php cron.php example:test"
80-
8173 For best practices, you should also add a ``.platform `` folder at the root of
8274your Git repository which contains the following files:
8375
@@ -97,13 +89,13 @@ your Git repository which contains the following files:
9789
9890 An example of these configurations can be found on `GitHub `_.
9991
100- Configuredatabase access
92+ ConfigureDatabase Access
10193~~~~~~~~~~~~~~~~~~~~~~~~~
10294
10395Platform.sh overrides your database specific configuration via importing the
10496following file:
10597
106- ..code-block ::yaml
98+ ..code-block ::php
10799
108100 # app/config/parameters_platform.php
109101 <?php
@@ -128,7 +120,7 @@ following file:
128120 $container->setParameter('database_path', '');
129121 }
130122
131- # Hack .
123+ #Store session into /tmp .
132124 ini_set('session.save_path', '/tmp/sessions');
133125
134126 Make sure this file is listed in your *imports *:
@@ -147,7 +139,11 @@ command that you see on the Platform.sh web UI):
147139
148140..code-block ::bash
149141
150- $ git remote add platform kjh43kbobssae@git.eu.platform.sh:kjh43kbobssae.git
142+ $ git remote add platform [PROJECT-ID]@git.[CLUSTER].platform.sh:[PROJECT].git
143+
144+
145+ * PROJECT-ID: Unique identifier of your project. Something like: *kjh43kbobssae *.
146+ * CLUSTER: Server location where your project is deployed. It can be *eu * or *us *.
151147
152148Commit the Platform.sh specific files created in the previous section:
153149
@@ -179,7 +175,7 @@ Push your code base to the newly added remote:
179175 That's it! Your application is being deployed on Platform.sh and you'll soon be
180176able to access it in your browser.
181177
182- Deploy a newsite
178+ Deploy a newSite
183179-----------------
184180
185181You can start a new `Platform.sh project `_. Choose the development plan and go