nexforge-cli 1.0.1 → 1.0.3

package/README.md

@@ -1,60 +1,113 @@
 # NexForge CLI 🚀
 
-Welcome to the NexForge Command Line Interface. This tool allows you to deploy your local projects directly to the NexForge platform without pushing to GitHub.
+The official Command Line Interface for **NexForge** - Your custom Platform as a Service (PaaS).
+Deploy, manage, and scale your applications directly from your terminal with zero friction!
 
-## Getting Started
+## Installation
 
-If you are developing this CLI locally you can link it so it's available globally on your computer
+You can install the CLI globally via NPM:
 
 ```bash
-npm link
+npm install -g nexforge-cli
 ```
 
-Now you can use the `nexforge` command from anywhere!
+## Available Commands
 
-## Commands
+Here is the complete list of commands available in the NexForge CLI:
 
-### 1. Login
-Authenticate yourself with your NexForge Project ID.
+### 🔐 1. `nexforge login`
+**Description:** Authenticate your local machine with your NexForge account.
+**Usage:**
 ```bash
 nexforge login
 ```
-This saves your configuration in your home directory `~/.nexforge/config.json`.
+**Details:** 
+- Prompts you for your personal **CLI Token** (which you can generate from your NexForge Dashboard Settings).
+- Prompts you for your **Project ID**.
+- Saves your credentials securely in `~/.nexforge/config.json`.
 
-### 2. Deploy
-Package your current directory and upload it to NexForge.
+---
+
+### ✨ 2. `nexforge init`
+**Description:** Initialize a new NexForge project right from your terminal without opening the browser.
+**Usage:**
 ```bash
-nexforge deploy
+nexforge init
 ```
-This command automatically zips your project (ignoring `node_modules` and `.env`) and sends it to the deployment queue.
+**Details:** 
+- Asks for your **Project Name**.
+- Asks for the **Framework** you are using (e.g., React, Vue, Express, Node.js).
+- Automatically registers the project on NexForge servers and links your current directory to the new Project ID.
 
-### 3. Rollback
-Revert your live site to the previous stable deployment.
+---
+
+### 🚀 3. `nexforge deploy`
+**Description:** Package and deploy your current directory to NexForge.
+**Usage:**
 ```bash
-nexforge rollback
+nexforge deploy
 ```
-*Note: This feature is currently in active development.*
+**Details:**
+- Instantly zips your source code (ignoring `node_modules`, `.git`, and `.env`).
+- Uploads the code to NexForge backend servers.
+- Automatically connects to the live **WebSocket log stream** so you can watch your build progress in real-time.
+- Returns your live deployment URL upon success.
 
 ---
 
-## 📦 How to Publish to NPM
+### 🌐 4. `nexforge env`
+**Description:** Manage your environment variables securely.
+
+#### Push Variables
+```bash
+nexforge env push
+```
+- Reads your local `.env` file and securely pushes all variables to your NexForge project.
+
+#### Pull Variables
+```bash
+nexforge env pull
+```
+- Fetches all environment variables from your live NexForge project and saves them into a local `.env` file.
+
+---
 
-Once you are satisfied with this CLI and want to share it with the world you can publish it to the NPM registry. This allows anyone to install it by running `npm install -g nexforge-cli`.
+### 📜 5. `nexforge logs`
+**Description:** Stream live build and deployment logs for your project.
+**Usage:**
+```bash
+nexforge logs
+```
+**Details:** 
+- Connects to the NexForge WebSocket server and streams real-time logs for any ongoing deployment pipelines.
 
-### Step 1: Create an NPM Account
-If you don't have one go to [npmjs.com](https://www.npmjs.com/) and create an account.
+---
 
-### Step 2: Login via Terminal
-Run the following command in your terminal and enter your NPM credentials
+### ⏪ 6. `nexforge rollback`
+**Description:** Instantly revert your live website to a previous stable deployment.
+**Usage:**
 ```bash
-npm login
+nexforge rollback
 ```
