To externalize the ElasticSearch database, respond to the prompts as described below:
Prompt | Response |
---|---|
Install Elasticsearch? [Y/n]:n | "n" |
Please enter the Elasticsearch URL [http://docker.for.mac.localhost:9200]: | Provide the URL to your ElasticSearch database or accept the default if that is correct. Please ensure you provide http or https protocol in the url. |
After the installation completes, update the following properties in the file: mission-control.properties with appropriate values
To externalize the MongoDB database, respond to the prompts as described below:
Prompt | Response | ||
---|---|---|---|
Install MongoDB? [Y/n]:n | "n" | ||
Please enter the MongoDB Host [docker.for.mac.localhost]: | Enter the host that MongoDB is available on. (Usually, `localhost`). NOTE: Do NOT include a protocol. | ||
Please enter the MongoDB Port [27017]: | Enter the port that Mission Control can use to access MongoDB. (Usually, 27017) | ||
Attempt to seed MongoDB? [y/N]: | To have the installer seed your MongoDB automatically, respond with "y"
If you respond with "N", the installer copies the files you will need to manually seed the database and ends the installation process. If you respond with "y" the installer continue and prompt you with the following questions. | ||
Is this a fresh installation with no users? (If you choose 'y', the installer will create an admin user): |
| ||
| Provide an admin user ID and password The installer will attempt to perform the following actions to seed the MongoDB automatically:
|
If you choose to seed your database manually, make sure you do so BEFORE starting up JFrog Mission Control. |
MongoDB is used to store metadata about Mission Control's microservices, so the script attempts to create the necessary databases and users. If you are familiar with MongoDB or do not have access to the Mongo instance, you can review the createMongoUsers.js
file and create these yourself using the appropriate database client. If not and if you have access to the instance where MongoDB is installed, follow the instructions below:
createMongoUsers.sh
and createMongoUsers.js
to the system where MongoDB is running. chmod +x createMongoUsers.sh
)./createMongoUsers.sh
and follow the prompts on screen. To externalize the PostgreSQL database, respond to the prompts as described below:
Prompt | Response |
---|---|
Install Postgres? [Y/n]:n | "n" |
Please enter the Postgres Host [docker.for.mac.localhost]: | Enter the host that Postgres is available on. NOTE: Do NOT include a protocol. |
Please enter the Postgres Port [5432]: | Enter the port that Mission Control can use to access Postgres. (Usually, 5432) |
If you choose to seed your database manually, make sure you do so BEFORE starting up JFrog Mission Control. |
Additional information about seeding your database manually a pre-configured script can be found here. |
PostgreSQL is used to store metadata about Mission Control's microservices, so the script attempts to create the necessary database, users and schema. If you are familiar with PostgreSQL or do not have access to the postgres instance, you can review the createPostgresUsers.sh file and create these yourself using the appropriate database client. If not and if you have access to the instance where PostgreSQL is installed, follow the instructions below:
chmod +x createPostgresUsers.sh
)./createPostgresUsers.sh
. You can externalize the databases Mission Control uses on an existing installation at any time by simply running the installer again.
When prompted with Perform a standard upgrade? [Y/n]
,
select
"N".
Now just continue with the process in the same way you would during a new installation
Mission Control offers you the flexibility to decide when to externalize its databases, and even to switch externalized databases in case you have more than one instance of any particular database installed in your system.