Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fortrabbit deployment guide + index listing #6291

Closed
wants to merge 8 commits into from
Closed
Show file tree
Hide file tree
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
230 changes: 230 additions & 0 deletions cookbook/deployment/fortrabbit.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,230 @@
.. index::
single: Deployment; Deploying to fortrabbit.com

Deploying to fortrabbit
=======================

This step-by-step cookbook describes how to deploy a Symfony web application to
`fortrabbit`_. You can read more about using Symfony with fortrabbit on the
official fortrabbit `Symfony install guide`_.



Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We only use one blank line (same applies to several places below).

Setting up fortrabbit
---------------------

Before we begin, you should have done a few things on the fortrabbit side:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We avoid use "I" or "we" in the documentation.


- Sign up
- Add an SSH key to your Account (to deploy via Git)
- Create an App
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please use the * character for unordered item lists.



Preparing your Application
--------------------------

You don't need to change any code to deploy a Symfony application to fortrabbit.
But it requires some minor tweaks to its configuration.


Configure Logging
~~~~~~~~~~~~~~~~~

Per default Symfony logs to a file. Modify the app/config/config_prod.yml file
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please enclose the filename with literals (double backticks).

to redirect it to PHP's error_log():
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can use the phpfunction role to link to the PHP API documentation:

[...] redirect it to :phpfunction:`error_log`:


.. code-block:: yaml

monolog:
# ..
handlers:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indentation is wrong here and you could also add XML and PHP configuration examples:

.. configuration-block::

    .. code-block:: yaml

        # app/config/config_prod.yml
        monolog:
            # ...
            handlers:
                nested:
                    type: error_log

    .. code-block:: xml

        <!-- app/config/config_prod.xml -->
        <?xml version="1.0" encoding="UTF-8" ?>
        <container xmlns="http://symfony.com/schema/dic/services"
            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
            xmlns:monolog="http://symfony.com/schema/dic/monolog"
            xsi:schemaLocation="http://symfony.com/schema/dic/services
                http://symfony.com/schema/dic/services/services-1.0.xsd
                http://symfony.com/schema/dic/monolog
                http://symfony.com/schema/dic/monolog/monolog-1.0.xsd">

            <monolog:config>
                <!-- ... -->
                <monolog:handler
                    name="nested"
                    type="error_log"
                />
            </monolog:config>
        </container>

    .. code-block:: php

        // app/config/config_prod.php
        $container->loadFromExtension('monolog', array(
            // ...
            'handlers' => array(
                'nested' => array(
                    'type' => 'error_log',
                ),
            ),
        ));

# ..
nested:
type: error_log
# ..

Configuring Database Access & Session Handler
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

You can use the fortrabbit App Secrets to attain your database credentials.
Create the file app/config_prod_secrets.php with the following contents::

<?php
// Get the path to the secrects.json file
if (!$secrets = getenv("APP_SECRETS")) {
return;
}

// Read the file and decode json to an array
$secrets = json_decode(file_get_contents($secrets), true);

// Set database parameters to the container
if (isset($secrets['MYSQL'])) {

$container->setParameter('database_driver', 'pdo_mysql');
$container->setParameter('database_host', $secrets['MYSQL']['HOST']);
$container->setParameter('database_name', $secrets['MYSQL']['DATABASE']);
$container->setParameter('database_user', $secrets['MYSQL']['USER']);
$container->setParameter('database_password', $secrets['MYSQL']['PASSWORD']);
}

// Check if the Memcache component is present
if (isset($secrets['MEMCACHE'])) {

$memcache = $secrets['MEMCACHE'];
$handlers = [];

foreach (range(1, $memcache['COUNT']) as $num) {
$handlers [] = $memcache['HOST'. $num]. ':'. $memcache['PORT'. $num];
}

// Apply ini settings
ini_set('session.save_handler', 'memcached');
ini_set('session.save_path', implode(',', $handlers));

if ($memcache['COUNT'] == 2) {
ini_set('memcached.sess_number_of_replicas', 1);
ini_set('memcached.sess_consistent_hash', 1);
ini_set('memcached.sess_binary', 1);
}

}


