@powerhousedao/academy 0.1.0-dev.6 → 2.5.0-dev.1

package/CHANGELOG.md

@@ -1,3 +1,51 @@
+## 2.5.0-dev.1 (2025-06-05)
+
+This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
+
+## 2.5.0-dev.0 (2025-06-04)
+
+### 🚀 Features
+
+- **academy:** centralize husky & auto-update cli docs ([8c92e0bb1](https://github.com/powerhouse-inc/powerhouse/commit/8c92e0bb1))
+- **ph-cli:** added setup-service command ([dfa082aa6](https://github.com/powerhouse-inc/powerhouse/commit/dfa082aa6))
+- **scripts:** updated setup scripts ([9f7fa7644](https://github.com/powerhouse-inc/powerhouse/commit/9f7fa7644))
+- enforce conventional commits ([faa49da40](https://github.com/powerhouse-inc/powerhouse/commit/faa49da40))
+- removed scalars package ([d6f7059a7](https://github.com/powerhouse-inc/powerhouse/commit/d6f7059a7))
+- enabled switchboard command ([5a9c467bf](https://github.com/powerhouse-inc/powerhouse/commit/5a9c467bf))
+- removed scalars dependencies ([596aedbd5](https://github.com/powerhouse-inc/powerhouse/commit/596aedbd5))
+- **builder-tools:** handle recursive objects in initial state generator ([c9eedcc43](https://github.com/powerhouse-inc/powerhouse/commit/c9eedcc43))
+- **monorepo:** bump graphql lib ([ba9d5d338](https://github.com/powerhouse-inc/powerhouse/commit/ba9d5d338))
+- **monorepo:** handle updating monorepo build deps ([db2ac2316](https://github.com/powerhouse-inc/powerhouse/commit/db2ac2316))
+- **monorepo:** regenerate lockfile ([a6c390b4e](https://github.com/powerhouse-inc/powerhouse/commit/a6c390b4e))
+- **builder-tools:** fix wrong value used for field id ([a6c6142e0](https://github.com/powerhouse-inc/powerhouse/commit/a6c6142e0))
+- **reactor-api,reactor-local:** updated analytics dependencies ([cbeace573](https://github.com/powerhouse-inc/powerhouse/commit/cbeace573))
+
+### 🩹 Fixes
+
+- **academy:** docker build ([58e83be09](https://github.com/powerhouse-inc/powerhouse/commit/58e83be09))
+- **academy:** lockfile issue second time' ([6208fe614](https://github.com/powerhouse-inc/powerhouse/commit/6208fe614))
+- **academy:** fix frozen lockfile issue' ([80f18ec73](https://github.com/powerhouse-inc/powerhouse/commit/80f18ec73))
+- **academy:** fix frozen lockfile issue ([bfc3dcd21](https://github.com/powerhouse-inc/powerhouse/commit/bfc3dcd21))
+- **pre-commit:** use bash syntax and shebang ([da00ff581](https://github.com/powerhouse-inc/powerhouse/commit/da00ff581))
+- added missing dep to academy ([4ec6c8278](https://github.com/powerhouse-inc/powerhouse/commit/4ec6c8278))
+- **academy:** clean up husky script ([e18e26cd8](https://github.com/powerhouse-inc/powerhouse/commit/e18e26cd8))
+- **academy:** deployment ([36e5f194d](https://github.com/powerhouse-inc/powerhouse/commit/36e5f194d))
+- **switchboard:** docker build ([7052e39e1](https://github.com/powerhouse-inc/powerhouse/commit/7052e39e1))
+- docker build with PH_PACKAGES ([856ac1187](https://github.com/powerhouse-inc/powerhouse/commit/856ac1187))
+- **document-drive:** fix type issue on browser storage ([240a78b41](https://github.com/powerhouse-inc/powerhouse/commit/240a78b41))
+- **ph-cli:** ph add does not remove installed packages ([aedfbf56e](https://github.com/powerhouse-inc/powerhouse/commit/aedfbf56e))
+- remove .env and add to .gitignore ([0d2d48684](https://github.com/powerhouse-inc/powerhouse/commit/0d2d48684))
+- **switchboard,reactor-local:** latest version of sky atlas was not being installed ([72bf72fd4](https://github.com/powerhouse-inc/powerhouse/commit/72bf72fd4))
+
+### ❤️ Thank You
+
+- acaldas @acaldas
+- Benjamin Jordan
+- Callme-T
+- Frank
+- Guillermo Puente @gpuente
+- ryanwolhuter @ryanwolhuter
+
 ## 0.1.0-dev.6 (2025-06-04)
 
 ### 🩹 Fixes

package/docs/academy/01-GetStarted/03-ImplementOperationReducers.md

@@ -11,8 +11,7 @@ Reducers are a core concept in Powerhouse document models. They implement the st
 **Connection to Schema Definition Language (SDL)**: The reducers directly implement the operations you defined in your SDL. Remember how we defined `AddTodoItemInput`, `UpdateTodoItemInput`, and `DeleteTodoItemInput` in our schema?   
 The reducers provide the actual implementation of what happens when those operations are performed.
 
-To import the document model specification into your Powerhouse project, you can either:
- 
+To import the document model specification into your Powerhouse project, you can either: 
 - Copy and paste the file directly into the root of your Powerhouse project.
 - Or drag and drop the file into the Powerhouse project directory in the VSCode editor as seen in the image below:
 

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

@@ -6,67 +6,36 @@ Powerhouse is a powerful platform that helps you manage and deploy your applicat
 ## 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.
 
-## 1. Installing Powerhouse CLI
+## 1. Setting up a new cloud environment
 
-The `install-tools.sh` 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.
+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. Download the setup script:
-```bash
-curl -O https://raw.githubusercontent.com/powerhouse-inc/powerhouse/refs/heads/main/scripts/install-tools.sh
-```
-
-2. Make the script executable:
-```bash
-chmod +x install-tools.sh
-```
 
-3. Run the script:
+### Installation Steps:
+1. Run the setup script:
 ```bash
-./install-tools.sh
+curl -fsSL https://apps.powerhouse.io/install | bash # for macOS, Linux, and WSL
 ```
 
-4. Choose a version when prompted:
-   - `dev`: Development version - Use this for testing new features or development work
-   - `staging`: Staging version - Use this for pre-production testing
-   - RECOMMENDED: `latest`: Latest stable version - Recommended for production environments
-   - Press Enter to go ahead with the latest version
-
-5. After installation, source your shell configuration:
+2. After installation, source your shell configuration:
 ```bash
 source ~/.bashrc  # or source ~/.zshrc if using zsh
 ```
 
-6. Verify the installation:
+3. Verify the installation:
 ```bash
 ph --version
 ```
 
-## 2. Configuring Your Machine
-
-Download the setup script:
-```bash
-curl -O  https://raw.githubusercontent.com/powerhouse-inc/powerhouse/refs/heads/main/scripts/setup-environment.sh
-```
-
-The `setup-environment.sh` script is a comprehensive tool that 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.
+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
 
-### Configuration Steps:
-
-1. Make the script executable:
-```bash
-chmod +x setup-environment.sh
-```
-
-2. Run the script:
-```bash
-./setup-environment.sh
-```
-
-3. Follow the interactive prompts:
+5. Follow the interactive prompts:
 
 ### 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 install `@sky-ph/atlas` or other Powerhouse packages. This step is crucial for adding the specific functionality you need to your Powerhouse installation. You can 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.
+During the package installation phase, you'll be prompted to enter package names that you want to install. For example, you might want to 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 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. 
@@ -138,7 +107,7 @@ It will take a minute or two for your Droplet to be provisioned. Once it's ready
 
 To log in via SSH:
 
-1. Open a terminal (on macOS/Linux) or an SSH client like PuTTY (on Windows).
+1. Open a terminal (on macOS/Linux) or an SSH client like PuTTY (on Windows). You can also use Digital Ocean's web 'Console'. 
 2. Use one of these commands:
    ```bash
    # If using password authentication
@@ -154,7 +123,7 @@ To log in via SSH:
 3. If you used a password, you'll be prompted to enter it.
 4. If it's your first time logging in, you might be asked to change the root password.
 
-Now your Droplet is running! You'll likely want to install and configure a web server (like Nginx or Apache) and your application or website files. This part is beyond the scope of just creating the Droplet but is crucial for it to do anything useful.
+Now your Droplet is running! Now you can continue with the Powerhouse tutorial or any next steps.
 
 ### DNS Configuration
 
@@ -165,7 +134,7 @@ Now your Droplet is running! You'll likely want to install and configure a web s
    - Enter your domain name (e.g., `yourdomain.com`)
    - Click "Add Domain"
 
-2. **Update Nameservers at Your Domain Registrar:**
+2. **Start with Updating Nameservers at Your Domain Registrar:**
    - Log in to your domain registrar
    - Update nameservers to:
      ```
@@ -187,9 +156,9 @@ Now your Droplet is running! You'll likely want to install and configure a web s
      - **WILL DIRECT TO:** Your Droplet's IP
      - **TTL:** 3600
 
-#### Option B: Using Your Existing Nameservers
+#### Option B: Using Your Existing Nameservers (NS locked)
 
-1. **Create DNS Records at Your Registrar:**
+1. **Just Create DNS Records at Your Registrar:**
    - **Root Domain (A Record):**
      - **TYPE:** A
      - **HOSTNAME:** @
@@ -324,10 +293,16 @@ Security is a top priority in the setup process. The script implements automatic
 
 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:
+1. Check service status of switchboard & connect:
+```bash
+ph service status
+```
+You can also use
+
 ```bash
-pm2 status
+ph service start | stop | restart 
 ```
+- to start | stop | restart switchboard and connect
 
 2. View Nginx configuration:
 ```bash
@@ -390,12 +365,12 @@ ph update <package-name>
 
 ### Restarting Services:
 ```bash
-pm2 restart all
+ph service restart
 ```
 
 ### Viewing Logs:
 ```bash
-pm2 logs
+ph service status
 ```
 
 ## 7. Security Notes

package/package.json

@@ -1,7 +1,11 @@
 {
   "name": "@powerhousedao/academy",
-  "version": "0.1.0-dev.6",
+  "version": "2.5.0-dev.1",
   "homepage": "https://powerhouse.academy",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/powerhouse-inc/powerhouse"
+  },
   "dependencies": {
     "@codesandbox/sandpack-react": "^2.14.4",
     "@docusaurus/core": "^3.8.0",