generate random secret if there is no parameter named secret
"installAssets" can now install the assets using the --symlink option
merged branch francodacosta/master (PR #22)

Commits
-------

030a45e generate random secret if there is no parameter named secret

Discussion
----------

Generate random secret if there is no parameter named secret

For some weird reason after updating from symfony 2.0.1 to symfony-standard master branch I kept having undefined index secret errors, event though I had a parameter named secret in my parameters section of the config file (not in the .ini file)

This PR solves this issue by generating a random secret if I do not specify one
merged branch Seldaek/composer (PR #21)

Commits
-------

f9a6a52 Fix escaping

Discussion
----------

Fix escaping

Currently the symfony-standard stuff breaks if you have a space in your php path (which some windows users do when installing to Program Files), this is part 1 of the fix, part 2 needs you to make sure the https://github.com/symfony/Process split is up to date so I can update it in Composer (it needs the windows compatibility enhancement thing that got merged recently).
merged branch fixe/patch-1 (PR #20)

Commits
-------

4529670 "installAssets" can now install the assets using the --symlink option

Discussion
----------

Change "installAssets" method to accept --symlink option

```
# composer.json
    "extra": {
        "symfony-app-dir": "app",
        "symfony-web-dir": "web",
        "symfony-symlink": true

---------------------------------------------------------------------------

by stloyd at 2012-03-06T12:00:07Z

+1

---------------------------------------------------------------------------

by ericclemmons at 2012-03-19T00:53:45Z

There's also a `--relative` option as well which would be useful...

---------------------------------------------------------------------------

by Seldaek at 2012-03-22T13:14:43Z

I'm wondering if this wouldn't be best done with an env var or something that the script reads. This has two benefits:

- It's configurable per machine and not just per project so you do it once for your machine and forget about it
- It's configurable per machine and not just per project so those that don't want to use the feature in your project don't have to remove it from composer.json all the time

---------------------------------------------------------------------------

by fabpot at 2012-03-22T13:17:03Z

+1 for @Seldaek suggestion.

---------------------------------------------------------------------------

by Seldaek at 2012-03-22T13:19:52Z

That said, the "extra" key could still remain if you want to enforce it in your project, it might be easier in some cases than having everyone setup the env var. But I don't think it should be the only option because it's limiting.

I'd suggest symfony-symlink-assets in json and SYMFONY_SYMLINK_ASSETS env.

---------------------------------------------------------------------------

by ericclemmons at 2012-03-22T17:25:17Z

I'd say give preference to an environment variable, but allow the `extra` key.  That way we have project-specific settings that greatly simplify the process of large deployments on cloud machines, but allow for individualizing when it calls for it.

---------------------------------------------------------------------------

by fixe at 2012-03-22T23:34:06Z

Both options added.
fixed CS
Fix usage of new option for assets installation
merged branch stloyd/patch-1 (PR #23)

Commits
-------

5054e3c Fix usage of new option for assets installation

Discussion
----------

Fix usage of new option for assets installation
$options['symfony-assets-install'] is a string, not a bool
Merge pull request #24 from fixe/patch-2

$options['symfony-assets-install'] is a string, not a bool
fix asset install relative option
merged branch csanquer/patch_assets_2 (PR #27)

Commits
-------

bd04094 fix asset install relative option
e78f65f Merge pull request #24 from fixe/patch-2
9580eeb $options['symfony-assets-install'] is a string, not a bool

Discussion
----------

fix asset install relative option

the assets:install --symlink option was missing when using composer extra option relative
fixed CS
Build bootstrap started from a separate PHP process
Issue #28
merged branch krymen/build_bootstrap (PR #29)

Commits
-------

c202066 Build bootstrap started from a separate PHP process Issue #28

Discussion
----------

Build bootstrap started from a separate PHP process

Issue #28

---------------------------------------------------------------------------

by fabpot at 2012-04-19T12:55:23Z

Can you squash your commits? Thanks.

---------------------------------------------------------------------------

by krymen at 2012-04-19T13:18:11Z

Done
Restore colored output for unix (requires latest composer.phar)