Skip to content

Commit d523212

Browse files
committed
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.
1 parent 9e25439 commit d523212

File tree

1 file changed

+35
-3
lines changed

1 file changed

+35
-3
lines changed

src/guides/build-iapp/deploy-&-run.md

Lines changed: 35 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,22 @@ specify your app version, and push both standard and TEE-compatible images:
4040
/>
4141
</template>
4242

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.
44+
45+
Here is an example:
46+
47+
```json
48+
[
49+
{
50+
"sconifiedImage": "robiniexec/iapp:0.0.1-tee-scone-5.9.1-v16-debug-5aea8b4aa71d",
51+
"appContractAddress": "0x9665136c599ec361C8eE627eC4F35A23fBa94897",
52+
"owner": "0xbabE8270aC9857Af3aaC06877888F1939FbeC578",
53+
"date": "2025-08-12T13:16:18.252Z"
54+
},
55+
...
56+
]
57+
```
58+
4359
## Run your iApp
4460

4561
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.
8096
/>
8197
</template>
8298

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.
100+
101+
Here is an example:
102+
103+
```json
104+
[
105+
{
106+
"iAppAddress": "0x9665136c599ec361C8eE627eC4F35A23fBa94897",
107+
"dealid": "0x26d758de1be51697c33fa606cd0c5243082a6e675a4463b106d71fde2893280f",
108+
"taskid": "0x1a58dd6018b30b022eb35be53ad9374eb630925458d14643a1dfd9c686b964d8",
109+
"txHash": "0x6f14eac6933c609fb6d3e6b2bbd18c373c6dc99c7d7fd22036d5a20f847c5e42",
110+
"date": "2025-08-18T18:30:03.711Z"
111+
},
112+
...
113+
]
114+
```
115+
83116
## Next Steps
84117

85-
- Discover how to
86-
[run an iApp with inputs](/guides/use-iapp/run-iapp-with-inputs)
87-
- Understand [how to pay for executions](/guides/use-iapp/how-to-pay-executions)
118+
- Learn how to [manage access to your iApp](/guides/build-iapp/manage-access)
119+
- Discover [debugging techniques](/guides/build-iapp/debugging) for troubleshooting
88120

89121
<script setup>
90122
import CLIDemo from '@/components/CLIDemo.vue';

0 commit comments

Comments
 (0)