Created
November 24, 2012 10:29
-
-
Save mattwillsher/4139117 to your computer and use it in GitHub Desktop.
Capifony evaluation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| + Backs up DB | |
| - Poor db permission handling | |
| - Bad data hygiene, db can be copied prod to dev, dev to prod | |
| - dumps assets at the remote end, potentially increasing dependencies (e.g. node, java) | |
| - installs vendors/bundles at the remote end | |
| - installs composer via curl | via shell (even as root!) | |
| - uncontrolled composer versioning for composer itself. update installs the latest via the curl | shell method. | |
| + Comprehensive control of post installation tasks | |
| + Can deploy as non-root user | |
| - Symlinks add overhead | |
| + Seeming largely OS agnostic though deb task implies Ubuntu/Debian leanings (couldn't find source for deb task) | |
| - Couldn't find any control of app server | |
| - No environment configuration | |
| = What's an optimized autoloaded? Do we want it ? | |
| = Why normalise asset timestamps? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment