Folllowing the process outlined in "Installing Replicated", you will be prompted with the configuration stage.
You will see several sections of configuration options. This document illustrates how to configure each.
This is the domain that you want the site to be available on for your users. This should be a full URL in the form of waydev.mycompany.com.
If you use BitBucket Server, ignore this step. If you use BitBucket Cloud, complete the fields with the key and secret pair generated from BitBucket.
If you use GitLab Enterprise, ignore this step. If you use GitLab Cloud, complete the fields with the key and secret pair generated from GitLab.
This section controls how Waydev communicates with the required MySQL database. As mentioned in previous documents, Waydev Enterprise requires a MySQL database.
- The fields available to you are as follows:
- Front Database Host: This is the hostname or IP address of the database server.
- Front Database Port: This is the port of that server.
- Front Database Name: The name of the database you created on the server.
- Front Database Username: The user that has ownership rights to the database.
- Front Database Password: The password for that user.
If you choose to use the embedded database method, you will be prompted to enter a directory on the server where MySQL can store data. This allows us to persist your data between system restarts. We recommend keeping all the storage-related fields as default (do not insert any value).
It must be set to file permissions mode 0725 or rwx-w-r-x. It must be owned by root:root.
The directory must be empty when you start the installation. MySQL will place its database files in this directory.
This section is where you define the location of temporary storage for your repository data. In the field "Workers Path", simply enter the path on the server that you prepared.
Once you fill in all the fields above correctly, you can hit save. At this time, the Replicated framework will persist the data and restart all the Waydev Enterprise services so that they can take effect. If this is the first time the server has started, or the first restart after an upgrade, the database will be migrated forward to the latest schema and default data.
This screen shows all the checks that the system performs to validate that it can run. If any dependencies are not met, they will be called out in red.
Once you have validated that the checks are correct, you may choose to re-run the checks (if you've corrected them) or proceed anyway, ignoring any warnings.
You should not skip warnings and errors here. Modify the system to meet proper specifications, especially for production machines.
Once that is complete, you should see the main dashboard screen.
Please note that the initial start of the application may take quite some time the first time it is installed. The dashboard will keep you informed of the status.
Updated 4 months ago