[FEATURE] Add command "init" to configure platform install for legacy bridge usage#147
Conversation
c08267e to
ab43a22
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
ab43a22 to
0b06e0d
Compare
This comment has been minimized.
This comment has been minimized.
0b06e0d to
103870d
Compare
|
@emodric what do you think? ref:
|
emodric
left a comment
There was a problem hiding this comment.
This looks good (with one minor remark about spelling). What is missing is some docs on the intended usage workflow (init and then symlink?).
| <<<EOT | ||
| The command <info>%command.name%</info> creates the following folders for migration usage: | ||
| - src/AppBundle/ezpublish_legacy => Optionaly for extensions you want to version in your project source (as opposed to install using composer) | ||
| - src/legacy_files/design => Optionally for cusotm designs not already made part of an extension |
|
@emodric PR description updated to reflect better the overall workflow I'm suggesting here. This might be something @vidarl, @crevillo, @joekepley and @peterkeung might want to give input on as well here. |
e348452 to
2bfe4ce
Compare
|
Implemented "Adjust composer.json as current described in INSTALL doc automatically"... |
| $updateComposerJson = true; | ||
| } elseif (!in_array('@legacy-scripts', $composerJson['scripts']['symfony-scripts'])) { | ||
| $symfonyScripts = $composerJson['scripts']['symfony-scripts']; | ||
| $offset = array_search('@php bin/console assetic:dump', $symfonyScripts); |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
| legacy install: | ||
| - <info>ezpublish:legacy:symlink</info> | ||
| - <info>ezpublish:legacybundles:install_extensions</info> | ||
| - <info>ezpublish:legacy:assets_install</info> |
There was a problem hiding this comment.
these can now be changed to composer legacy-scripts
| } | ||
|
|
||
| if (!array_key_exists('symfony-scripts', $composerJson['scripts'])) { | ||
| $composerJson['scripts']['symfony-scripts'] = ['@legacy-scripts']; |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
89fcfce to
217b792
Compare
9516554 to
1280828
Compare
This comment has been minimized.
This comment has been minimized.
7c18f2e to
f1b2798
Compare
Move creation of intial structure for migration to own command to also cover needs for creating extension folder.
6e5b264 to
01f9893
Compare
Co-Authored-By: andrerom <andre.romcke@gmail.com>
Co-Authored-By: andrerom <andre.romcke@gmail.com>
Co-Authored-By: andrerom <andre.romcke@gmail.com>
Co-Authored-By: andrerom <andre.romcke@gmail.com>
|
I'd like to see manual install instructions preserved in a separate file, as I don't like to rely on scripted installations 100%. Otherwise, looks good. |
|
@emodric Better?
|
In order to simplify upgrades from pure legacy installs, this command is meant to be used like this to simplify install / upgrades (in comparison to todays INSTALL.md, which does not cover upgrades, and is a bit more manual still):
initwhich will:Optional: Enable legacy_mode for your backoffice siteaccessOptional: add security rules for the Setup WizardOptional: Ask user to install recommended extensions / bundles (search ext, richtext ext, ..)composer run-script post-update-cmdonce things have been moved into folders, or maybe rathercomposer legacy-scripts