-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Configuring base_url for sregistry when deployed behind an Apache reverse proxy on port 80 #441
Comments
The setup is built with Nginx, so first I’d start with modifying that configuration first (instead of putting it behind a different webserver). Then if you want to tweak the baseurl it should be in settings.py, and you can build a custom image. |
Hi vsoch, thank you for the suggestion. On the server I have apache, so I have to pass through it using a simple rewrite rule urlpatterns = [ url(r"^sregistry/django-rq/", include("django_rq.urls")), ] But I don't see css and images. Any suggestion about this? |
You likely want to look at your console logs to see the path that is being tried, and adjust accordingly. The roots are defined here: Lines 549 to 556 in 675fb4d
|
Hello,
I'm trying to deploy sregistry behind an Apache reverse proxy on port 80 and have run into some issues with the application's URLs. I've set up Apache to route requests from /sregistry to the sregistry application running on port 81, as I have other sites and configurations on my server.
Here's my current Apache configuration:
With this configuration, I'm able to access the sregistry homepage fine. However, some internal application links, like /collections and /login, are broken because they don't seem to be aware of the /sregistry prefix.
I assume there's a need to adjust a base_url or similar setting in the sregistry configuration to inform it of the /sregistry prefix. Could you provide guidance on how to properly configure this or point out if there's any step I might be overlooking?
Thank you for your assistance!
The text was updated successfully, but these errors were encountered: