-
Notifications
You must be signed in to change notification settings - Fork 163
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
Banner links dont work in local build #496
Comments
cc @missBerg - i think you mentioned this |
@phlax can i work on this ? |
@MAVRICK-1 for sure - that would be appreciated this is for the probably the easiest way to resolve is adding a custom nginx config with something like: server {
listen 80;
server_name yourdomain.com;
location / {
try_files $uri $uri.html $uri/ =404;
}
} |
Okay I'm working on it
…On Thu, 12 Dec 2024, 15:43 phlax, ***@***.***> wrote:
@MAVRICK-1 <https://github.com/MAVRICK-1> for sure - that would be
appreciated
this is for the static target in docker-compose
probably the easiest way to resolve is adding a custom nginx config with
something like:
server {
listen 80;
server_name yourdomain.com;
location / {
try_files $uri $uri.html $uri/ =404;
}
}
—
Reply to this email directly, view it on GitHub
<#496 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDBQOEN622OVZ5POVW6INTD2FFOVXAVCNFSM6AAAAABTN5I2T2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZYGQ2TENZUG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
this is partially fixed by the layout in the new website theme relatedly, i also have an nginx file which resolves a similar issue and can be adapted if needed |
i think this more/less fixed now - we also have an inline nginx config so we can adapt it if there are issues - but i think we can close this |
Currently if you build locally the banner links - ie:
they 404
the reason for this is that the links are to eg
training
rather thantraining.html
- on the real website netlify mangles/redirects thesefixing this is not trivial - we would need to add some nginx config (or similar) to do it.
relatedly the main link goes to the envoy website not to the local site root. This should be an easier fix
The text was updated successfully, but these errors were encountered: