@powerhousedao/academy 2.5.0-dev.14 → 2.5.0-dev.15

package/CHANGELOG.md

@@ -1,3 +1,7 @@
+## 2.5.0-dev.15 (2025-06-11)
+
+This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
+
 ## 2.5.0-dev.14 (2025-06-10)
 
 ### 🚀 Features

package/docs/academy/01-GetStarted/home.mdx

@@ -55,7 +55,7 @@ import BrowserOnly from '@docusaurus/BrowserOnly';
       <h3 className="card-title">Get Started</h3>
     </div>
     <div className={styles.cardContent}>
-      <a href="/docs/academy/GetStarted/CreateNewPowerhouseProject" className="path-button">Build a Todo-list Document Model</a>
+      <a href="/academy/GetStarted/CreateNewPowerhouseProject" className="path-button">Build a Todo-list Document Model</a>
     </div>
   </div>
 
@@ -70,10 +70,10 @@ import BrowserOnly from '@docusaurus/BrowserOnly';
       <h3 className="card-title">Build User Experiences</h3>
     </div>
     <div className={styles.cardContent}>
-      <a href="/docs/academy/GetStarted/BuildToDoListEditor" className="path-button">Building a Todo-list Editor</a>
-      <a href="/docs/academy/BuildingUserExperiences/BuildingDocumentEditors" className="path-button">Building Document Editors</a>
-      <a href="/docs/academy/MasteryTrack/BuildingUserExperiences/BuildingADriveExplorer" className="path-button">Building Custom Drive Explorers</a>
-      <a href="/docs/academy/ComponentLibrary/DocumentEngineering" className="path-button">Component Library</a>
+      <a href="/academy/GetStarted/BuildToDoListEditor" className="path-button">Building a Todo-list Editor</a>
+      <a href="/academy/MasteryTrack/BuildingUserExperiences/BuildingDocumentEditors" className="path-button">Building Document Editors</a>
+      <a href="/academy/MasteryTrack/BuildingUserExperiences/BuildingADriveExplorer" className="path-button">Building Custom Drive Explorers</a>
+      <a href="/academy/ComponentLibrary/DocumentEngineering" className="path-button">Component Library</a>
     </div>
   </div>
 
@@ -106,10 +106,10 @@ import BrowserOnly from '@docusaurus/BrowserOnly';
       <h3 className="card-title">Work with Data</h3>
     </div>
     <div className={styles.cardContent}>
-      <a href="//docs/academy/MasteryTrack/WorkWithData/ReadingAndWritingThroughTheAPI" className="path-button">Reading & Writing through the API</a>
-      <a href="/docs/academy/MasteryTrack/WorkWithData/WorkingWithSubgraphs" className="path-button">Create your own Subgraph</a>
-      <a href="/docs/academy/WorkWithData/Analytics Engine/intro" className="path-button">Using the Analytics Engine</a>
-      <a href="/docs/academy/WorkWithData/Analytics Engine/intro" className="path-button">Using the Analytics Engine</a>
+      <a href="/academy/MasteryTrack/WorkWithData/ReadingAndWritingThroughTheAPI" className="path-button">Reading & Writing through the API</a>
+      <a href="/academy/MasteryTrack/WorkWithData/WorkingWithSubgraphs" className="path-button">Create your own Subgraph</a>
+      <a href="/academy/MasteryTrack/WorkWithData/Analytics-Engine/intro" className="path-button">Using the Analytics Engine</a>
+      <a href="/academy/MasteryTrack/WorkWithData/Analytics-Engine/intro" className="path-button">Using the Analytics Engine</a>
     </div>
   </div>
 
@@ -123,9 +123,9 @@ import BrowserOnly from '@docusaurus/BrowserOnly';
     </div>
     <div className={styles.cardContent}>
       <div className={styles.buttonContainer}>
