Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

116 - Update Edge CLI Readme sections #117

Merged
merged 1 commit into from
Nov 27, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
51 changes: 50 additions & 1 deletion Minimal/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -346,6 +346,12 @@ enter its virtual environment:
$ edge app shell
```

To rebuild the application's EDM environment:

```
$ edge env build
```

See the full list of application commands with:

```
Expand All @@ -356,4 +362,47 @@ Run any given command in verbose mode for debugging:

```
$ edge app --verbose <command>
```
```

## Handling Application Compatibility in Edge CLI

When working with the new Edge CLI alongside an older installed application, you
might encounter compatibility issues during the build process. These issues
arise because the configuration file format has changed, and the new CLI is
designed for the updated format. Follow the steps below to resolve the issue:

### Instructions

1. Trigger the Build

Run the following command to build your app:

```
$ edge app build
```

If your app's configuration is incompatible with the new CLI, the command will
fail with a message indicating the need to upgrade.

2. Upgrade the App Configuration

Upgrade the application's configuration to the new format using:

```
$ edge app upgrade
```

This command updates the application's configuration file to match the
requirements of the new Edge CLI. If the configuration is already compatible,
the command will exit cleanly, confirming that no further changes are necessary.

3. Rebuild the App

Attempt the build again:

```
$ edge app build
```

This time, the build should succeed, as the configuration has been updated to
ensure compatibility with the new CLI.
51 changes: 50 additions & 1 deletion Panel/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -325,6 +325,12 @@ enter its virtual environment:
$ edge app shell
```

To rebuild the application's EDM environment:

```
$ edge env build
```

See the full list of application commands with:

```
Expand All @@ -335,4 +341,47 @@ Run any given command in verbose mode for debugging:

```
$ edge app --verbose <command>
```
```

## Handling Application Compatibility in Edge CLI

When working with the new Edge CLI alongside an older installed application, you
might encounter compatibility issues during the build process. These issues
arise because the configuration file format has changed, and the new CLI is
designed for the updated format. Follow the steps below to resolve the issue:

### Instructions

1. Trigger the Build

Run the following command to build your app:

```
$ edge app build
```

If your app's configuration is incompatible with the new CLI, the command will
fail with a message indicating the need to upgrade.

2. Upgrade the App Configuration

Upgrade the application's configuration to the new format using:

```
$ edge app upgrade
```

This command updates the application's configuration file to match the
requirements of the new Edge CLI. If the configuration is already compatible,
the command will exit cleanly, confirming that no further changes are necessary.

3. Rebuild the App

Attempt the build again:

```
$ edge app build
```

This time, the build should succeed, as the configuration has been updated to
ensure compatibility with the new CLI.
51 changes: 50 additions & 1 deletion Plotly Dash/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -325,6 +325,12 @@ enter its virtual environment:
$ edge app shell
```

To rebuild the application's EDM environment:

```
$ edge env build
```

See the full list of application commands with:

```
Expand All @@ -335,4 +341,47 @@ Run any given command in verbose mode for debugging:

```
$ edge app --verbose <command>
```
```

## Handling Application Compatibility in Edge CLI

When working with the new Edge CLI alongside an older installed application, you
might encounter compatibility issues during the build process. These issues
arise because the configuration file format has changed, and the new CLI is
designed for the updated format. Follow the steps below to resolve the issue:

### Instructions

1. Trigger the Build

Run the following command to build your app:

```
$ edge app build
```

If your app's configuration is incompatible with the new CLI, the command will
fail with a message indicating the need to upgrade.

2. Upgrade the App Configuration

Upgrade the application's configuration to the new format using:

```
$ edge app upgrade
```

This command updates the application's configuration file to match the
requirements of the new Edge CLI. If the configuration is already compatible,
the command will exit cleanly, confirming that no further changes are necessary.

3. Rebuild the App

Attempt the build again:

```
$ edge app build
```

This time, the build should succeed, as the configuration has been updated to
ensure compatibility with the new CLI.
51 changes: 50 additions & 1 deletion React/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -369,6 +369,12 @@ enter its virtual environment:
$ edge app shell
```

To rebuild the application's EDM environment:

```
$ edge env build
```

See the full list of application commands with:

```
Expand All @@ -379,4 +385,47 @@ Run any given command in verbose mode for debugging:

```
$ edge app --verbose <command>
```
```

## Handling Application Compatibility in Edge CLI

When working with the new Edge CLI alongside an older installed application, you
might encounter compatibility issues during the build process. These issues
arise because the configuration file format has changed, and the new CLI is
designed for the updated format. Follow the steps below to resolve the issue:

### Instructions

1. Trigger the Build

Run the following command to build your app:

```
$ edge app build
```

If your app's configuration is incompatible with the new CLI, the command will
fail with a message indicating the need to upgrade.

2. Upgrade the App Configuration

Upgrade the application's configuration to the new format using:

```
$ edge app upgrade
```

This command updates the application's configuration file to match the
requirements of the new Edge CLI. If the configuration is already compatible,
the command will exit cleanly, confirming that no further changes are necessary.

3. Rebuild the App

Attempt the build again:

```
$ edge app build
```

This time, the build should succeed, as the configuration has been updated to
ensure compatibility with the new CLI.
49 changes: 49 additions & 0 deletions Streamlit/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -325,6 +325,12 @@ enter its virtual environment:
$ edge app shell
```

To rebuild the application's EDM environment:

```
$ edge env build
```

See the full list of application commands with:

```
Expand All @@ -336,3 +342,46 @@ Run any given command in verbose mode for debugging:
```
$ edge app --verbose <command>
```

## Handling Application Compatibility in Edge CLI

When working with the new Edge CLI alongside an older installed application, you
might encounter compatibility issues during the build process. These issues
arise because the configuration file format has changed, and the new CLI is
designed for the updated format. Follow the steps below to resolve the issue:

### Instructions

1. Trigger the Build

Run the following command to build your app:

```
$ edge app build
```

If your app's configuration is incompatible with the new CLI, the command will
fail with a message indicating the need to upgrade.

2. Upgrade the App Configuration

Upgrade the application's configuration to the new format using:

```
$ edge app upgrade
```

This command updates the application's configuration file to match the
requirements of the new Edge CLI. If the configuration is already compatible,
the command will exit cleanly, confirming that no further changes are necessary.

3. Rebuild the App

Attempt the build again:

```
$ edge app build
```

This time, the build should succeed, as the configuration has been updated to
ensure compatibility with the new CLI.