Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-3250

Blesta Installer: Allow the MySQL port to be overriden

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.6.0
    • Fix Version/s: 4.8.0-b1
    • Component/s: Staff Interface
    • Labels:
      None

      Description

      During Blesta installation in both the UI and CLI environment, a MySQL port should be set. In both environments, this should default to 3306. In the UI, 3306 can be set in the input field by default. In CLI mode, it can default to 3306. A port should be required and validated as a port number similar to other fields during installation. This will allow users to specify non-standard MySQL ports during installation that they cannot currently set.

      1. Create a new input field/option for a MySQL server Port
        • The Port field should appear beneath/after the Host field as a separate field atogether. It should not be given as a socket to the host field (e.g. not "domain.com:3306")
      2. The configuration file should then have a 'port' field set for the database profile
      3. When performing a backup in Blesta, a mysqldump command is run. This needs to be given the port for backups to work
      4. Test Blesta works on a non-standard port set from installation and that a database dump can be downloaded

      When installing Blesta, the default port of 3306 is used for the MySQL server specified. We should allow this port to be overridden. For one, some MySQL hosting instances work on non-standard ports

      Suggestion is to allow the port be specified in the hostname field as such:

      localhost
      localhost:3306
      localhost:8712
      mysql.domain.com
      mysql.domain.com:3306
      mysql.domain.com:8712

      If no port is specified, then we use the default port 3306. If a port is specified, then we use that port. During installation, when the config file is written we must then also specify the port in the /config/blesta.php config file. Currently there is an option for port that is commented out.

        Activity

        admin Paul Phillips created issue -
        tyson Tyson Phillips (Inactive) made changes -
        Field Original Value New Value
        Story Points 2
        tyson Tyson Phillips (Inactive) made changes -
        Sprint 4.8.0 Sprint 3 [ 94 ]
        tyson Tyson Phillips (Inactive) made changes -
        Rank Ranked higher
        tyson Tyson Phillips (Inactive) made changes -
        Sprint 4.8.0 Sprint 3 [ 94 ] 4.8.0 Sprint 3, 4.8.0 Sprint 4 [ 94, 95 ]
        tyson Tyson Phillips (Inactive) made changes -
        Rank Ranked higher
        tyson Tyson Phillips (Inactive) made changes -
        Description When installing Blesta, the default port of 3306 is used for the MySQL server specified. We should allow this port to be overridden. For one, some MySQL hosting instances work on non-standard ports

        Suggestion is to allow the port be specified in the hostname field as such:

        localhost
        localhost:3306
        localhost:8712
        mysql.domain.com
        mysql.domain.com:3306
        mysql.domain.com:8712

        If no port is specified, then we use the default port 3306. If a port is specified, then we use that port. During installation, when the config file is written we must then also specify the port in the /config/blesta.php config file. Currently there is an option for port that is commented out.
        During Blesta installation in both the UI and CLI environment, a MySQL port should be set. In both environments, this should default to 3306. In the UI, 3306 can be set in the input field by default. In CLI mode, it can default to 3306. A port should be required and validated as a port number similar to other fields during installation. This will allow users to specify non-standard MySQL ports during installation that they cannot currently set.

        # Create a new input field/option for a MySQL server Port
        #* The Port field should appear beneath/after the Host field as a separate field atogether. It should not be given as a socket to the host field (e.g. not "domain.com:3306")
        # The configuration file should then have a 'port' field set for the database profile
        # When performing a backup in Blesta, a _mysqldump_ command is run. This needs to be given the port for backups to work
        # Test Blesta works on a non-standard port set from installation and that a database dump can be downloaded


        ----

        When installing Blesta, the default port of 3306 is used for the MySQL server specified. We should allow this port to be overridden. For one, some MySQL hosting instances work on non-standard ports

        Suggestion is to allow the port be specified in the hostname field as such:

        localhost
        localhost:3306
        localhost:8712
        mysql.domain.com
        mysql.domain.com:3306
        mysql.domain.com:8712

        If no port is specified, then we use the default port 3306. If a port is specified, then we use that port. During installation, when the config file is written we must then also specify the port in the /config/blesta.php config file. Currently there is an option for port that is commented out.
        tyson Tyson Phillips (Inactive) made changes -
        Fix Version/s 4.8.0-b1 [ 11127 ]
        Fix Version/s Short Term [ 10800 ]
        tyson Tyson Phillips (Inactive) made changes -
        Assignee Abdy Franco [ abdy ]
        abdy Abdy Franco made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Automated transition triggered when Abdy Franco created pull request #754 in Stash -
        Status In Progress [ 3 ] In Review [ 5 ]
        Resolution Fixed [ 1 ]
        abdy Abdy Franco made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 2 hours, 52 minutes [ 10320 ]
        Worklog Id 12729 [ 12729 ]
        Automated transition triggered when Tyson Phillips (Inactive) merged pull request #754 in Stash -
        Status In Review [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            abdy Abdy Franco
            Reporter:
            admin Paul Phillips
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              23/Dec/19

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 2 hours, 52 minutes
              2h 52m

                Agile