How to set root context url?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

How to set root context url?

greenaj
We are running Artifactory Pro 4.7.4 installed using the jfrog repo on CentOS 7. I want to get rid of /artifactory in the URL. Why is this so hard? Seems like this should be a simple Tomcat 8 configuration setting. Doing it in the NGINX reverse proxy setup seems nasty; a bunch of rewrite rules to maintain. I have tried changing the Tomcat config files and have had zero success. Is /artifactory forever baked into the URL and it is not worth it to remove? Seems like jfrom docs need a much better explanation for this. Get a nice root context with the port in the URL for the Tomcat setup, and we use a simple reverse proxy Apache/NGINX setup to nix the port.
Reply | Threaded
Open this post in threaded view
|

Re: [#40038] How to set root context url?

JFrog Support
Hi Aris,

Thank you for contacting JFrog Support.

We don't recommend removing the internal context path of Artifactory by modifying the tomcat configuration which is bundled with Artifactory. 
However, this can indeed be achieved by a reverse proxy configuration.
Check the following auto generator configuration feature which enable you to generate configuration files on nginx or apache based on information you are providing it.
You can leave the Public Context Path empty and in this case the the Artifactory will be accessible on the root of the server:
<public server name = custom url base>/

Please let us know for any further inquiries.

Best regards
Avi Zaig
JFrog Support




On Thu, 5 May at 8:00 PM , greenaj <[hidden email]> wrote:
We are running Artifactory Pro 4.7.4 installed using the jfrog repo on CentOS
7. I want to get rid of /artifactory in the URL. Why is this so hard? Seems
like this should be a simple Tomcat 8 configuration setting. Doing it in the
NGINX reverse proxy setup seems nasty; a bunch of rewrite rules to maintain.
I have tried changing the Tomcat config files and have had zero success. Is
/artifactory forever baked into the URL and it is not worth it to remove?
Seems like jfrom docs need a much better explanation for this. Get a nice
root context with the port in the URL for the Tomcat setup, and we use a
simple reverse proxy Apache/NGINX setup to nix the port.
40038

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
Reply | Threaded
Open this post in threaded view
|

Re: How to set root context url?

dragon788
In reply to this post by greenaj
It is possible to change the root URL, but you need to both change the URL in the Tomcat settings AND move the artifactory.war file from a subdirectory in WEBROOT directly to the root. This can lead to some weirdness, so the suggestion we've received is to use the zip file and deploy with a configuration management script rather than installing the RPM/deb and attempting to change the paths around.

For best performance if you can use a reverse proxy it is suggested to use Apache, because it can handle the Java authentication proxy required to make Artifactory work well if you are redirecting /artifactory to the root of the URL, we ran into issues with doing this on Nginx which is how we discovered the workaround above when using the RPM.