DevCamps make it easy to manage parallel development and production environments, and keep them in sync.

A camp is a complete snapshot of the production environment as of the instant the camp is created. Each camp has:

  • its own web server
  • its own application server
  • its own URL
  • and its own copy of the production database.

Each camp is insulated from changes to other camps. Production is completely isolated from the development and staging camps.

Should you accidentally delete crucial files, drop the database, mistakenly corrupt the webserver configuration, or simply introduce programming errors while in development or staging — no worries, it’s only a copy. This means you can experiment with the entire software environment in complete safety.

Camps leverage popular open source tools, such as Git for version control, and build upon them. The Camps software is freely available.

Things to know about Camps:

  • An index web page is provided to show all available camps at a glance.
  • Camps are accessible to all who need access, but protected from search engines and others.
  • Projects may have one or more camps.
  • Multiple camps are available for each developer.
  • Separate web server, database, and application servers are provided for every camp.
  • Staging sites are camps too.
  • Version control is often used to move code around, typically even when promoting to production.
  • Product owners can see and approve changes before they go live.
  • Clients can see your work in progress just as it will appear in production.

The Workflow

  1. Create one or more camps
  2. Work in your camp:
    1. Make changes
    2. Test and review
    3. Commit
    4. Get client approval (as needed) or make more changes.
  3. Push to repository
  4. Pull and test in staging camp
  5. Pull into production when desired

DevCamps Tutorial

To see DevCamps in action, visit our DevCamps Tutorial.

DevCamps FAQs

We also maintain our own list of FAQs that SpreeCamps customers have asked.