Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-5108

Non-interactive setup

XMLWordPrintable

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Currently, the only way to setup Confluence is either to:

      1) Run through the web-based setup
      2) Manually generate a valid confluence home directory

      The second is complicated by the fact that you can't plonk a license into confluence.cfg.xml and expect it to work.

      Dan Hardiker in an email:

      > Ideally I would like to be able to replace the setup script with an automated version. Having it pull from a file put in a
      > system property (e.g. -Dconfluence.setup.config=/path/to/confluence-setup.properties) with the ability to set a URL
      > to navigate to once setup has completed would enable us to leave confluence to set itself up automatically, and then
      > have it directed to our xwork plugin to deal with setting up anything custom.

      Maybe instead of a system property (which can cause problems if you forget to remove it next time you start up, have Confluence check if the confluence-home directory is (a) without a confluence-cfg.xml, and (b) contains a setup.properties file. If so, do the setup from setup.properties and then delete the properties file.

            [CONFSERVER-5108] Non-interactive setup

            Sen made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 3575778 ] New: JAC Suggestion Workflow 3 [ 4326657 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow 2 [ 3168080 ] New: JAC Suggestion Workflow 4 [ 3575778 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3029678 ] New: JAC Suggestion Workflow 2 [ 3168080 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2529558 ] New: JAC Suggestion Workflow [ 3029678 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 2256341 ] New: Confluence Workflow - Public Facing v4 [ 2529558 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 - TEMP [ 2185703 ] New: Confluence Workflow - Public Facing v3 [ 2256341 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 1934130 ] New: Confluence Workflow - Public Facing v3 - TEMP [ 2185703 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v2 [ 1754525 ] New: Confluence Workflow - Public Facing v3 [ 1934130 ]
            jonah (Inactive) made changes -
            Description Original: Currently, the only way to setup Confluence is either to:

            1) Run through the web-based setup
            2) Manually generate a valid confluence home directory

            The second is complicated by the fact that you can't plonk a license into confluence.cfg.xml and expect it to work.

            Dan Hardiker in an email:

            > Ideally I would like to be able to replace the setup script with an automated version. Having it pull from a file put in a
            > system property (e.g. -Dconfluence.setup.config=/path/to/confluence-setup.properties) with the ability to set a URL
            > to navigate to once setup has completed would enable us to leave confluence to set itself up automatically, and then
            > have it directed to our xwork plugin to deal with setting up anything custom.

            Maybe instead of a system property (which can cause problems if you forget to remove it next time you start up, have Confluence check if the confluence-home directory is (a) without a confluence-cfg.xml, and (b) contains a setup.properties file. If so, do the setup from setup.properties and then delete the properties file.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-5108].
              {panel}

            Currently, the only way to setup Confluence is either to:

            1) Run through the web-based setup
            2) Manually generate a valid confluence home directory

            The second is complicated by the fact that you can't plonk a license into confluence.cfg.xml and expect it to work.

            Dan Hardiker in an email:

            > Ideally I would like to be able to replace the setup script with an automated version. Having it pull from a file put in a
            > system property (e.g. -Dconfluence.setup.config=/path/to/confluence-setup.properties) with the ability to set a URL
            > to navigate to once setup has completed would enable us to leave confluence to set itself up automatically, and then
            > have it directed to our xwork plugin to deal with setting up anything custom.

            Maybe instead of a system property (which can cause problems if you forget to remove it next time you start up, have Confluence check if the confluence-home directory is (a) without a confluence-cfg.xml, and (b) contains a setup.properties file. If so, do the setup from setup.properties and then delete the properties file.
            jonah (Inactive) made changes -
            Link New: This issue relates to CONFCLOUD-5108 [ CONFCLOUD-5108 ]

              Unassigned Unassigned
              cmiller@atlassian.com Charles Miller (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: