You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Enabling static URLs on one branch does not automatically apply to other branches. You must enable static URLs separately for each branch, that also includes the main branch.
55
55
- Different branches of an application can have different unique app slug URLs. However, it's a best practice to configure the same app slug across all branches to maintain consistency.
56
56
57
-
## Import and export scenarios
57
+
## Cross-Instance deployment and Version control
58
58
59
-
- Exportingor importing an application (via JSON or Git) preserves the static URL settings. If the application slugs are available on the target instance, the same routes continue to work.
59
+
- Exporting, importing, or syncing an application (via JSON or Git sync) preserves the static URL settings. If the application slugs are available on the target instance, the same routes continue to work.
60
60
- Importing into the same Appsmith instance automatically appends a short suffix when needed to keep the application slug unique.
61
61
- After import, you can rename slugs manually if you prefer a different URL.
62
62
63
-
## Disable or re-enable static URLs
63
+
:::info
64
+
Since static URLs remain constant, you can synchronize your apps across different instances without worrying about broken links. The same static URL structure works consistently across environments.
65
+
:::
66
+
67
+
## Navigate between apps
68
+
69
+
With static URLs enabled, you can navigate between different apps using the [navigateTo](/reference/appsmith-framework/widget-actions/navigate-to) action. Static URLs provide predictable routes that remain consistent across instances, making cross-app navigation reliable.
70
+
71
+
To navigate to another app:
72
+
73
+
1. Use a widget (such as a Button or Icon button) and set its **onClick** property to navigate to another app.
74
+
2. Select the **Navigate to** action and choose **URL** as the destination type.
75
+
3. Enter the static URL in the following format:
76
+
77
+
```jsx
78
+
{{appsmith.URL.host}}/app/<app-slug>/<page-slug>
79
+
```
80
+
81
+
Replace `<app-slug>` and `<page-slug>` with the actual slugs of the target application and page.
82
+
83
+
Example:
84
+
```jsx
85
+
{{appsmith.URL.host}}/app/sales-dashboard/reports
86
+
```
87
+
88
+
## Embed apps with static URLs
89
+
90
+
You can embed apps that use static URLs in the same way. Static URLs make embedding more reliable by providing consistent routes that don't change when apps are exported and imported or version controlled.
91
+
92
+
To embed an app with static URLs:
93
+
94
+
1. Use the static URL format with the `embed=true` parameter:
2. For different environments (development, staging, production), you can configure the instance URL dynamically while keeping the app and page slugs constant. This means you only need to update the instance URL when deploying to different environments, and the app path remains the same across all environments.
106
+
107
+
## Disable static URLs
64
108
65
109
1. Go to **Settings → General → Static URL** and turn the toggle off.
66
110
2. Confirm the change to remove the static routes. The app remains accessible through the original UUID-based URLs.
0 commit comments