Skip to content

Commit 0ce8913

Browse files
committed
docs: Revise iApp deployment and execution guides for clarity and structure
- Removed outdated deployment examples from the 'Build and Test' guide to streamline content. - Enhanced the 'Deploy and Run' guide with a clearer introduction and restructured sections for better flow. - Updated headings for consistency and improved readability throughout the documentation.
1 parent b9d6d41 commit 0ce8913

File tree

2 files changed

+5
-38
lines changed

2 files changed

+5
-38
lines changed

src/guides/build-iapp/build-&-test.md

Lines changed: 0 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -205,38 +205,6 @@ The CLI will build a Docker image, run your app, and show you the results:
205205
:autoRestart="true"
206206
/>
207207

208-
## Deployment
209-
210-
After your tests pass and the package is built, you can deploy your iApp to a
211-
supported network. During deployment, you'll enter your DockerHub credentials,
212-
specify your app version, and push both standard and TEE-compatible images:
213-
214-
<template v-if="selectedChain === 42161">
215-
<CLIDemo
216-
initialCommand="iapp deploy --chain arbitrum-mainnet"
217-
asciiText="Deploy"
218-
:steps="arbitrumSteps"
219-
:completionStep="15"
220-
:completionMessage="'Deployment of your iApp completed successfully:'"
221-
:completionItems="arbitrumCompletionItems"
222-
:successMessage="'Run iapp run 0x1f80DCebc2EAAff0Db7156413C43B7e88D189923 to execute your iApp on an iExec TEE worker'"
223-
:autoRestart="true"
224-
/>
225-
</template>
226-
227-
<template v-else>
228-
<CLIDemo
229-
initialCommand="iapp deploy"
230-
asciiText="Deploy"
231-
:steps="bellecourSteps"
232-
:completionStep="14"
233-
:completionMessage="'Deployment of your iApp completed successfully:'"
234-
:completionItems="bellecourCompletionItems"
235-
:successMessage="'Run iapp run 0x1f80DCebc2EAAff0Db7156413C43B7e88D189923 to execute your iApp on an iExec TEE worker'"
236-
:autoRestart="true"
237-
/>
238-
</template>
239-
240208
## Next Steps
241209

242210
- When everything is ready

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

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,10 @@ description:
77

88
# Deploy and Run an iApp
99

10+
It's time to run your iApp! After building and testing, you'll need to deploy it to a supported network and then execute it.
11+
12+
## Deploy your iApp
13+
1014
After your tests pass and the package is built, you can deploy your iApp to a
1115
supported network. During deployment, you'll enter your DockerHub credentials,
1216
specify your app version, and push both standard and TEE-compatible images:
@@ -37,19 +41,14 @@ specify your app version, and push both standard and TEE-compatible images:
3741
/>
3842
</template>
3943

40-
# Run an iApp
44+
## Run your iApp
4145

4246
There are multiple ways to execute an iApp on the iExec network. An iApp can be:
4347

4448
- **Self-sufficient** - Basic execution without additional inputs
4549
- **Data-dependent** - Requires protected data, secrets, input files, or
4650
command-line arguments
4751

48-
This guide covers the basic execution methods. For advanced features like
49-
protected data, arguments, and input files, see the dedicated guides.
50-
51-
## Using the iApp Generator Toolkit
52-
5352
The iApp Generator CLI provides a streamlined way to execute iApp, especially
5453
for developers who have built their own iApp.
5554

0 commit comments

Comments
 (0)