odac 0.9.0 → 1.0.0

package/core/Lang.js

@@ -1,52 +0,0 @@
-const fs = require('fs')
-
-class Lang {
-  #locale = Intl.DateTimeFormat().resolvedOptions().locale
-  #file = __dirname + '/../locale/' + this.#locale + '.json'
-  #strings = {}
-  #loaded = false
-
-  constructor() {
-    this.#load()
-  }
-
-  #save() {
-    try {
-      fs.promises.writeFile(this.#file, JSON.stringify(this.#strings, null, 4), 'utf8')
-    } catch (err) {
-      console.error('Error saving language file:', err)
-    }
-  }
-
-  #load() {
-    try {
-      const data = fs.readFileSync(this.#file, 'utf8')
-      this.#loaded = true
-      this.#strings = JSON.parse(data)
-    } catch {
-      this.#strings = {}
-      this.#save()
-    }
-    return true
-  }
-
-  get(key, ...args) {
-    if (!this.#loaded) this.#load()
-    if (key === 'CandyPack') return 'CandyPack'
-    let text = this.#strings[key]
-    if (text === undefined) {
-      text = key
-      this.#strings[key] = text
-      this.#save()
-    }
-    if (args.length > 0) {
-      args.forEach((arg, i) => {
-        if (text.includes(`%s${i + 1}`)) text = text.replace(`%s${i + 1}`, arg)
-        else text = text.replace('%s', arg)
-      })
-    }
-    return text
-  }
-}
-
-module.exports = Lang

package/core/Log.js

@@ -1,43 +0,0 @@
-class Log {
-  #cliMode = false
-
-  constructor() {
-    // Detect if we're running in CLI mode
-    // CLI mode is when the main module is in cli/ or bin/ directory
-    if (require.main && require.main.filename) {
-      const mainFile = require.main.filename
-      this.#cliMode = mainFile.includes('/cli/') || mainFile.includes('/bin/')
-    }
-  }
-
-  init(...arg) {
-    this.module = '[' + arg.join('][') + '] '
-    return {
-      error: this.error.bind(this),
-      log: this.log.bind(this)
-    }
-  }
-
-  error(...arg) {
-    // Always show errors, even in CLI mode
-    console.error(this.module, ...arg)
-  }
-
-  log(...arg) {
-    // Suppress logs in CLI mode to avoid breaking the interface
-    if (this.#cliMode) return
-
-    if (!arg.length) return this
-    if (typeof arg[0] === 'string' && arg[0].includes('%s')) {
-      let message = arg.shift()
-      while (message.includes('%s') && arg.length > 0) {
-        message = message.replace('%s', arg.shift())
-      }
-      message = message.replace(/%s/g, '')
-      arg.unshift(message)
-    }
-    console.log(this.module, ...arg)
-  }
-}
-
-module.exports = Log

package/core/Process.js

@@ -1,26 +0,0 @@
-const findProcess = require('find-process').default
-
-class Process {
-  stop(pid) {
-    return new Promise(resolve => {
-      findProcess('pid', pid)
-        .then(list => {
-          for (const proc of list) if (proc.name == 'node') process.kill(proc.pid, 'SIGTERM')
-        })
-        .catch(() => {})
-        .finally(() => {
-          resolve()
-        })
-    })
-  }
-
-  async stopAll() {
-    if (Candy.core('Config').config.server?.watchdog) await this.stop(Candy.core('Config').config.server.watchdog)
-    if (Candy.core('Config').config.server?.pid) await this.stop(Candy.core('Config').config.server.pid)
-    for (const domain of Object.keys(Candy.core('Config').config?.websites ?? {}))
-      if (Candy.core('Config').config.websites[domain].pid) await this.stop(Candy.core('Config').config.websites[domain].pid)
-    for (const service of Candy.core('Config').config.services ?? []) if (service.pid) await this.stop(service.pid)
-  }
-}
-
-module.exports = Process

package/docs/backend/05-controllers/02-your-trusty-candy-assistant.md

@@ -1,20 +0,0 @@
-## 🤝 Your trusty `Candy` Assistant
-
-Remember the `Candy` object? It's your best friend inside a controller. It's passed to your controller function and gives you all the tools you need for the current request.
-
-#### Awesome Services at Your Fingertips
-
-*   `Candy.Request`: Info about the user's request.
-*   `Candy.View`: Renders your HTML pages.
-*   `Candy.Auth`: Manages user logins.
-*   `Candy.Token`: Protects your forms.
-*   `Candy.Lang`: Helps with different languages.
-
-#### Handy Helper Functions
-
-*   `Candy.return(data)`: Send back a response.
-*   `Candy.direct(url)`: Redirect the user to a new page.
-*   `Candy.cookie(key, value)`: Set a browser cookie.
-*   `Candy.validator()`: Check user input easily.
-
-With controllers and the `Candy` object, you have everything you need to start building powerful application logic!

package/docs/server/01-installation/01-quick-install.md

@@ -1,19 +0,0 @@
-## ⚡ Quick Install
-
-This is the recommended method for most users.
-
-### Linux & macOS
-
-Run the following command in your terminal:
-
-```bash
-curl -sL https://candypack.dev/install | bash
-```
-
-### Windows
-
-Open PowerShell as an administrator and run the following command:
-
-```powershell
-iex (iwr -useb 'https://candypack.dev/install')
-```

package/docs/server/01-installation/02-manual-installation-via-npm.md

@@ -1,9 +0,0 @@
-## 📦 Manual Installation (via NPM)
-
-If you prefer to install manually or have issues with the quick install script, you can install CandyPack directly from NPM.
-
-1.  **Install Node.js:** Ensure you have Node.js (v18+) installed on your system. You can download it from [nodejs.org](https://nodejs.org/).
-2.  **Install CandyPack:** Use npm to install CandyPack globally:
-    ```bash
-    npm install -g candypack
-    ```

package/docs/server/02-get-started/01-core-concepts.md

@@ -1,7 +0,0 @@
-## 🧠 Core Concepts
-
-CandyPack is designed to be a powerful, developer-first toolkit that runs as a persistent background service on your server. Here’s how it works:
-
-- **Background Service:** Once started, CandyPack runs continuously in the background, managing all your configured websites and services. You don't need to manually keep it active.
-- **CLI Control:** You interact with and control the CandyPack server through the `candy` command-line tool. This tool allows you to start, stop, monitor, and manage your applications.
-- **Automation:** The primary goal of CandyPack is to automate common server management tasks, such as SSL certificate renewal, service monitoring, and application deployment, allowing you to focus on development.

package/docs/server/02-get-started/02-basic-commands.md

@@ -1,57 +0,0 @@
-## 💻 Basic Commands
-
-These are the most common commands for interacting with the CandyPack server.
-
-### Check Status
-To see the current status of the CandyPack server, including uptime and the number of running services, simply run the `candy` command with no arguments:
-```bash
-candy
-```
-
-### Restart the Server
-If you need to apply new configurations or restart all services, you can use the `restart` command:
-```bash
-candy restart
-```
-
-### Monitor Services
-To get a real-time, interactive view of your running websites and services, use the `monit` command:
-```bash
-candy monit
-```
-
-### View Live Logs
-For debugging purposes, you can view a live stream of all server and application logs with the `debug` command:
-```bash
-candy debug
-```
-
-### Get Help
-To see a list of all available commands, use the `help` command:
-```bash
-candy help
-```
-
-### Using Prefix Arguments
-Many CandyPack commands support prefix arguments that allow you to provide values directly in the command line, avoiding interactive prompts. This is especially useful for automation and scripting.
-
-**Common Prefixes:**
-- `-d`, `--domain`: Specify domain name
-- `-e`, `--email`: Specify email address  
-- `-p`, `--password`: Specify password
-- `-s`, `--subdomain`: Specify subdomain
-- `-i`, `--id`: Specify service ID
-- `-k`, `--key`: Specify authentication key
-
-**Example:**
-```bash
-# Interactive mode (prompts for input)
-candy web create
-
-# Single-line mode with prefix
-candy web create -d example.com
-```
-
----
-
-**Next Steps:** For more advanced topics, such as managing websites, services, SSL certificates, and mail accounts, please refer to the upcoming documentation files.

package/docs/server/02-get-started/03-cli-reference.md

@@ -1,276 +0,0 @@
-## 📖 CLI Reference
-
-This comprehensive reference covers all CandyPack CLI commands and their usage patterns, including both interactive and single-line modes with prefix arguments.
-
-### Command Structure
-
-CandyPack CLI follows a hierarchical command structure:
-```bash
-candy [command] [subcommand] [prefixes] [arguments]
-```
-
-### Prefix Arguments
-
-Most commands support prefix arguments that allow you to provide values directly in the command line, avoiding interactive prompts. This is especially useful for automation, scripting, and quick operations.
-
-#### Common Prefixes
-- `-d`, `--domain`: Domain name
-- `-e`, `--email`: Email address  
-- `-p`, `--password`: Password
-- `-s`, `--subdomain`: Subdomain name
-- `-i`, `--id`: Service ID or name
-- `-k`, `--key`: Authentication key
-
-### Authentication Commands
-
-#### `candy auth`
-Define your server to your CandyPack account.
-
-**Interactive:**
-```bash
-candy auth
-```
-
-**Single-line:**
-```bash
-candy auth -k your-auth-key
-candy auth --key your-auth-key
-```
-
-### Basic Server Commands
-
-#### `candy` (no arguments)
-Display server status, uptime, and statistics.
-
-#### `candy restart`
-Restart the CandyPack server.
-
-#### `candy monit`
-Monitor websites and services in real-time.
-
-#### `candy debug`
-View live server and application logs.
-
-#### `candy help`
-Display help information for all commands.
-
-### Service Management
-
-#### `candy run <file>`
-Add a new service by specifying the entry file path.
-
-**Example:**
-```bash
-candy run /path/to/your/app.js
-candy run ./index.js
-```
-
-#### `candy service delete`
-Delete a running service.
-
-**Interactive:**
-```bash
-candy service delete
-```
-
-**Single-line:**
-```bash
-candy service delete -i service-name
-candy service delete --id service-name
-```
-
-### Website Management
-
-#### `candy web create`
-Create a new website configuration.
-
-**Interactive:**
-```bash
-candy web create
-```
-
-**Single-line:**
-```bash
-candy web create -d example.com
-candy web create --domain example.com
-```
-
-#### `candy web delete`
-Delete a website configuration.
-
-**Interactive:**
-```bash
-candy web delete
-```
-
-**Single-line:**
-```bash
-candy web delete -d example.com
-candy web delete --domain example.com
-```
-
-#### `candy web list`
-List all configured websites.
-
-```bash
-candy web list
-```
-
-### Subdomain Management
-
-#### `candy subdomain create`
-Create a new subdomain.
-
-**Interactive:**
-```bash
-candy subdomain create
-```
-
-**Single-line:**
-```bash
-candy subdomain create -s blog.example.com
-candy subdomain create --subdomain blog.example.com
-```
-
-#### `candy subdomain delete`
-Delete a subdomain.
-
-**Interactive:**
-```bash
-candy subdomain delete
-```
-
-**Single-line:**
-```bash
-candy subdomain delete -s blog.example.com
-candy subdomain delete --subdomain blog.example.com
-```
-
-#### `candy subdomain list`
-List all subdomains for a domain.
-
-**Interactive:**
-```bash
-candy subdomain list
-```
-
-**Single-line:**
-```bash
-candy subdomain list -d example.com
-candy subdomain list --domain example.com
-```
-
-### SSL Certificate Management
-
-#### `candy ssl renew`
-Renew SSL certificate for a domain.
-
-**Interactive:**
-```bash
-candy ssl renew
-```
-
-**Single-line:**
-```bash
-candy ssl renew -d example.com
-candy ssl renew --domain example.com
-```
-
-### Mail Account Management
-
-#### `candy mail create`
-Create a new email account.
-
-**Interactive:**
-```bash
-candy mail create
-```
-
-**Single-line:**
-```bash
-candy mail create -e user@example.com -p password123
-candy mail create --email user@example.com --password password123
-```
-
-#### `candy mail delete`
-Delete an email account.
-
-**Interactive:**
-```bash
-candy mail delete
-```
-
-**Single-line:**
-```bash
-candy mail delete -e user@example.com
-candy mail delete --email user@example.com
-```
-
-#### `candy mail list`
-List all email accounts for a domain.
-
-**Interactive:**
-```bash
-candy mail list
-```
-
-**Single-line:**
-```bash
-candy mail list -d example.com
-candy mail list --domain example.com
-```
-
-#### `candy mail password`
-Change password for an email account.
-
-**Interactive:**
-```bash
-candy mail password
-```
-
-**Single-line:**
-```bash
-candy mail password -e user@example.com -p newpassword
-candy mail password --email user@example.com --password newpassword
-```
-
-### Usage Tips
-
-#### Automation and Scripting
-Single-line commands with prefixes are perfect for automation:
-
-```bash
-#!/bin/bash
-# Create multiple email accounts
-candy mail create -e admin@example.com -p admin123
-candy mail create -e support@example.com -p support123
-candy mail create -e sales@example.com -p sales123
-
-# Set up subdomains
-candy subdomain create -s blog.example.com
-candy subdomain create -s shop.example.com
-candy subdomain create -s api.example.com
-```
-
-#### Mixed Usage
-You can mix interactive and single-line modes as needed:
-
-```bash
-# Specify domain, but let the system prompt for other details
-candy web create -d example.com
-```
-
-#### Password Security
-When using password prefixes (`-p`, `--password`):
-- Interactive mode requires password confirmation
-- Single-line mode skips confirmation for automation
-- Consider using environment variables for sensitive data in scripts
-
-```bash
-# Using environment variable
-candy mail create -e user@example.com -p "$MAIL_PASSWORD"
-```
-
-### Error Handling
-
-If a command fails or you provide invalid arguments, CandyPack will display helpful error messages and suggest corrections. Use `candy help [command]` to get specific help for any command.

package/docs/server/02-get-started/04-cli-quick-reference.md

@@ -1,102 +0,0 @@
-## ⚡ CLI Quick Reference
-
-A compact reference for all CandyPack CLI commands with their prefix arguments.
-
-### Basic Commands
-```bash
-candy                    # Show server status
-candy restart            # Restart server
-candy monit              # Monitor services
-candy debug              # View live logs
-candy help               # Show help
-```
-
-### Authentication
-```bash
-candy auth [-k|--key] <key>
-```
-
-### Services
-```bash
-candy run <file>                           # Start new service
-candy service delete [-i|--id] <service>  # Delete service
-```
-
-### Websites
-```bash
-candy web create [-d|--domain] <domain>   # Create website
-candy web delete [-d|--domain] <domain>   # Delete website
-candy web list                             # List websites
-```
-
-### Subdomains
-```bash
-candy subdomain create [-s|--subdomain] <subdomain>  # Create subdomain
-candy subdomain delete [-s|--subdomain] <subdomain>  # Delete subdomain
-candy subdomain list [-d|--domain] <domain>          # List subdomains
-```
-
-### SSL Certificates
-```bash
-candy ssl renew [-d|--domain] <domain>    # Renew SSL certificate
-```
-
-### Mail Accounts
-```bash
-candy mail create [-e|--email] <email> [-p|--password] <password>  # Create account
-candy mail delete [-e|--email] <email>                             # Delete account
-candy mail list [-d|--domain] <domain>                             # List accounts
-candy mail password [-e|--email] <email> [-p|--password] <password> # Change password
-```
-
-### Common Prefixes
-| Prefix | Long Form | Description |
-|--------|-----------|-------------|
-| `-d` | `--domain` | Domain name |
-| `-e` | `--email` | Email address |
-| `-p` | `--password` | Password |
-| `-s` | `--subdomain` | Subdomain name |
-| `-i` | `--id` | Service ID/name |
-| `-k` | `--key` | Authentication key |
-
-### Usage Patterns
-
-**Interactive Mode:**
-```bash
-candy web create
-# Prompts for domain name
-```
-
-**Single-Line Mode:**
-```bash
-candy web create -d example.com
-# No prompts, immediate execution
-```
-
-**Mixed Mode:**
-```bash
-candy mail create -e user@example.com
-# Prompts only for password
-```
-
-### Automation Examples
-```bash
-# Batch create email accounts
-candy mail create -e admin@example.com -p admin123
-candy mail create -e support@example.com -p support456
-
-# Set up multiple subdomains
-candy subdomain create -s blog.example.com
-candy subdomain create -s api.example.com
-candy subdomain create -s shop.example.com
-
-# Renew multiple SSL certificates
-candy ssl renew -d example.com
-candy ssl renew -d api.example.com
-```
-
-### Tips
-- Use single-line mode for scripts and automation
-- Use interactive mode for one-off operations
-- Combine both modes as needed
-- All commands support `--help` for detailed information

package/docs/server/03-service/01-start-a-new-service.md

@@ -1,57 +0,0 @@
-## ⚙️ Start a New Service
-
-To start a new service, use the `run` command followed by the path to your application's entry file.
-
-### Usage
-```bash
-candy run <file>
-```
-
-### Arguments
-- `<file>`: The path to the script or application entry point you want to run. This can be an absolute path or a relative path from your current directory.
-
-### Examples
-
-**Absolute path:**
-```bash
-candy run /path/to/your/app/index.js
-```
-
-**Relative path from current directory:**
-```bash
-candy run index.js
-candy run ./src/server.js
-candy run ../other-project/app.js
-```
-
-**Multiple services:**
-```bash
-# Start multiple services in sequence
-candy run ./api/index.js
-candy run ./worker/processor.js
-candy run ./scheduler/cron.js
-```
-
-### Path Resolution
-- **Absolute paths**: Start with `/` (Linux/macOS) or drive letter (Windows)
-- **Relative paths**: Resolved from your current working directory
-- **Automatic conversion**: Relative paths are automatically converted to absolute paths internally
-
-### Service Management
-Once started, CandyPack will:
-- Monitor the service continuously
-- Automatically restart it if it crashes
-- Assign it a unique service ID for management
-- Log all output for debugging
-
-You can view service status using:
-```bash
-candy monit    # Real-time monitoring
-candy          # Quick status overview
-```
-
-### Service Deletion
-To remove a running service, use:
-```bash
-candy service delete -i <service-name-or-id>
-```