Cargo
  1. Cargo
  2. CARGO-743

Alllow for default standalone option

    Details

    • Type: New Feature New Feature
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.2.0
    • Component/s: None
    • Labels:
      None
    • Complexity:
      Intermediate
    • Number of attachments :
      0

      Description

      Allow for a default standalone option.
      This option would allow someone to use the standalone option without being able to configure the server in cargo. This means all the configuration files will be used from the server itself and not modified by Cargo.

      The only thing that Cargo could allow for modification would be to overwrite configuration files. Everything else would be the server defaults.

        Issue Links

          Activity

          Hide
          Savas Ali Tokmen added a comment -

          What is the difference between this and an existing configuration?

          Show
          Savas Ali Tokmen added a comment - What is the difference between this and an existing configuration?
          Hide
          Matt Wringe added a comment -

          The current standalone configuration overwrites a lot of the configuration files when starting the server. There are a bunch of issues which sometimes arises due to this (server updates change the configuration files, the user makes configuration changes in the original server location, etc...) At least this was the case the last time I was working on Cargo stuff.

          The idea here would be that cargo creates a copy of the server and runs that. It wouldn't overwrite any configuration files or make any changes to the configuration files which exist on the original server. If a user wanted to make a change to the server, they would either need to make that change to the configuration files on the original server, or manually overwrite a specific file using cargo.

          Show
          Matt Wringe added a comment - The current standalone configuration overwrites a lot of the configuration files when starting the server. There are a bunch of issues which sometimes arises due to this (server updates change the configuration files, the user makes configuration changes in the original server location, etc...) At least this was the case the last time I was working on Cargo stuff. The idea here would be that cargo creates a copy of the server and runs that. It wouldn't overwrite any configuration files or make any changes to the configuration files which exist on the original server. If a user wanted to make a change to the server, they would either need to make that change to the configuration files on the original server, or manually overwrite a specific file using cargo.
          Hide
          Savas Ali Tokmen added a comment -

          Hi Matt

          OK, so I'm asking again: what is the difference between this and the existing local configuration?

          Also, since a while now, CARGO does not overwrite configuration files anymore -it does XPath-based replacements in configuration files.

          Cheers

          Show
          Savas Ali Tokmen added a comment - Hi Matt OK, so I'm asking again: what is the difference between this and the existing local configuration? Also, since a while now, CARGO does not overwrite configuration files anymore -it does XPath-based replacements in configuration files. Cheers
          Hide
          Matt Wringe added a comment -

          local configuration -> start the server

          situation listed here -> create a copy of the server and start the copy (ie deploy things to the copy, the copy is thrown away after the tests and the original server doesn't have any changes).

          I have not worked on cargo stuff in a very long time. You can probably just close this issues as it seems it was me that opened it, and I don't know if anyone needs this behaviour now or not.

          Show
          Matt Wringe added a comment - local configuration -> start the server situation listed here -> create a copy of the server and start the copy (ie deploy things to the copy, the copy is thrown away after the tests and the original server doesn't have any changes). I have not worked on cargo stuff in a very long time. You can probably just close this issues as it seems it was me that opened it, and I don't know if anyone needs this behaviour now or not.
          Hide
          Savas Ali Tokmen added a comment -

          Fair enough, I'm linking the associated issues and closing the issue, then.

          Cheers

          Show
          Savas Ali Tokmen added a comment - Fair enough, I'm linking the associated issues and closing the issue, then. Cheers

            People

            • Assignee:
              Unassigned
              Reporter:
              Matt Wringe
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: