You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2. Perform the source code analysis and upload the results **at a later time**. The following section will explain how to run database analysis in **offline mode**
@@ -78,28 +78,43 @@ These are the steps you need to follow in order to bypass internet access limita
78
78
79
79
`tidal restore tidal-snapshot_DATE.tar`
80
80
81
-
This will load a docker image and all the existing Tidal Tools configurations from the original machine. You can now run the source code analysis without any external network connectivity.
81
+
This will load a docker image and all the existing Tidal Tools configurations from the original machine.
- The `--offline` flag indicates to Tidal Tools that the output needs to be stored in a file instead of being uploaded.
88
99
- The `--output-dir` flag determines where the output will be located.
89
100
90
-
After the analysis is completed, you will find a zip file called, `result-<DATE>.zip` that can then be transferred into a machine with internet connectivity.
101
+
After the analysis is completed, you will find an artifact file called`code-analysis-<DATE>-<TYPE>.json` that can then be transferred into a machine with internet connectivity.
91
102
92
-
4. Back to the machine with internet access, you can now upload your results to your workspace with this command.
103
+
5. Back to the machine with internet access, you can now upload your results to your workspace with this command.
You should receive confirmation that the upload has been completed and can navigate to Tidal to see the results.
97
111
98
112
{% include tip.html content="Need to run code analysis on a entire set of applications all from one machine? Run [this command and easily create a directory for every application already in Tidal Migrations](https://github.com/tidalmigrations/gists/blob/master/make_source_code_dirs.sh)" %}
99
113
100
114
### Why Docker?
101
115
102
-
You need to install Docker in order to complete the source code analysis. This is because the analysis uses several system dependent software libraries so by using Docker the analysis can use those libraries without you requiring to install the correct versions and dependencies.
116
+
You need to install Docker in order to complete the source code analysis. This is because the analysis uses several system dependent software libraries.
117
+
By using Docker, the analysis can use those libraries without requiring you to install any other dependencies.
0 commit comments