上线步骤-Symfony2

Question

I've been working on my website for some time now and I am now ready to push this brand new project to live.

I have already already read this link on Symfony2 with regards to what should be done, but I still think it is missing some details. For example, it talks nothing about some of the commands that I run to get the site to work on live.

Currently this is what I would like to do to get this to work on live:

php composer.phar install --no-dev --optimize-autoloader --no-scripts
rm -rf app/cache/* 
php app/console assetic:dump --env=prod --no-debug 
php app/console assets:install web --symlink --env=prod

Is there anything else that needs to be done, for example, I don't want live to be able to execute my fixtures, nor do I want any users to be able to go to www.mysite.com/app_dev.php

Answer 1

Check out How to deploy a Symfony2 application .

Refer to link above. The typical steps taken while deploying a Symfony2 application include:

1. Upload your modified code to the live server;
2. Update your vendor dependencies (typically done via Composer, and may be done before uploading);
3. Running database migrations or similar tasks to update any changed data structures;
4. Clearing (and perhaps more importantly, warming up) your cache.

Common Post-Deployment Tasks

1. Configure your app/config/parameters.yml file

2. Update your vendors

   $ php composer.phar install --no-dev --optimize-autoloader

3. Clear your Symfony cache

   $ php app/console cache:clear --env=prod --no-debug

4. Dump your Assetic assets

   $ php app/console assetic:dump --env=prod --no-debug

5. Other things!

There may be lots of other things that you need to do, depending on your setup:

• Running any database migrations
• Clearing your APC cache
• Running assets:install (taken care of already in composer.phar install)
• Add/edit CRON jobs
• Pushing assets to a CDN
• ...

Answer 2

take a look at capifony ( https://github.com/everzet/capifony ). Unfortunately the Website ( http://capifony.org ) is currently down..

Answer 3

The best solution to me is to have your project in a versionning system like git or svn without the vendors dir of course ...

This way, your simply have to do :

1) git clone your project into the prod dir

2) php composer.phar install to install your vendors

2b) create the mysql user with correct login and password according to your parameters.yml

 3) php app/console doctrine:database:create to create your database with the credentials you set up in mysql

 4) php app/console doctrine:schema:update --force to perform the database tables creation
 5) testing the project :)

If you are not using a versionning system just upload your project to your server with an ftp software without the vendors directory ( it will be feeded by step 2) then perform 3rd , 4th and 5th steps !

you now should be able to reach you project through you domain url .