Make sure this file is listed in your *imports*:

.. code-block:: yaml
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add config formats for XML and PHP too (like above)? Just let us know in case you need some assitance with the other formats.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about the correct nesting/structure here...

            <framework:config>
                <framework:session>
                    ?? handler_id:  ~
                </framework:session>
            </framework:config>

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

got it!

<framework:config>
    <framework:session handler_id="null" />
</framework:config>


# app/config/config_prod.yml
imports:
- { resource: config.yml }
- { resource: config_prod_secrets.php }

# ..
framework:
session:
# set handler_id to null to use default session handler from php.ini (memcached)
handler_id: ~
# ..



Configuring the Environment in the Dashboard
--------------------------------------------

PHP Settings
~~~~~~~~~~~~

The PHP version and enabled extensions are configuable under the PHP settings
of your App within the fortrabbit Dashboard.


Environment Variables
~~~~~~~~~~~~~~~~~~~~~

Set the ``SYMFONY_ENV`` environment variable to ``prod`` to make sure the right
config files get loaded. ENV vars are configuable in fortrabbit Dashboard as well.


Document Root
~~~~~~~~~~~~~

The document root is configuable for every custom domain you setup for your App.
The default is /htdocs, but for Symfony you probably want to change it to
/htdocs/web. You also do so in the fortrabbit Dashboard under ``Domain`` settings.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Paths here should be enclosed with double backticks (can you check the rest of the document too?).



Deploying to fortrabbit
-----------------------

It is assumed that your codebase is under version-control with Git and dependencies
are managed with Composer (locally).

Every time you push to fortrabbit composer install runs before your code gets
deployed. To finetune the deployment behavior put a `fortrabbit.yml`_. deployment
file (optional) in the project root.

Add fortrabbit as a (additional) Git remote and add your configuration changes.

.. code-block:: bash

$ git remote add fortrabbit git@deploy.eu2.frbit.com:your-app.git
$ git add composer.json composer.lock
$ git add app/config/config_prod_secrets.php

Commit and push

.. code-block:: bash

$ git commit -m 'fortrabbit config'
$ git push fortrabbit master -u


.. note::

Replace your-app with the name of your fortrabbit App.


.. code-block:: bash

Commit received, starting build of branch master

––––––––––––––––––––––– ∙ƒ –––––––––––––––––––––––

B U I L D

Checksum:
def1bb29911a62de26b1ddac6ef97fc76a5c647b

Deployment file:
fortrabbit.yml

Pre-script:
not found
0ms

Composer:
- - -
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Nothing to install or update
Generating autoload files

- - -
172ms

Post-script:
not found
0ms

R E L E A S E

Packaging:
930ms

Revision:
1455788127289043421.def1bb29911a62de26b1ddac6ef97fc76a5c647b

Size:
9.7MB

Uploading:
500ms

Build & release done in 1625ms, now queued for final distribution.


.. note::

The first ``git push`` takes much longer as all composer dependencies get
downloaded. All subsequent deploys are done within seconds.


That's it! Your application is being deployed on fortrabbit. More information
about `database migrations and tunneling`_ can be found in the fortrabbit
documentation.

.. _`fortrabbit`: http://www.fortrabbit.com
.. _`symfony install guide`: http://help.fortrabbit.com/install-symfony
.. _`fortrabbit.yml`: http://help.fortrabbit.com/deployment-file-v2
.. _`database migrations and tunneling`: http://help.fortrabbit.com/install-symfony-2#toc-migrate-amp-other-database-commands
1 change: 1 addition & 0 deletions cookbook/deployment/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -8,3 +8,4 @@ Deployment
azure-website
heroku
platformsh
fortrabbit
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We also need to add an entry to /cookbook/map.rst.inc to make the article appear on the index too.