-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simplify install and add EE support with eZ Platform 1.11 + legacy 2017.08 #98
Conversation
Bump: - legacy installer in order to skip install step about defining `ezpublish-legacy-dir` - legacy kernel to be able to skip install steps about setting `EZP_APP_FOLDER_NAME`
Is Other than that, 👍 |
composer.json
Outdated
"ezsystems/ezpublish-legacy": ">=2014.11", | ||
"ezsystems/ezpublish-kernel": "~6.0@dev", | ||
"ezsystems/ezpublish-legacy-installer": "^2.0.4", | ||
"ezsystems/ezpublish-legacy": ">=2017.08", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be 2017.07
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, that was what I first called it, but if we aim for parity with the features in the milestone, then that needs work also on platform side, hence 1.11 => august => 08 :)
I'm fine with that, but depends on if you or others have suggestions for what else we can do to further simplify the steps*. * Like both you, @Plopix and @crevillo has attempted before. For instance could we add handling of legacy-installer to do some of the remaining steps? Among them enabling bundle and/or add post-update-cmd steps to composer.json |
Not right now, no. |
We can try, but then composer would need to be ran twice, to take into account the new bundle and new scripts, which IMO is worse for DX than simply adding those beforehand. Also, in cases where some of the legacy scripts are replaced by an overriden variant (for whatever reason), automatic update of |
There are some settings to provide by default, to set up the Admin siteaccess etc. |
If we don't have other changes that don't require a major version, I'd rather go with a minor one. When we have identified and implemented the changes that require one, we can still do it. But I have no strong feelings here and might be missing something. Good idea in any case ! |
Changed to 1.3.0
@Plopix What did you have in mind here? something you think we can add here by default somehow? |
@andrerom Maybe something like this: https://github.com/emodric/ezplatform-legacy/tree/master/ezpublish_legacy/settings ? |
INSTALL.md
Outdated
"extra": { | ||
"ezpublish-legacy-dir": "ezpublish_legacy", | ||
``` | ||
|
||
### Install `ezsystems/legacy-bridge` | ||
|
||
**Make sure you have set the ezpublish legacy folder in composer.json, as instructed above** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
needs to be removed, but done in #103
Anything in particular there you mean we should inject via the bridge, or implying we should trigger legacy config generation somehow? |
I don't think there's a need to generate anything. Nowdays, legacy bridge is used mostly for legacy admin, so just copying |
hmm, well opting for |
It can be done, sure. BTW, we're using Twig internally to do it when needed :) |
Sorry long delay for this reply. Yes I was thinking about the settings for the Legacy Admin (basically everything we can't inject through the new stack) |
I would keep it optional in any case if done, not to collide with already existing configuration in existing sites. |
passing now, I assume your approval still stands @emodric ? :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(tiny speling nitpick)
INSTALL.md
Outdated
### Install `ezsystems/legacy-bridge` | ||
|
||
**Make sure you have set the ezpublish legacy folder in composer.json, as instructed above** | ||
`ezsystems/legacy-bridge` contains the libraries previous included in `ezsystems/ezpublish-kernel` in version 5.x. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
previously included
Proposal for a
2.0.01.3.0
release of legacy bridge, with aim to simplify installation. Implied in this simplification is also the need to provide a new legacy kernel release for use by community as well as potentially also eZ Enterprise users*.There might also be other things that can be simplified, suggestions (PR's) welcome :)
* Afaik 5.4 legacy can't have features found in the 2017.08 milestone below needed for eZ Platform compatibility, and we don't intend to do a 5.5 release.
Bumps:
ezpublish-legacy-dir
EZP_APP_FOLDER_NAME
TODO: