search

magento-hackathon / magento-composer-installer

Composer installer for Magento modules
210 stars 154 forks source link

Deployment type option #66

Closed maderlock closed 10 years ago

maderlock commented 10 years ago

Is it currently possible to specify one deployment type for dev and one for production? Obviously symlinking is most flexible for development, but for a number of reasons I would rather deploy to live using copy.

If it isn't possible, I would like to request this as an improvement.

Schrank commented 10 years ago

You can use a second composer.json for live.

How do you want to differ between live and dev?

Flyingmana commented 10 years ago

to use magento related words:
You should have different local.xml for dev and live, because things are different. The same for composer.

Also: you should always test with the deploy method used on live, as you never know, if they act completely the same.

maderlock commented 10 years ago

Well, no - by the same argument, you should be using a single composer.json file for development and live. Otherwise how do you know that the mappings are correct? The files could differ.

Yes, you should test the deploy mechanism. That is why you use a staging server.

What this tells me is that the deployment option needs to be controlled via the command line, so that a build script can specify this option. I will add this in a fork.