xima-media / xima-deployer-extended-typo3 Goto Github PK

The database dumps created by deployer ({{deploy_path}}/.dep/database/dumps) are not encrypted and therefore a potentially security risk.

It would be nice to extend the db:compress/ db:decompress commands for a password option of the gzip command.

This feature could be used as a PR for deployer-extended-database

Add TYPO3 labels ( 'var/labels',) to upload_paths

If composer is not available on the target system, it needs to be installed during the deployment process.

This recipe contains an example install: deploy/vendors.php (composer.phar is installed once)

Umask controls what file permissions are set for newly created files. A wrong umask means that Deployer will create new files with too restrictive or too open permissions.

Its default value can differ between servers and is usually set in ~/.bashrc or /etc/profile, /etc/pam.d/common-session or /etc/bash.bashrc.

However, it can also be set during the current session with the command umask xxxx before creating new files.

# show current umask
:~$ umask
0002
:~$ touch test
:~$ ls -l test 
-rw-rw-r-- 1 user group 0 16. Mai 15:27 test

# change umask
:~$ umask 0027
:~$ touch test2
:~$ ls -l test2
-rw-r----- 1 user group 0 16. Mai 15:28 test2

To eliminate this external dependency, the correct umask should be set by Deployer before executing file operations.

umask 0027
# create new files

As each deployer task can be executed individually and would then run in an isolated session, it would not make much sense to create a Deployer task that sets the umask before other tasks are executed.

Extending the run() command, so that the umask is set prior to all commands executed within that task, may be the better solution. Maybe this should also happen for runLocally()

Make files to upload configurable in "deploy:upload_code" for non-git deployment

This deployment configuration assumes a couple of settings that need to be done before doing a deployment. It would be nice to have an automated test of these server requirements. The PR #6 by @martipoe already contains some of these checks.