Last active
November 19, 2020 19:03
-
-
Save pniederlag/09edfb18e7a1c8ec8620c3098d9f98cc to your computer and use it in GitHub Desktop.
TYPO3 multi-domain/site-config with selection by TYPO3_CONTEXT
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
| # example typo3 site-config for multi-site project with different instances/hosts by TYPO3_CONTEXT | |
| # (not verified/tested yet) | |
| rootPageId: 100 | |
| base: 'https://first-project.example.com/' | |
| baseVariants: | |
| - | |
| base: 'https://xx.example.local/' | |
| condition: 'applicationContext == "Development/Server1"' | |
| rootPageId: 200 | |
| base: 'https://second-project.example.com/' | |
| baseVariants: | |
| - | |
| base: 'https://yy.example.local/' | |
| condition: 'applicationContext == "Development/Server1"' | |
| # Can I re-use the very same applicationContext here ^^ ? | |
| # Bonus: Does this work with solr indexing config? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thx! :-> I was not even really refering to using different solr properties, I thought about connecting the site-root to the proper domain for the solr-indexing from the scheduler job. I think this is indeeed already solved by using the proper TYPO3_CONTEXT.
each solr-indexer scheduler task has configured a site-root... the site-root changes based on TYPO3_CONTEXT... that's quite fine and would be sufficient for me to be happy... I think it would work out that way.
For changing properties I could easily stick with conditions (as in the good ol' days) or flip to .env ... sounds great! :->