-        <a href="/docs/academy/MasteryTrack/Launch/PublishYourProject" className="path-button">Package & Publish</a>
-        <a href="/docs/academy/Launch/LaunchYourBackend" className="path-button">Launch Back-end</a>
-        <a href="/docs/academy/Launch/LaunchYourFrontend" className="path-button">Launch Front-end</a>
+        <a href="/academy/MasteryTrack/Launch/IntroductionToPackages" className="path-button">Intro To Packages</a>
+        <a href="/academy/MasteryTrack/Launch/PublishYourProject" className="path-button">Publish Your Project</a>
+        <a href="/academy/MasteryTrack/Launch/SetupEnvironment" className="path-button">Setup a Cloud Environment</a>
       </div>
     </div>
   </div>
@@ -139,7 +139,7 @@ import BrowserOnly from '@docusaurus/BrowserOnly';
       <h3 className="card-title">Cookbook</h3>
     </div>
     <div className={styles.cardContent}>
-      <a href="/docs/academy/Cookbook" className="path-button">Powerhouse Recipes</a>
+      <a href="/academy/Cookbook" className="path-button">Powerhouse Recipes</a>
     </div>
   </div>
 
@@ -152,7 +152,7 @@ import BrowserOnly from '@docusaurus/BrowserOnly';
       <h3 className="card-title">Use-cases</h3>
     </div>
     <div className={styles.cardContent}>
-      <a href="/docs/academy/ExampleUsecases/Chatroom/SetupBuilderEnvironment" className="path-button">Explore Use-cases</a>
+      <a href="/academy/ExampleUsecases/Chatroom/SetupBuilderEnvironment" className="path-button">Explore Use-cases</a>
     </div>
   </div>
 
@@ -164,7 +164,7 @@ import BrowserOnly from '@docusaurus/BrowserOnly';
       <h3 className="card-title">Architecture</h3>
     </div>
     <div className={styles.cardContent}>
-      <a href="/academy/05-Architecture/00-PowerhouseArchitecture" className="path-button">Learn More</a>
+      <a href="/academy/Architecture/PowerhouseArchitecture" className="path-button">Learn More</a>
     </div>
   </div>
 </div>

package/docs/academy/02-MasteryTrack/05-Launch/{03-RunOnACloudServer.md → 03-RunOnACloudServer}

@@ -17,7 +17,8 @@ Let's have a look at how to set up Connect & Switchboard apps on a cloud server.
 Ask your IT provider to get access to the AWS environment to set up a server.
 Launch a new server instance for Connect and Switchboard with the specific specs that fit your project.
 
-The steps to create an EC2 instance:
+<details>
+<summary> **The steps to create an EC2 instance** </summary>
    - Make sure your region is set to eu-west-1 (Ireland)
    - Name your instance something like `cloud-server` or your project's name
    - Select Ubuntu 24.04 LTS
@@ -34,13 +35,15 @@ The steps to create an EC2 instance:
       - Custom TCP (Port 8441) for Switchboard
    - **Launch the instance**
 
+   :::warning
+   Make sure to keep your key pair file (.pem) secure and never share it. Without it, you won't be able to access your instance. Also, consider setting up AWS IAM roles and policies for better security management.
+   :::
+
+</details>
+
 Now click on your instance ID, which will open a new window with the instance details. Hit the 'Connect' button to get the connection details.
 Within the instance details, you'll find the public IP address of your server instance. We'll use this to connect to our server instance later.
 
-:::warning
-Make sure to keep your key pair file (.pem) secure and never share it. Without it, you won't be able to access your instance. Also, consider setting up AWS IAM roles and policies for better security management.
-:::
-
 ### 1.2. Setting up your SSH connection
 
 Once you've generated your key pairs and added them to the designated folder, you can set up the SSH connections to start the process.

package/docs/academy/02-MasteryTrack/05-Launch/03-SetupEnvironment.md

@@ -5,64 +5,19 @@ Powerhouse is a powerful platform that helps you manage and deploy your applicat
 This guide will walk you through the process of setting up both the Powerhouse CLI and configuring your server machine to run Powerhouse services. Whether you're setting up a development environment or preparing for production deployment, this guide provides all the necessary steps and considerations.
 
 ## Prerequisites
