You may need to check the deployment information when performing O&M operations on projects in FineOps or when viewing the mounting directory and component information.
You can visit the server where FineOps is located and click Export Deployment Information to export JSON files.
1. Log in to FineOps as the admin and choose Platform Management > O&M Component.
2. Click Export Deployment Information. After the successful export, the file path and the file name are displayed.
3. Find the corresponding file according to the prompt, where you can view the deployment information.
In JSON files, deployment information is segmentally stored according to components.
This document details some commonly used content to help you quickly find the required information.
1. Open the JSON file and search for /usr/local/tomcat/webapps/ops/WEB-INF/embed.
2. The content before the colon (:) in that line is Mounting path/embed.
For example, in the following figure, the project's mounting path is /home/katherine/data/fanruan_024288c2/ops.
1. Open the JSON file and locate the OPS component section.
2. This section contains the basic project configuration information, such as the image version and the maximum number of open files.
1. Open the JSON file and search for /run/secrets.
2. The content before the equal sign (=) in that line indicates the storage location of the password file bootstrapPassword.txt.
3. Check the bootstrapPassword.txt file at that location on the server. The password in it belongs to the Elasticsearch default user elastic.
The component passwords recorded in the exported JSON file are the ones set during project deployment.
If any component password has been modified through other means after deployment, ensure you store it securely. FineOps does not provide a query function for passwords changed post-deployment.
1. Username: ops_sign_key
2. Password:
Open the JSON file and search for OPS_SIGN_KEY.
The content after the equal sign (=) in that line is the password.
For example, in the following figure, the password is 40b5a64c770b63e1.
For the Registry component deployed/upgraded via FineOps of V2.27.0 or later versions:
1. Open the JSON file and search for :/etc/component/setting/registry.setting.
2. The path preceding this string is the location of the file storing the administrator's password of the Registry component.
For example, in the following figure, the password of the Registry component is stored in /home/ops/fanruan_188c48a4/registry/setting/registry.setting.
3. Check the registry.setting file at that location on the FineOps server. The password in it belongs to the administrator of the Registry component.
The default username is ops_sign_key.
The component passwords recorded in the file are the ones set during project deployment.
For the Registry component deployed/upgraded via FineOps of versions between V2.7.0 to V2.26.0 (both exclusive):
For the Registry component deployed/upgraded via FineOps of V2.6.0 or earlier versions:
No default user or password exists.
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy