ochorocho / joro-typo3reversedeployment Goto Github PK

Export DB: cd /kunden/homepages/XX/XXXXXXXXX/htdocs/staging/releases/current/html/ && php ../vendor/bin/typo3cms database:export 
rsync: change_dir "/kunden/homepages/XX/XXXXXXXXX/htdocs/staging/releases/current/html/typo3temp/joro_typo3reversedeployment" failed: No such file or directory (2)
rsync error: some files could not be transferred (code 23) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-51/rsync/main.c(1404) [receiver=2.6.9]

When starting the reverser deployment on a 1&1-Server the error message above occurs and no database is being downloaded. Fileadmin works just fine.

After creating the asked directory joro_typo3reversedeployment in typo3temp folder, the download of the dump worked.

Some hosters (e.g. Mittwald) require a non-default path to PHP command.

At the moment, the typo3cms binary is only searched in ../vendor/bin. The deployment tool should support non-composer-based installations and automatically detect, if the binary is installed in composer mode or non-composer mode.

It would be nice if ddev is used in the to do some nice stuff.
E.g. auto-import downloaded mysql-dump

I followed your example in your readme. But all I see, is "Login Failed" :-(

Send keepAlive to make connection persist during long server side operations.

Seems like for security reasons some ssh servers do not send keepAlive to the client and therefore the connections is dropped after a certain time.

According to TYPO3 Surf its possible to read a php file as configuration and execute via a php "binary"

like this:

typo3reverse myconfig

It would be nice to have the option to export/reverse deploy from a docker container.

On some servers we need to add the path to the php cli executable for typo3cms calls:

X-Powered-By: PHP/4.4.9
Content-type: text/html

This version of TYPO3 Console requires PHP 7.0.0 or above!
Your PHP version is: 4.4.9
Please specify a suitable PHP cli binary before the typo3cms binary like that:
/path/to/php70-latest ../vendor/bin/typo3cms

It would be nice to automatically create a phar file for standalone usage when a new tag was created.

https://pantheon.io/blog/automate-phar-releases-github-travisci

It would be great to have more configuration options for downloading the files

• download all files, ingnoring sys_file_reference
• exclude folders (e.g. fileadmin/_processed_)
• download additional folders with different names (e.g. /uploads)

If the script will abort, the file keeps accessible via HTTP. Ideas to solve this:

• Use ../ (relative to webroot) to save the dump. You require a composer folder structure to access typo3cms, so it should not be a problem to have write access to this root folder.
• Dynamically create a dedicated folder inside typo3temp and automatically add a .htaccess file to protect files.
• Let user configure the path.

• Add detailed reqirements: typo3-console, rsync, typo3-composer install (> 8.7)
• Explain features in Detail
• Publish doxygen docs (via GitHub Pages)

What does not work for you?
/vendor/bin/typo3cms is no longer a proper approach since it was removed...

What is your suggestion to fix/improve this?
...but from my testing the only change required was setting
$reverseDeploy->setPathToConsoleExecutable('../vendor/bin/typo3');
in reverse configuration file and so far it works flawlessly.

Allow user to set SSH Port

With the last change on this line, the reverse deployment tool can't fetch the LocalConfiguration.php file.

Error Message:
PHP Parse error: syntax error, unexpected 'in' (T_STRING) in /[...]/vendor/joro/typo3reversedeployment/JoRo/Typo3ReverseDeployment.php(404) : eval()'d code on line 1

The old implementation $remoteConf = $ssh->exec('cat ' . $path . '/typo3conf/LocalConfiguration.php'); works.

It would be nice if theres is an option to uglify certain data (customer data) which should be invisible by the programmer.

e.g. user.name = Bart Simpson change automatically to something random like "elBarto" (different on every export)

Use something like this: https://packagist.org/packages/greenlion/php-sql-parser

1. Use correct calls:

$reverseDeploy->setFileTarget("./fileadmin/");
$reverseDeploy->getFiles($ssh);

2. Use more generic example data for username and host

3. You can use exact file name ./folder/dump.sql in setSqlTarget function or you use a folder ./dump/, wich results in generic file names like 2018031336-db722877585.sql

The setIncludes/setExcludes, but it would be great to have methods, to keep the existing values and add some more without overwriting everything.

What does not work for you?

How do you think it should work?

It should work with newer php versions

What is your suggestion to fix/improve this?

Check compatibility and raise php dependencies in composer.json

The environment variable should be configurable and if set, it should be prepended to all php commands.

And when reading the local configuration, the file AdditionalConfiguration.php should be included, to get the correct settings.