+**Details:**
+- Fetches a list of your recent successful and failed deployments.
+- Prompts you to select a version.
+- Instantly updates the symbolic links on the server to serve the older version with **zero downtime** and **no rebuild required**.
+
+---
 
-### Step 3: Publish
-Ensure your `package.json` has a unique name (e.g. `nexforge-cli`). Then simply run
+### ✏️ 7. `nexforge rename`
+**Description:** Rename the subdomain of your project.
+**Usage:**
 ```bash
-npm publish
+nexforge rename
 ```
+**Details:**
+- Asks for your new preferred subdomain.
+- Validates availability on the NexForge servers.
+- Instantly updates your live URL to the new subdomain.
+
+---
+
+### Built With ❤️ by Manav Sharma
 
-If everything is successful your package is now live on NPM!
-Every time you make updates to the code you need to bump the version number in `package.json` (e.g. `"version": "1.0.1"`) before running `npm publish` again.

package/index.js

@@ -453,5 +453,83 @@ program
     }
   })
 
+// change name of subdomain
+program
+  .command("rename")
+  .description("Rename the subdomain of your project")
+  .action(async () => {
+    const readline = require("readline").createInterface({
+      input: process.stdin,
+      output: process.stdout
+    })
+
+    console.log(chalk.cyan("✨ Let's rename your project subdomain!"))
+    
+    let defaultProjectId = ""
+    if (fs.existsSync(CONFIG_FILE)) {
+      const config = JSON.parse(fs.readFileSync(CONFIG_FILE, "utf8"))
+      defaultProjectId = config.projectId || ""
+    }
+
+    const promptText = defaultProjectId 
+      ? `What is your project ID? (${defaultProjectId}) ` 
+      : "What is your project ID? "
+    
+    readline.question(promptText, async (inputProjectId) => {
+      const projectId = inputProjectId.trim() || defaultProjectId
+
+      if (!projectId) {
+        console.log(chalk.red("Project ID cannot be empty!"))
+        readline.close()
+        return
+      }
+
+      readline.question("What is your new subdomain? ", async (newSubdomain) => {
+        if (!newSubdomain) {
+          console.log(chalk.red("Subdomain cannot be empty!"))
+          readline.close()
+          return
+        }
+
+        const spinner = ora("Renaming project subdomain...").start()
+        
+        try {
+          const response = await axios.post(`${API_BASE_URL}/cli/rename/${projectId}`, {
+            newSubdomain
+          })
+
+          const { projectId } = response.data
+
+          // Ensure the config directory exists before saving
+          if (!fs.existsSync(CONFIG_DIR)) {
+            fs.mkdirSync(CONFIG_DIR, { recursive: true })
+          }
+
+          // We preserve the existing CLI Token if it exists, and just update the projectId
+          let currentConfig = {}
+          if (fs.existsSync(CONFIG_FILE)) {
+            currentConfig = JSON.parse(fs.readFileSync(CONFIG_FILE, "utf8"))
+          }
+
+          fs.writeFileSync(CONFIG_FILE, JSON.stringify({ ...currentConfig, projectId }))
+
+          spinner.succeed(chalk.green("🎉 Project subdomain renamed successfully!"))
+          console.log(chalk.cyan(`Project ID: ${projectId} has been saved locally.`))
+          console.log(chalk.yellow(`You can now run \`nexforge deploy\` to push your code.`))
+
+        } catch (error) {
+          spinner.fail(chalk.red("Failed to rename project subdomain!"))
+          if (error.response && error.response.data) {
+            console.log(chalk.red(`Server Error: ${JSON.stringify(error.response.data)}`))
+          } else {
+            console.error(error.message)
+          }
+        } finally {
+          readline.close()
+        }
+      })
+    })
+  })
+
 // Parse the arguments passed by the user in the terminal
 program.parse(process.argv)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nexforge-cli",
-  "version": "1.0.1",
+  "version": "1.0.3",
   "description": "Custom Deployment CLI for NexForge",
   "main": "index.js",
   "bin": {