-Before you begin, ensure you have a Linux-based system (Ubuntu or Debian recommended), sudo privileges, and a stable internet connection. These are essential for the installation and configuration process. The system should have at least 1GB of RAM and 10GB of free disk space for optimal performance. While these are minimum requirements, more resources will provide better performance, especially when running multiple services.
+Before you begin, ensure you have a Linux-based system (Ubuntu or Debian recommended), sudo privileges, and a stable internet connection.   
+These are essential for the installation and configuration process. 
+The system should have at least 1GB of RAM and 10GB of free disk space for optimal performance. 
+While these are minimum requirements, more resources will provide better performance, especially when running multiple services.
 
-## 1. Setting up a new cloud environment
-
-The `install` script provides a streamlined way to install the Powerhouse CLI tool and all its necessary dependencies. This script handles the installation of node.js 22, pnpm, Powerhouse CLI itself and the services. It's designed to work across different Linux distributions, though it's optimized for Ubuntu and Debian-based systems. It also prepares your machine for running Powerhouse services. It handles everything from package installation to service configuration, making the setup process straightforward and automated. This script is particularly useful for setting up new servers or reconfiguring existing ones.
-
-
-### Installation Steps:
-
-1. Run the setup script:
-```bash
-curl -fsSL https://apps.powerhouse.io/install | bash # for macOS, Linux, and WSL
-```
-
-2. After installation, source your shell configuration:
-```bash
-source ~/.bashrc  # or source ~/.zshrc if using zsh
-```
-
-3. Verify the installation:
-```bash
-ph --version
-```
-
-4. You will see ph-cli is not yet installed. But it will get installed automatically in the next step. 
-If you are a builder that wants to make use of the dev releases use `ph use dev` before going to the next step. 
-   - `ph use dev`: Development version - Use this for testing new features or development work
-   - `ph use staging`: Staging version - Use this for pre-production testing
-
-5. Initialize your project with `ph init <project-name>` 
-
-6. Follow the interactive prompts that are appearing after having installed your first package. 
-
-### Step 1: Package Installation
-During the package installation phase, you'll be prompted to enter package names that you want to install. For example, you might want to `ph install @powerhousedao/todo-demo-package` or other Powerhouse packages. This step is crucial for adding the specific functionality you need to your Powerhouse installation. 
-
-You can also press Enter to skip this step if you don't need to install any packages immediately, but you can always install packages later using the `ph install` command.
-
-### Step 2: Database Configuration
-The script offers two options for database configuration. 
-
-**Option 1:** Sets up a local PostgreSQL database, which is ideal for development or small deployments. It automatically creates a database user with a secure random password and configures the database to accept local connections. This option is perfect for getting started quickly or for development environments. 
-
-**Option 2:** Allows you to connect to a remote PostgreSQL database by providing a connection URL in the format `postgres://user:password@host:port/db`. This is recommended for production environments where you might want to use a managed database service or a dedicated database server.
-
-### Step 3: SSL Configuration
-For SSL configuration, you have two choices. 
-
-**Option 1:** The **Let's Encrypt** option is recommended for production environments. It requires you to provide a base domain (like `powerhouse.xyz`) and optional subdomains for your services. The script will automatically obtain and configure SSL certificates for your domains, ensuring secure communication between your services and clients. 
-
-**Option 2:** The self-signed certificate option is suitable for development or testing environments. It uses your machine's hostname and generates a self-signed certificate, configuring the services with appropriate base paths. While this option is convenient for development, browsers will show security warnings, which is why it's not recommended for production use.
+Also make sure you have your preferred domain registered and created subdomains for your Connect & Switchboard instances.
 
 <details>
-<summary>Setting up a domain in DigitalOcean</summary>
+<summary>**Setting up a Droplet (Digitial Ocean) instance and connecting your domain**</summary>
 
 This tutorial will guide you through the process of creating a new virtual private server (called a "Droplet") on DigitalOcean and then pointing your custom domain name to it. This will allow users to access your server using a memorable URL like `www.yourdomain.com`.
 
