@bostonuniversity/buwp-local 0.5.1 → 0.5.2

package/lib/commands/keychain.js

@@ -174,6 +174,44 @@ async function setupCommand(options) {
   console.log(chalk.gray('You can override specific credentials per-project using .env.local files.\n'));
 }
 
+/**
+ * Prompt user to delete the source credentials file
+ * @param {string} filePath - Path to the file to delete
+ * @param {boolean} hasFailures - Whether some credentials failed to import
+ */
+async function promptToDeleteSourceFile(filePath, hasFailures = false) {
+  const fileExists = fs.existsSync(filePath);
+  if (!fileExists) {
+    return; // File already deleted or doesn't exist
+  }
+
+  console.log(chalk.yellow('🔐 Source Credentials File Security'));
+  console.log(chalk.gray(`   Location: ${filePath}`));
+  console.log(chalk.gray('   This file contains plaintext credentials and should be deleted.'));
+  console.log('');
+
+  const defaultDelete = !hasFailures; // Default to yes if all imported successfully
+  const { shouldDelete } = await prompts({
+    type: 'confirm',
+    name: 'shouldDelete',
+    message: 'Delete the source credentials file now?',
+    initial: defaultDelete
+  });
+
+  if (shouldDelete) {
+    try {
+      fs.unlinkSync(filePath);
+      console.log(chalk.green(`✓ Deleted: ${filePath}\n`));
+    } catch (err) {
+      console.log(chalk.red(`✗ Failed to delete file: ${err.message}`));
+      console.log(chalk.yellow(`⚠️  Please manually delete: ${filePath}\n`));
+    }
+  } else {
+    console.log(chalk.yellow(`⚠️  Remember to manually delete: ${filePath}`));
+    console.log(chalk.yellow('   This file contains plaintext credentials.\n'));
+  }
+}
+
 /**
  * Bulk import credentials from JSON file
  * @param {string} filePath - Path to credentials JSON file
@@ -289,6 +327,16 @@ async function bulkImportFromFile(filePath, force) {
   
   console.log(chalk.gray('These credentials will be used automatically by all buwp-local projects.'));
   console.log(chalk.gray('You can override specific credentials per-project using .env.local files.\n'));
+  
+  // Offer to delete the source file
+  if (failCount === 0) {
+    // All credentials imported successfully - safe to delete
+    await promptToDeleteSourceFile(filePath);
+  } else if (successCount > 0) {
+    // Some imported successfully - ask with a warning
+    console.log(chalk.yellow('⚠️  Not all credentials imported successfully.\n'));
+    await promptToDeleteSourceFile(filePath, true);
+  }
 }
 
 /**

package/lib/commands/start.js

@@ -81,6 +81,8 @@ async function startCommand(options) {
     const tempEnvFileFlag = tempEnvPath ? `--env-file ${tempEnvPath}` : '';
     
     try {
+      // 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`,
         { 

package/package.json

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

package/readme.md

@@ -1,6 +1,6 @@
 # BU WordPress Local Development
 
-This repository contains resources and instructions for setting up a local WordPress development environment for Boston University projects. It uses the BU WordPress container image and provides the additional resoures needed to run it locally with Docker.
+This repository contains resources and instructions for setting up a local WordPress development environment for Boston University projects. It uses the BU WordPress container image and provides the additional resources needed to run it locally with Docker.
 
 
 ## Quickstart for plugin or theme development
@@ -43,6 +43,10 @@ This repository contains resources and instructions for setting up a local WordP
 
     This will guide you through setting up your project name, hostname, port mappings, volume mappings, and service options.
 
+    If you choose plugin, theme, or mu-plugin project type, the setup will automatically add volume mappings for your current directory into the appropriate WordPress location in the container.
+
+    If you choose sandbox project type, you will need to manually add volume mappings to your `.buwp-local.json` file later, or you can run without any volume mappings.
+
 6. **Setup local hostname**: Add your project's local hostname (e.g. `myproject.local`) to your `/etc/hosts` file
 
 7. **Start your local environment**:
@@ -80,3 +84,11 @@ Your local WordPress site should now be accessible at the hostname you configure
     ```
 
     This will download the latest snapshot from the specified source and import it into your local WordPress environment.
+
+
+
+
+scp username@ist-wp-app-dv01.bu.edu:/etc/ist-apps/buwp-local-credentials.json ~/Downloads/
+
+
+scp jaydub@ist-wp-app-dv01.bu.edu:/etc/ist-apps/buwp-local-credentials.json ~/Downloads/