Morning Deployment.

Me: Let's add this application to this server.

Deployer: Alright.

...

D: Done. Please verify.

Me: I'm seeing errors. Send me the logs.

D: Sure. I also updated the framework to a version that wasn't tested.

M: Yeah, that won't work. Roll it back.

D: Fine.

...

D: Done. Please verify.

M: All the applications on the box are broken. Please revert to the snapshot before the Deployment.

D: Oops, I didn't make one.

🙁😟😢😭😤

If you publish a package over Composer - or in fact any package manager that allows optional dependencies - please don't make dependencies that aren't **absolutely necessary** required.

Is it a theme for your nice app? Don't make it required, some are not going to want to use this theme and don't want to deploy extra Megabytes to their servers every single time.

In fact, someone may even want to replace that dependency with a fork, like a customized version of that theme because it is not flexible enough! Forcing that dependency means it can only be replaced with hacks.

I am looking at you, `oxid-esales/oxideshop-metapackage-ce`, with your extra themes and demoshop data that makes the Deployer tool push and copy around half a Gigabyte of unused assets on a website every single deployment!!

To most non-dev people, being hit with error after error when fixing one small problem out of a much bigger collection of problems would probably be infuriating.

To me, it's a huge loop of:
for(var failsAtLine = 1; failsAtLine < lines.length; failsAtLine++;) {
changeSomething();
runTest();
readErrors();
cry();
comtemplateMeaningOfLife();
}

openChampagne();

Would help if deployer.org had better documentation and bigger support community.