-**Current Date:** May 15, 2025
+**Current Date:** May 15, 2024
 
 ## Part 1: Setting Up Your DigitalOcean Droplet
 
@@ -162,6 +117,18 @@ Now your Droplet is running! Now you can continue with the Powerhouse tutorial o
      - **WILL DIRECT TO:** Your Droplet's IP
      - **TTL:** 3600
 
+   - **Connect Subdomain (A Record):**
+     - **TYPE:** A
+     - **HOSTNAME:** connect
+     - **WILL DIRECT TO:** Your Droplet's IP
+     - **TTL:** 3600
+
+   - **Switchboard Subdomain (A Record):**
+     - **TYPE:** A
+     - **HOSTNAME:** switchboard
+     - **WILL DIRECT TO:** Your Droplet's IP
+     - **TTL:** 3600
+
 #### Option B: Using Your Existing Nameservers (NS locked)
 
 1. **Just Create DNS Records at Your Registrar:**
@@ -177,6 +144,18 @@ Now your Droplet is running! Now you can continue with the Powerhouse tutorial o
      - **VALUE:** Your Droplet's IP
      - **TTL:** 3600
 
+   - **Connect Subdomain (A Record):**
+     - **TYPE:** A
+     - **HOSTNAME:** connect
+     - **VALUE:** Your Droplet's IP
+     - **TTL:** 3600
+
+   - **Switchboard Subdomain (A Record):**
+     - **TYPE:** A
+     - **HOSTNAME:** switchboard
+     - **VALUE:** Your Droplet's IP
+     - **TTL:** 3600
+
 **Note:** DNS changes may take up to 48 hours to propagate globally.
 
 ### Verify Configuration
@@ -185,20 +164,43 @@ Now your Droplet is running! Now you can continue with the Powerhouse tutorial o
    ```bash
    dig +short yourdomain.com
    dig +short www.yourdomain.com
+   dig +short connect.yourdomain.com
+   dig +short switchboard.yourdomain.com
    ```
 
-2. Both should return your Droplet's IP address
+2. All should return your Droplet's IP address
 
 **Congratulations!** You have successfully set up your DigitalOcean Droplet and configured your domain. Your server is now ready to host your Powerhouse services.
 
 </details>
 
 <details>
-<summary>Setting up a domain with AWS EC2</summary>
+<summary> **Setting up an EC2 instance and connecting your domain** </summary>
 
 This tutorial will guide you through the process of assigning a static IP (Elastic IP) to your EC2 instance and configuring your domain to point to it.
 
-**Current Date:** May 15, 2025
+**Current Date:** May 15, 2024
+
+   - Make sure your region is set to eu-west-1 (Ireland)
+   - Name your instance something like `cloud-server` or your project's name
+   - Select Ubuntu 24.04 LTS
+   - Architecture 64-bit (x86)
+   - Scroll down to Instance type and select t2.medium (recommended)
+      - 2 vCPUs and 4 GiB of memory are the recommended minimum specs
+      - For larger projects or higher load, consider t2.large or t2.xlarge
+   - Create a new key pair and save it in a secure location from which you can connect to your instance with the SSH client later.
+   - Configure the security group to allow inbound traffic:
+      - SSH (Port 22) from your IP address
+      - HTTP (Port 80) from anywhere
+      - HTTPS (Port 443) from anywhere
+      - Custom TCP (Port 8442) for Connect
+      - Custom TCP (Port 8441) for Switchboard
+   - **Launch the instance**
+
+   :::warning
+   Make sure to keep your key pair file (.pem) secure and never share it. Without it, you won't be able to access your instance. Also, consider setting up AWS IAM roles and policies for better security management.
+   :::
+
 
 ## Part 1: Assigning a Static IP to EC2 Instance
 
