fix: Remove SiteAccess generation and rely on manual configuration #184
Conversation
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
This was referenced Dec 15, 2017
mateuszdebinski
pushed a commit
that referenced
this pull request
Oct 25, 2022
…in the content tree (#184)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We don't need siteaccess autoconfiguration anymore. We should create manually an admin siteaccess in
ezplatform.ymlconfig file.Ping @DominikaK - I guess we should document that in case of multisite with multiple admin panels, user should create additional siteaccesses manually and add them to
admin_groupgroup. By default, we'll have one siteaccess configured meta repository with nameadmin.Checklist:
$ composer fix-cs)