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
docs: Enhance 'Deploy and Run' guide with deployment and run tracking details
- Added sections explaining the creation of `deployments.json` and `runs.json` files for tracking deployments and runs on the iExec network.
- Included JSON examples to illustrate the structure of the tracking files.
- Updated next steps to guide users on managing access and debugging techniques.
Copy file name to clipboardExpand all lines: src/guides/build-iapp/deploy-&-run.md
+35-3Lines changed: 35 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,6 +40,22 @@ specify your app version, and push both standard and TEE-compatible images:
40
40
/>
41
41
</template>
42
42
43
+
Now that your iApp has been deployed on the iExec protocol, you can navigate to the `cache` folder to see your deployments saved. A file named `deployments.json` in the folder corresponding to your target network will be created containing each deployment made on this network. These files will help you easily track each deployment per network.
There are multiple ways to execute an iApp on the iExec network. An iApp can be:
@@ -80,11 +96,27 @@ for developers who have built their own iApp.
80
96
/>
81
97
</template>
82
98
99
+
Now that you have run your iApp on the iExec protocol, you can navigate to the `cache` folder to see your runs saved. A file named `runs.json` in the folder corresponding to your target network will be created containing each run made on this network. These files will help you easily track each run per network. Use the [iExec Explorer](/guides/tooling-and-explorers/iexec-explorer) to retrieve more data about your tasks.
0 commit comments