@@ -253,6 +255,18 @@ This tutorial will guide you through the process of assigning a static IP (Elast
      - **VALUE:** Your Elastic IP
      - **TTL:** 3600
 
+   - **Connect Subdomain (A Record):**
+     - **TYPE:** A
+     - **HOSTNAME:** connect
+     - **VALUE:** Your Elastic IP
+     - **TTL:** 3600
+
+   - **Switchboard Subdomain (A Record):**
+     - **TYPE:** A
+     - **HOSTNAME:** switchboard
+     - **VALUE:** Your Elastic IP
+     - **TTL:** 3600
+
 ### Option B: Using Your Existing Nameservers
 
 1. **Create DNS Records at Your Registrar:**
@@ -268,6 +282,18 @@ This tutorial will guide you through the process of assigning a static IP (Elast
      - **VALUE:** Your Elastic IP
      - **TTL:** 3600
 
+   - **Connect Subdomain (A Record):**
+     - **TYPE:** A
+     - **HOSTNAME:** connect
+     - **VALUE:** Your Elastic IP
+     - **TTL:** 3600
+
+   - **Switchboard Subdomain (A Record):**
+     - **TYPE:** A
+     - **HOSTNAME:** switchboard
+     - **VALUE:** Your Elastic IP
+     - **TTL:** 3600
+
 1. **Set Up DNS First:**
    - Create A records for all subdomains before running the setup script
    - Point them to your EC2 instance's public IP address
@@ -279,27 +305,77 @@ This tutorial will guide you through the process of assigning a static IP (Elast
    ```bash
    dig +short yourdomain.com
    dig +short www.yourdomain.com
+   dig +short connect.yourdomain.com
+   dig +short switchboard.yourdomain.com
    ```
 
-2. Both should return your Elastic IP address
+2. All should return your Elastic IP address
 
 **Congratulations!** You have successfully set up your EC2 instance with a static IP and configured your domain. Your server is now ready to host your Powerhouse services.
 
 </details>
 
-### Step 4: Service Configuration
+## 1. Setting up a new cloud environment
+
+The `install` script provides a streamlined way to install the Powerhouse CLI tool and all its necessary dependencies. This script handles the installation of Node.js 22, pnpm, and the Powerhouse CLI itself. It's designed to work across different Linux distributions, though it's optimized for Ubuntu and Debian-based systems. It also prepares your machine for running Powerhouse services. It handles everything from package installation to service configuration, making the setup process straightforward and automated. This script is particularly useful for setting up new servers or reconfiguring existing ones.
+
+### Installation
+
+1.  Run the setup script:
+    ```bash
+    curl -fsSL https://apps.powerhouse.io/install | bash # for macOS, Linux, and WSL
+    ```
+
+2.  After installation, source your shell configuration:
+    ```bash
+    source ~/.bashrc  # or source ~/.zshrc if using zsh
+    ```
+
+3.  Verify that the Powerhouse CLI is ready to be installed in the next step:
+    ```bash
+    ph --version
+    ```
+    You will see that `ph-cli` is not yet installed. This is expected, as it will be installed by the service setup command.
+
+### Service Configuration
+
+Next, run `ph service setup` and follow the interactive prompts. This command installs the Powerhouse services (Connect and Switchboard) and guides you through their configuration.
+
+:::info
+**What does `ph service setup` do?**
+The script takes care of all the necessary service configuration automatically.
+It installs and configures **Nginx** as a reverse proxy, sets up SSL certificates, and configures the proxy settings for optimal performance.
+It also installs **PM2** for process management and starts your services with the appropriate configuration based on your SSL choice.
+The Nginx configuration includes optimizations for **WebSocket connections**, static file serving, and security headers.
+PM2 is configured to automatically restart services if they crash and to start them on system boot.
+:::
+
+The setup command will prompt you for the following information:
+
+#### Package Installation
+During this phase, you can enter package names that you want to install. For example, you might want to `ph install @powerhousedao/todo-demo-package` or other Powerhouse packages. This step is crucial for adding the specific functionality you need. You can also press Enter to skip this step and install packages later using the `ph install` command.
+
+#### Database Configuration
+The script offers two options for database configuration:
+*   **Option 1: Local Database** Sets up a local PostgreSQL database, which is ideal for development or small deployments. It automatically creates a database user with a secure random password and configures the database to accept local connections. This option is perfect for getting started quickly.
+*   **Option 2: Remote Database** Allows you to connect to a remote PostgreSQL database by providing a connection URL in the format `postgres://user:password@host:port/db`. This is recommended for production environments.
 
-The script takes care of all the necessary service configuration automatically. It installs and configures **Nginx** as a reverse proxy, sets up SSL certificates, and configures the proxy settings for optimal performance. It also installs **PM2** for process management and starts your services with the appropriate configuration based on your SSL choice. The Nginx configuration includes optimizations for **WebSocket connections**, static file serving, and security headers. PM2 is configured to automatically restart services if they crash and to start them on system boot.
+#### SSL Configuration
+For SSL configuration, you have two choices:
+*   **Option 1: Let's Encrypt (Recommended for Production)** This option requires you to provide a base domain (e.g., `powerhouse.xyz`) and subdomains for your services. The script will automatically obtain and configure SSL certificates for your domains.
+*   **Option 2: Self-signed Certificate** This is suitable for development or testing. It uses your machine's hostname and generates a self-signed certificate. Browsers will show security warnings with this option.
 
-### Step 5: Security Features
-Security is a top priority in the setup process. The script implements automatic SSL certificate management, generates secure database passwords, and configures security headers in Nginx. It also sets up proper proxy settings to support WebSocket connections securely. The security headers include protection against common web vulnerabilities, and the SSL configuration uses modern cipher suites and protocols. The script also ensures that sensitive files and directories have appropriate permissions.
+#### Domain Setup
+You will be asked to enter your `connect` and `switchboard` subdomains to complete the setup. If you need more information, revisit the cloud provider setup sections at the beginning of this guide.
 
+#### Security Features
+Security is a top priority. The script implements automatic SSL certificate management, generates secure database passwords, and configures security headers in Nginx, and sets up proper proxy settings to support WebSocket connections securely.
 
-## 3. Verifying the Setup
+## 2. Verifying the Setup
 
 After the installation is complete, it's important to verify that everything is working correctly. You can check the status of your services using PM2, verify the Nginx configuration, and ensure your SSL certificates are properly installed. This step is crucial for identifying any potential issues before they affect your users.
 
-1. Check service status of switchboard & connect:
+1. Check service status of switchboard and connect:
 ```bash
 ph service status
 ```
@@ -320,9 +396,10 @@ sudo nginx -t
 sudo certbot certificates  # if using Let's Encrypt
 ```
 
-## 4. Accessing Services
+## 3. Accessing the Services
 
-Once everything is set up, you can access your services through the configured domains. If you chose Let's Encrypt, your services will be available at their respective subdomains. With a self-signed certificate, you'll access the services through your machine's hostname with the appropriate base paths. The services are configured to use HTTPS by default, ensuring secure communication.
+Once everything is set up, you can access your services through the configured domains.   
+If you chose Let's Encrypt, your services will be available at their respective subdomains. With a self-signed certificate, you'll access the services through your machine's hostname with the appropriate base paths. The services are configured to use HTTPS by default, ensuring secure communication.
 
 ### With Let's Encrypt:
 - Connect: `https://connect.yourdomain.com`
@@ -332,18 +409,18 @@ Once everything is set up, you can access your services through the configured d
 - Connect: `https://your-hostname/connect`
 - Switchboard: `https://your-hostname/switchboard`
 
-## 5. Troubleshooting
+## 4. Troubleshooting
 
 When issues arise, there are several common problems you might encounter. 
-- The "ph: command not found" error usually means you need to source your shell configuration file. 
+- The "`ph`: command not found" error usually means you need to source your shell configuration file. 
 - Nginx configuration errors can be investigated through the error logs, and service issues can be diagnosed using PM2 logs. 
 - SSL certificate problems often relate to DNS settings or certificate paths. Understanding these common issues and their solutions will help you maintain a stable Powerhouse installation.
 
 ### Common Issues:
-1. **"ph: command not found"**
+1. **"`ph`: command not found"**
    - Run `source ~/.bashrc` or restart your terminal
-   - Verify that the PNPM_HOME environment variable is set correctly
-   - Check if the ph binary exists in the PNPM_HOME directory
+   - Verify that the `PNPM_HOME` environment variable is set correctly
+   - Check if the `ph` binary exists in the `PNPM_HOME` directory
 
 2. **Nginx configuration errors**
    - Check logs: `sudo tail -f /var/log/nginx/error.log`
@@ -360,7 +437,7 @@ When issues arise, there are several common problems you might encounter.
    - Check certificate paths in Nginx config
    - Ensure that the certificate files are readable by Nginx
 
-## 6. Maintenance
+## 5. Maintenance
 
 Regular maintenance is crucial for keeping your Powerhouse installation running smoothly. You can update services using the Powerhouse CLI, restart services through PM2, and monitor logs to ensure everything is functioning correctly. Regular maintenance helps prevent issues and ensures that your services are running with the latest security patches and features.
 
@@ -374,16 +451,16 @@ ph update <package-name>
 ph service restart
 ```
 
-### Viewing Logs:
+### Checking Service Status and Logs:
 ```bash
 ph service status
 ```
 
-## 7. Security Notes
+## 6. Security Notes
 
 Maintaining security is an ongoing process. It's essential to keep your database credentials secure and regularly update your SSL certificates. Regular monitoring of system logs helps identify potential security issues, and keeping your system and packages updated ensures you have the latest security patches. Consider implementing additional security measures such as firewall rules, intrusion detection systems, and regular security audits.
 
-## 8. Backup
+## 7. Backup
 
 Regular backups are crucial for data safety. The database can be backed up using pg_dump, and your configuration files can be archived using tar. These backups should be stored securely and tested regularly to ensure they can be restored if needed. Consider implementing an automated backup schedule and storing backups in multiple locations for redundancy.
 
@@ -397,7 +474,7 @@ pg_dump -U powerhouse -d powerhouse > backup.sql
 sudo tar -czf powerhouse-config.tar.gz /etc/powerhouse/
 ```
 
-## 9. Best Practices
+## 8. Best Practices
 
 To get the most out of your Powerhouse installation, follow these best practices:
 
@@ -407,7 +484,7 @@ To get the most out of your Powerhouse installation, follow these best practices
 4. **Testing**: Test your backup and restore procedures regularly.
 5. **Security**: Regularly review and update your security measures.
 
-## 10. Getting Help
+## 9. Getting Help
 
 If you encounter issues or need assistance, there are several resources available:
 

package/docs/academy/08-Glossary.md

@@ -17,7 +17,7 @@
 - **Powerhouse Academy** – A training platform for onboarding and upskilling SNO contributors.
 - **Connect** – The contributor's public or private workspace, serving as the entry point for individual contributors to install apps and packages for specific business solutions.
 - **Powergrid** – A decentralized network of reactors that sync with each other.
-- **ph-cmd (Powerhouse CLI)** – The command-line tool for Powerhouse project initialization, code generation, package management, and running local development environments (Connect Studio).
+- **Powerhouse CLI (ph)** – The command-line tool for Powerhouse project initialization, code generation, package management, and running local development environments (Connect Studio). It also manages services, ensuring the terminology aligns with the updated setup guide.
 - **Connect App (Connect Studio)** – The primary Powerhouse application for defining document models, building/testing editors (in Studio mode), and collaborating on documents.
 - **Document Tools** – Built-in features within Powerhouse applications (e.g., Connect) that assist with document management, inspection, and interaction, such as Operations History.
 - **Operations History** – A Document Tool in Connect providing a chronological, immutable log of all operations on a document for traceability.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@powerhousedao/academy",
-  "version": "2.5.0-dev.14",
+  "version": "2.5.0-dev.15",
   "homepage": "https://powerhouse.academy",
   "repository": {
     "type": "git",