Migrate legacy shared applications
Use this guide if a shared application was installed before Olares 1.12.6 and you want to move to its current shared-app architecture. Legacy v2 apps continue to run after the Olares update, but they cannot be upgraded in place.
For an explanation of the current architecture, see About shared applications.
Check app data before uninstalling
Uninstalling a legacy shared app can remove data that the new app cannot restore directly. Identify the app and complete the applicable export or backup steps before uninstalling it.
Identify a legacy v2 app
Open the app details page in Market and check Compatibility in the Information panel:
- A legacy v2 shared app typically shows
Olares >=1.12.3-0, <1.12.6. - A current shared app shows
Olares >=1.12.6-0.
If the app does not match these ranges, do not use this guide. Record the app and chart versions before choosing a migration path.
Choose a migration path
| App or data state | Migration path |
|---|---|
| ComfyUI | Use the app's automatic migration workflow |
| Falco, MTranServer, or another app with no user-created data | Confirm that no data must be preserved, then reinstall |
| Dify, OnlyOffice, SearXNG, or Xinference | Export or back up app-specific data, then restore it into the new app |
| Standalone Ollama shared app | Re-create the required model on an Engine Base app, then reconnect clients |
Migrate ComfyUI
Follow ComfyUI migration notes to run the supported migration and confirm the new data locations before removing the old app.
Reinstall an app with no data to preserve
Use this path only after confirming that the app contains no user-created data, settings, or workflows that you need.
- Record the legacy app name and version.
- Uninstall the legacy v2 app.
- Find the current shared app in Market and confirm that its compatibility range starts with
Olares >=1.12.6-0. - Install the current shared app and open it from the Launchpad.
Migrate app data manually
The data that can be preserved differs by app. Complete the app-specific guide before uninstalling the legacy app:
Do not restore an old app data directory into a new version unless its migration guide explicitly requires it.
Move from Ollama to Engine Base
- Note the models and client applications that use the standalone Ollama shared app.
- Deploy each required model with an Engine Base app.
- Open the model console and copy the new Base URL.
- Replace the Ollama endpoint in each client application with the new Base URL.
- Send a test request from each client. Remove the old Ollama app only after the clients use the new model successfully.