@bostonuniversity/buwp-local 0.6.1 → 0.6.2

package/docs/CHANGELOG.md

@@ -7,10 +7,35 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.6.2]
+
+### Fixed
+- **Project paths with spaces** - Fixed shell command construction to properly quote Docker Compose file paths when project directory contains spaces
+- Prevents shell word-splitting errors like `unknown docker command: "compose folder/..."`
+- All Docker Compose commands (`start`, `stop`, `destroy`, `logs`, `wp`) now correctly handle paths with spaces and special characters
+
+### Changed
+- Volume mapping generation now uses cleaner functional programming pattern with `map()` and spread operator
+- Improved code readability in `generateWordPressService()` by isolating volume mapping transformation
+
+## [0.6.1]
+
+### Added
+- Container registry accessibility check on `start` command
+- Automatic Docker image pull with helpful authentication guidance
+- GitHub Packages authentication assistance when image access is denied
+
+### Fixed
+- Clear error messages for registry authentication failures with actionable next steps
+
+## [0.6.0]
+
 ### Added
 - Credential validation on `start` command with interactive setup prompt
 - Documentation consolidation in `docs/` directory
 - Comprehensive guides: GETTING_STARTED.md, COMMANDS.md, CREDENTIALS.md, MULTI_PROJECT.md, ARCHITECTURE.md
+- Robust `/etc/hosts` detection with smart one-time warnings
+- VM Sandbox migration guide highlighting architectural advantages
 
 ## [0.5.3]
 

package/docs/MIGRATION_FROM_VM.md

@@ -14,9 +14,9 @@ This guide explains the architectural advantages of buwp-local compared to tradi
 In traditional VM-based development environments:
 
 1. **Monthly rebuild cycles** - VM sandboxes must be periodically replaced with fresh builds to keep WordPress core, plugins, and infrastructure up to date
-3. **Manual preservation** - Developers must manually back up their work before each rebuild and restore it afterward
-4. **Coordination overhead** - Team-wide rebuild schedules require coordination and can interrupt active development
-5. **All-or-nothing updates** - The entire team must update together, regardless of individual project needs
+2. **Manual preservation** - Developers must manually back up their work before each rebuild and restore it afterward
+3. **Coordination overhead** - Team-wide rebuild schedules require coordination and can interrupt active development
+4. **All-or-nothing updates** - The entire team must update together, regardless of individual project needs
 
 ## How buwp-local Solves This
 

package/docs/ROADMAP.md

@@ -101,14 +101,21 @@ hostile.remove('127.0.0.1', config.hostname);
 
 ---
 
-## Incremental Functional Improvements: v0.6.1
+## Incremental Functional Improvements: v0.6.x
 **Status:** Currently Ongoing
 **Focus:** Enhancements based on initial user experience
 
+### Shipped in v0.6.1
 - **Container Registry Assistance**
   - Guide users on setting up access to private registries (ghcr.io)
   - Automatic check for registry login or existing image on `start`
 
+### Planned for v0.6.2
+
+- ***Get spaces in volume mappings working correctly***
+  - Fix issues with spaces in host paths causing Docker errors
+  - Ensure cross-platform compatibility (Windows, macOS, Linux)
+
 - **Basic docs on existing Xdebug features**
   - Quickstart guide for enabling and using Xdebug in containers
 

package/feedback-from-0-6-1.md

@@ -0,0 +1,16 @@
+feedback from 0.6.1
+
+For volume mapped sandbox flavor, make a new directory for the sandbox project.
+
+Next, use npm init to create a package.json file if you don't have one already:
+
+```bash
+npm init -y
+```
+
+Then install buwp-local as a development dependency:
+
+```bash
+npm install --save-dev @bostonuniversity/buwp-local
+```
+

package/lib/commands/destroy.js

@@ -50,7 +50,7 @@ async function destroyCommand(options) {
     try {
       // This is the actual docker compose down command that removes everything
       execSync(
-        `docker compose -p ${projectName} -f ${composePath} down -v`,
+        `docker compose -p ${projectName} -f "${composePath}" down -v`,
         { 
           cwd: composeDir,
           stdio: 'inherit'

package/lib/commands/logs.js

@@ -36,7 +36,7 @@ async function logsCommand(options) {
 
     // Build docker compose logs command
     const composeDir = path.dirname(composePath);
-    let command = `docker compose -p ${projectName} -f ${composePath} logs`;
+    let command = `docker compose -p ${projectName} -f "${composePath}" logs`;
 
     if (options.follow) {
       command += ' -f';

package/lib/commands/start.js

@@ -313,7 +313,7 @@ async function startCommand(options) {
       // This is the actual docker compose up command that starts everything
       // If there is a local .env file, it will take over the temp env file generated from the keychain, because it is specified last.
       execSync(
-        `docker compose -p ${projectName} ${tempEnvFileFlag} ${envFileFlag} -f ${composePath} up -d`,
+        `docker compose -p ${projectName} ${tempEnvFileFlag} ${envFileFlag} -f "${composePath}" up -d`,
         { 
           cwd: composeDir,
           stdio: 'inherit'

package/lib/commands/stop.js

@@ -39,7 +39,7 @@ async function stopCommand() {
     
     try {
       execSync(
-        `docker compose -p ${projectName} -f ${composePath} stop`,
+        `docker compose -p ${projectName} -f "${composePath}" stop`,
         { 
           cwd: composeDir,
           stdio: 'inherit'

package/lib/commands/wp.js

@@ -35,7 +35,7 @@ async function wpCommand(args, _options) {
     // Build docker compose exec command for WP-CLI
     const composeDir = path.dirname(composePath);
     const wpArgs = args.join(' ');
-    const command = `docker compose -p ${projectName} -f ${composePath} exec wordpress wp ${wpArgs}`;
+    const command = `docker compose -p ${projectName} -f "${composePath}" exec wordpress wp ${wpArgs}`;
 
     // Execute WP-CLI command
     try {

package/lib/compose-generator.js

@@ -152,16 +152,13 @@ function generateWordPressService(config, wpVolumeName) {
     environment.WORDPRESS_CONFIG_EXTRA = wpConfigExtra;
   }
 
-  // Build volumes array
-  const volumes = [`${wpVolumeName}:/var/www/html`];
-  
-  // Add custom mappings
-  if (config.mappings && Array.isArray(config.mappings)) {
-    config.mappings.forEach(mapping => {
-      const localPath = path.resolve(mapping.local);
-      volumes.push(`${localPath}:${mapping.container}`);
-    });
-  }
+  // Build volumes array with base WordPress volume
+  const customVolumes = (config.mappings || []).map(mapping => {
+    const localPath = path.resolve(mapping.local);
+    return `${localPath}:${mapping.container}`;
+  });
+
+  const volumes = [`${wpVolumeName}:/var/www/html`, ...customVolumes];
 
   return {
     image: config.image,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bostonuniversity/buwp-local",
-  "version": "0.6.1",
+  "version": "0.6.2",
   "description": "Local WordPress development environment for Boston University projects",
   "type": "module",
   "main": "lib/index.js",