-
-
Notifications
You must be signed in to change notification settings - Fork 122
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
Default domain feature: Allow secondary domain #405
Comments
@readtedium Have you considered nginx proxy as a solution?
|
This required me to set up a separate NGINX proxy to reach my S3 bucket (this was a good guide), but once I did that, I found @AlekseyArh’s suggestion to be a good solve. This idea may still be useful for those who don’t want to have to manage an additional NGINX proxy, though. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bouncing off the great work done in #309, is it possible to add an override, or maybe an alternate? I think it might come in handy to have a default base URL but if you need to grab from a different domain than the default.
I mostly grab from one domain, but sometimes I grab from a second; currently the tool forces me to use long URLs for both, but I think adding the option for additional variables could be useful. One way I could see it working:
In .env:
First example (uses BASE_URL):
Second example (uses ALT_URL):
Third example (with a watermark pulled from the base URL):
The one challenge I see is that if there’s a folder named
ALT_URL
it would override this, but I do think there’s probably a way to solve this, maybe by using a filter?The text was updated successfully, but these errors were encountered: