Skip to content

Conversation

@TJM
Copy link

@TJM TJM commented Nov 12, 2018

Here are some updates, per https://www.jfrog.com/confluence/display/RTF/Upgrading+Artifactory

  • Added startStopThreads="2" (since 5.4.0)
  • Added sendReasonPhrase="true" to all connectors (since 5.6.1)
  • Added connector for port 8040, access listener (since 5.7.0)
  • Added relaxedPathChars='[]' relaxedQueryChars='[]' (since 6.3.0)

I am not sure why AJP is commented out, but I left it that way, and just added the new options, in case someone needs to enable it.

Also, I am not sure why the shutdown port is disabled, since the "stop" process tries to use it.

Interestingly, the "PRO" version questions whether this is needed. Is it still needed?

~tommy

Copy link
Contributor

@jainishshah17 jainishshah17 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jainishshah17
Copy link
Contributor

@TJM I think we should make the custom server.xml optional

@TJM
Copy link
Author

TJM commented Nov 28, 2018

Sorry, I think this branch got mixed up with my "all fixes to make it work" ... it was supposed to be just the server.xml fixes. :)

@jainishshah17 I wondered if the custom server.xml was actually needed. I think it mostly has to do with changing the application port to match what was assigned through docker? right?

ADD files/access/etc/keys/root.crt /var/opt/jfrog/artifactory/access/etc/keys/root.crt
ADD files/security/communication.key /var/opt/jfrog/artifactory/communication.key
RUN mkdir -p /var/opt/jfrog/artifactory/access/etc/keys/ /var/opt/jfrog/artifactory/etc/security/
COPY --chown=artifactory:artifactory files/access/etc/keys/private.key /var/opt/jfrog/artifactory/access/etc/keys/private.key
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This section concerns me. I don't really feel like pre-populating the same keys in everyone's HA artifactory is a good idea.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@TJM We don't need this anymore

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will remove them.

@jainishshah17
Copy link
Contributor

@TJM Yes, server.xml was only used to change default port to dynamically assigned port

@TJM
Copy link
Author

TJM commented Nov 29, 2018

@jainishshah17 The server.xml also has some other stuff:

        <Engine name="Catalina" defaultHost="localhost">
            <Host name="localhost" appBase="webapps" startStopThreads="2"/>
        </Engine>

vs

        <Engine name="Catalina" defaultHost="localhost">
            <Host name="localhost" appBase="webapps" startStopThreads="2"/>
            <Valve className="org.apache.catalina.valves.RemoteIpValve"
                   remoteIpHeader="x-forwarded-for"
                   protocolHeader="x-forwarded-proto"
                   portHeader="x-forwarded-port" />
        </Engine>

Are these still needed (desired)?

@TJM TJM force-pushed the additional_6.5.2 branch from 47be750 to ff58105 Compare November 29, 2018 15:10
@TJM TJM changed the title Update server.xml for 6.5.2 (since like 5.4.0 actually) Update server.xml for 6.5.x (since like 5.4.0 actually) Nov 29, 2018
@TJM
Copy link
Author

TJM commented Nov 29, 2018

Re key... https://www.jfrog.com/confluence/display/RTF/HA+Installation+and+Setup#HAInstallationandSetup-CreatetheMasterKey

Maybe it would be better to "generate" the key in the entrypoint script and put it in shared storage?

@TJM
Copy link
Author

TJM commented Jan 15, 2019

What is the status of this? Do I need to do anything else (besides bumping the versions?)

Copy link
Contributor

@elioengcomp elioengcomp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants