Skip to content

Commit

Permalink
include reference to cleanup procedure
Browse files Browse the repository at this point in the history
  • Loading branch information
joswig committed Jan 7, 2025
1 parent 026fed1 commit 97669d6
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 1 deletion.
2 changes: 1 addition & 1 deletion docs/deployment/advanced-ui-custom-base-path.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Advanced - UI Custom Base Path

This document lists the instructions for building an aerie-ui Docker image with a [custom base path](https://kit.svelte.dev/docs/configuration#paths). While the default path and resulting application URL are usually a good fit, some installations may choose a custom path to provide consistency with other non-Aerie applications that the mission is using. Alternately, this could be part of a configuration that supports running multiple instances of Aerie UI on the same machine.
This document lists the instructions for building an aerie-ui Docker image with a [custom base path](https://kit.svelte.dev/docs/configuration#paths). While the default path and resulting application URL are usually a good fit, some installations may choose a custom path to support deployment behind a gateway, to provide consistency with other non-Aerie applications that the mission is using, or this could be part of a configuration that supports running multiple instances of Aerie UI on the same machine.

### Building

Expand Down
4 changes: 4 additions & 0 deletions docs/introduction.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,3 +43,7 @@ Understand Aerie in **5 minutes** by trying it out!
Note that the fast track deployment is not configured to connect to an authentication and authorization provider, therefore any credentials are accepted.

1. Head over to the planning documentation to learn how to [upload a mission model](../planning/upload-mission-model).

## Cleanup

Aerie is an actively developed application suite with interdepenencies between the server, the web ui, and the database schema. New capabilities may require ensuring that all parts of the application are on the same version. Breaking changes are stated in the release notes. If the above fast track instructions worked previously, but are now seeing an inconsistent schema consult the [developer docs](https://github.com/NASA-AMMOS/aerie/blob/develop/docs/DEVELOPER.md) for instructions on clearing container images. For long running hosts see [Production Deployment](https://nasa-ammos.github.io/aerie-docs/deployment/production-deployment/) for an overview of the data migration process.

0 comments on commit 97669d6

Please sign in to comment.