@magentrix-corp/magentrix-cli 1.3.9 → 1.3.10

package/README.md

@@ -573,7 +573,7 @@ Your Vue project needs two configuration files:
 ```typescript
 // src/config.ts
 export const config = {
-  appPath: "my-app",           // Required: App identifier (folder name on server)
+  appSlug: "my-app",           // Required: App identifier (folder name on server)
   appName: "My Application",   // Required: Display name in navigation menu
   appDescription: "",          // Optional: App description
   appIconId: "",               // Optional: App icon ID
@@ -589,11 +589,43 @@ VITE_ASSETS = '[]'  # Injected automatically by vue-run-dev
 ```
 
 **Accepted field names in config.ts:**
-- Slug: `appPath`, `slug`, or `app_path`
+- Slug: `appSlug`, `slug`, or `app_slug`
 - Name: `appName`, `app_name`, or `name`
 - Description: `appDescription` or `app_description`
 - Icon: `appIconId` or `app_icon_id`
 
+#### Changing an App Slug
+
+> **⚠️ Important:** Changing the `appSlug`/`slug` in `config.ts` creates a **new** Iris app on Magentrix. The old app is **not** automatically deleted.
+
+If you simply change the slug and run `vue-run-build`, you'll end up with two apps on the server - the old one becomes orphaned.
+
+**Recommended workflow for changing an app slug:**
+
+```bash
+# 1. Delete the old app first (from Magentrix workspace)
+cd ~/magentrix-workspace
+magentrix iris-app-delete         # Select the old app, confirm deletion
+                                  # This removes it from server, local files, and cache
+                                  # Optionally unlink the Vue project when prompted
+
+# 2. Change the slug in your Vue project
+cd ~/my-vue-app
+# Edit config.ts: change appSlug from "old-slug" to "new-slug"
+
+# 3. Re-link the project with the new slug
+magentrix iris-app-link           # Updates the linked project with new slug
+
+# 4. Build, stage, and publish
+magentrix vue-run-build           # Stages to new folder: src/iris-apps/new-slug/
+# When prompted, choose to publish
+```
+
+**What happens if you don't follow this workflow:**
+- Both `old-slug` and `new-slug` apps will exist on the server
+- The old app remains in `src/iris-apps/old-slug/` locally
+- You'll need to manually delete the old app using `magentrix iris-app-delete`
+
 ### Command Availability
 
 **In Vue project directories** (detected by presence of `config.ts`):
@@ -693,8 +725,8 @@ When running `vue-run-build` from a Vue project, the CLI checks if the target wo
 2. Pull latest changes: `magentrix pull`
 3. Re-run `vue-run-build` from your Vue project
 
-#### "Missing required field in config.ts: slug (appPath)"
-Your Vue project's `config.ts` is missing the app identifier. Add an `appPath` or `slug` field.
+#### "Missing required field in config.ts: slug (appSlug)"
+Your Vue project's `config.ts` is missing the app identifier. Add an `appSlug` or `slug` field.
 
 #### "Missing required field in config.ts: appName"
 Your Vue project's `config.ts` is missing the display name. Add an `appName` field.
@@ -743,6 +775,12 @@ magentrix publish              # Sync to server
 #### Changes not detected after vue-run-build
 The CLI uses content hash tracking to detect changes. If you rebuild without changes, `magentrix publish` will show "All files are in sync — nothing to publish!" This is expected behavior and saves unnecessary uploads.
 
+#### Duplicate apps after changing slug
+If you changed the `appSlug`/`slug` in `config.ts` and now have two apps on the server:
+1. The old app is orphaned and needs manual cleanup
+2. Run `magentrix iris-app-delete` and select the old app to remove it
+3. See [Changing an App Slug](#changing-an-app-slug) for the proper workflow
+
 ---
 
 ## Handling Conflicts

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@magentrix-corp/magentrix-cli",
-  "version": "1.3.9",
+  "version": "1.3.10",
   "description": "CLI tool for synchronizing local files with Magentrix cloud platform",
   "main": "index.js",
   "type": "module",

package/utils/iris/config-reader.js

@@ -163,13 +163,13 @@ export function parseConfigFile(configPath) {
     result.raw = content;
 
     // Extract slug (various patterns)
-    // slug: "dashboard", appPath: "dashboard", app_path: "dashboard"
+    // slug: "dashboard", appSlug: "dashboard", app_slug: "dashboard"
     // Also handles: slug: env.slug || "fallback"
-    const slugMatch = content.match(/(?:slug|appPath|app_path)\s*:\s*["'`]([^"'`]+)["'`]/);
+    const slugMatch = content.match(/(?:slug|appSlug|app_slug)\s*:\s*["'`]([^"'`]+)["'`]/);
     if (slugMatch) {
         result.slug = slugMatch[1];
     } else {
-        const slugFallbackMatch = content.match(/(?:slug|appPath|app_path)\s*:\s*[^,\n]+\|\|\s*["'`]([^"'`]+)["'`]/);
+        const slugFallbackMatch = content.match(/(?:slug|appSlug|app_slug)\s*:\s*[^,\n]+\|\|\s*["'`]([^"'`]+)["'`]/);
         if (slugFallbackMatch) {
             result.slug = slugFallbackMatch[1];
         }
@@ -296,7 +296,7 @@ export function readVueConfig(projectPath) {
 
     // Validate required fields in config.ts
     if (!result.slug) {
-        result.errors.push('Missing required field in config.ts: slug (appPath)');
+        result.errors.push('Missing required field in config.ts: slug (appSlug)');
     }
     if (!result.appName) {
         result.errors.push('Missing required field in config.ts: appName');
@@ -422,7 +422,7 @@ Could not find config.ts in the Vue project.
 Expected location: ${join(projectPath, 'src/config.ts')}
 
 Required fields in config.ts:
-  - appPath (slug): App identifier (used as folder name)
+  - appSlug (slug): App identifier (used as folder name)
   - appName: Display name for navigation menu
 
 Required fields in .env.development:
@@ -432,7 +432,7 @@ Required fields in .env.development:
 
 Example config.ts:
   export const config = {
-    appPath: "my-app",
+    appSlug: "my-app",
     appName: "My Application"
   }