-
Notifications
You must be signed in to change notification settings - Fork 40
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
[FEATURE] Allow overriding "web-dir" with environment variable #146
base: main
Are you sure you want to change the base?
Conversation
The Core uses TYPO3_PATH_ROOT for all paths related to the document root. The PackageArtifactBuilder (inside Core) uses the web-dir to create the _assets symlinks. Consequently, the web-dir must adhere to the TYPO3_PATH_ROOT variable as well, in order to get a properly set up frontend. Resolves: TYPO3#145
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.
I'm sorry, this does not work out like this. Please provide more concrete examples of what you are trying to achieve in #145
I'll close this for now. Let's discuss #145 first |
This reverts commit 894a40f.
For some edge cases it might be useful to override, what is defined in the root composer.json file for the web-dir, to allow different web directories for different environments, without changing the root composer.json
I backported this change to v3.1 now in my fork (but with using We should merge this for v4 and v5. |
@liayn Thanks. I finally asked the core team for feedback. Pretty sure this will not end up in 3.1 though, as the impact of changing the web-dir is quite different here.
v4 is only a release candidate and will never be published as stable. So not going to be merged there either. So we're discussing putting that into v5.
Using an identical name for different things would cause more confusion than it would help imho. All |
Right, I simply set As said above, I have absolutely no problem with a dedicated ENV var for this (build time) purpose, but it will/must influence the runtime variable |
@helhum Can we get this one finished? |
@liayn can you elaborate a bit more? If I understand correctly, setting |
@bmack Thanks for picking this up. I'll gladly explain. We are not in the position to request changes to F5 (or whatever reverse proxy they are using rightnow)
No, this is absolutely not the case. The env var only changes the web-dir to a different folder, everything works like normal. We have this setup running with a v11 instance now for a long time. I'll gladly show you the instance and the setup in person as this thread here got quite lengthy over time. |
Another alternative is manually creating a symlink to the public folder, that matches the desired structure.
The existing env var and the env var introduced here have very little in common. The existing In fact, they have so little in common, that I would find it very confusing to use the same env var name for it. @bmack setting |
I asked for feedback in the core team months ago and a few days ago again and feedback was very reluctant. My / our biggest concern still is, that people will misuse this somehow, where a more simple solution is possible. That said, I still did not fully understand, why any other option we discussed, did not work for you. |
Thanks for that. We have exactly 2 customers with a setup like this. The first one, we created quite some years back, I wasn't aware of this issue here, but we had access to the reverse proxy and could make some changes there to make it work.
The only "more simple solution" I have on my radar, is the suggestion to create the symlink. I honestly forgot what the problem was there, but I'll gladly give this a shot. My whole goal of this patch is:
Explanation for @bmack how I came to my initial patch as can be seen here: bfb7648 In |
Just a note that this kind of setup (public dir as a subfolder of docroot) is not a specialty of mine: Issue filed for a bug exactly in this usecase: https://forge.typo3.org/issues/103157 |
For some edge cases it might be useful to override, what is defined
in the root composer.json file for the web-dir, to allow
different web directories for different environments, without
changing the root composer.json
Resolves: #145