Damp

Managing Projects

Manage, delete, and sync your DAMP projects

View, manage, and delete your PHP projects from DAMP's dashboard.

Project Dashboard

Project List

All your projects displayed as cards showing:

  • Project Name - Project identifier
  • Domain - HTTPS URL (e.g., myproject.local)
  • Status Indicator
    • 🟢 Running - DevContainer active
    • 🔴 Created - Not yet opened in VS Code
    • Stopped - DevContainer stopped

DAMP checks if your DevContainer is running in real-time. Green = accessible via browser.

Project Details

Click any project card to view full details and actions.

Project Actions

Open in VS Code

Launch directly into VS Code:

  1. Click "Open in VS Code" button
  2. VS Code opens the project
  3. Reopen in Container when prompted
  4. Start coding
This launches your project in VS Code without folder browsing.

Open Folder

Open the project folder in Windows Explorer:

  • View project files
  • Copy/paste files
  • Backup project manually

Browse Project

Visit the project in your default browser:

https://myproject.local

Project must be running in VS Code DevContainer to respond to browser requests.

Environment Variables

View connection information for services:

# Database (if MySQL installed)
DB_HOST=damp-mysql
DB_PORT=3306
DB_DATABASE=development
DB_USERNAME=developer
DB_PASSWORD=devpassword

# Redis (if installed)
REDIS_HOST=damp-redis
REDIS_PORT=6379

# Mail (if Mailpit installed)
MAIL_HOST=damp-mailpit
MAIL_PORT=1025

Copy to Clipboard - One click copies all environment variables!

Volume Sync

Named volumes provide fast performance but files live in the container. Sync copies them to your local machine.

Quick Action:

  • Sync From Volume - Copy container files to local folder

Options:

  • Exclude node_modules/ - Skip Node.js dependencies
  • Exclude vendor/ - Skip PHP dependencies

See the complete Volume Sync Guide for details on performance, sync timing, and troubleshooting.

Laravel Tools

Projects marked as Laravel get additional features:

Open Tinker

Launch Laravel's interactive REPL:

  1. Click "Open Tinker" button
  2. Terminal opens with Tinker running
  3. Test code interactively
>>> User::count()
=> 5

>>> $user = User::first()
>>> $user->name
=> "John Doe"

Learn more: Tinker Documentation

Ngrok Tunneling

Share your local project publicly:

Enable Tunnel

Open Tunnel Tab

Select a project → click "Tunnel" tab

Configure (Optional)

  • Choose region (us, eu, ap, etc.)
  • Set custom subdomain (requires paid Ngrok plan)

Start Tunnel

Click "Start Tunnel" - public URL created in seconds

Tunnel URL Example:

https://abc123.ngrok.io → https://myproject.local

Share the ngrok URL with clients, testers, or webhooks.

Learn more: Ngrok Tunneling

Deleting Projects

Safe Deletion

When you delete a project, DAMP:

  1. ✅ Stops the DevContainer (if running)
  2. ✅ Removes project from DAMP dashboard
  3. ✅ Removes domain from hosts file
  4. ✅ Removes SSL certificate
  5. ✅ Removes Caddy configuration
  6. Preserves project folder
  7. Preserves named volume

Your code and data are safe - only DAMP's tracking and configuration are removed.

Delete Process

Select Project

Click the project you want to remove

Click Delete

Click "Delete Project" button

Confirm

Confirm deletion in dialog

Done

Project removed from DAMP - folder and volume remain on disk

What Remains After Deletion

Your local filesystem still contains:

C:\Users\You\Projects\myproject\    ← Project folder intact

Docker volumes still exist:

docker volume ls
# Shows: myproject_data

Complete Removal

To fully remove everything:

# 1. Delete from DAMP (above steps)

# 2. Delete project folder
Remove-Item -Path "C:\Users\You\Projects\myproject" -Recurse -Force

# 3. Delete Docker volume
docker volume rm myproject_data

Bulk Operations

Refresh All Projects

Click "Refresh" button to:

  • Update all project statuses
  • Check DevContainer states
  • Refresh connection info

Search Projects

Use the search bar to filter projects by name or domain.


Keep projects organized with clear naming conventions like client-project or app-v2.

Troubleshooting


Next Steps

On this page