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 <[email protected]> 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.
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
