Skip to content

Commit

Permalink
added developer warning to vagrant & docker install
Browse files Browse the repository at this point in the history
  • Loading branch information
André Bauer committed Nov 17, 2016
1 parent 871e21d commit 1f93c76
Show file tree
Hide file tree
Showing 2 changed files with 25 additions and 0 deletions.
2 changes: 2 additions & 0 deletions contributing-install-docker.rst
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,8 @@ Install with Docker

Docker is a container-based software framework for automating deployment of applications. Our Docker image is a **single container** based application designed to have Zammad **up and running fast for testing proposes**.

Be aware that Vagrant is meaned for developers and therefore uses our unstable packages from the "develop" branch on GitHub.

Your Docker environment needs to be up and running.

You can find the image at https://hub.docker.com/r/zammad/zammad/
Expand Down
23 changes: 23 additions & 0 deletions contributing-install-vagrant.rst
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,8 @@ Install with Vagrant

Vagrant is a tool for building complete development environments. With an easy-to-use workflow and focus on automation, Vagrant lowers development environment setup time, increases development/production parity, and makes the "works on my machine" excuse a relic of the past.

Be aware that Vagrant is meaned for developers and therefore uses our unstable packages from the "develop" branch on GitHub.

Let’s begin using Vagrant!
First be sure that a Vagrant provider is installed. You can use "Virtual Box" from https://www.virtualbox.org .

Expand Down Expand Up @@ -38,3 +40,24 @@ After "vagrant up"
::

vagrant ssh


Problems to start the VM?
=========================

Iy you get errors like:

::

A VirtualBox machine with the name 'Zammad' already exists.
Please use another name or delete the machine with the existing
name, and try again.


Use the following commands to fix it:

::

vboxmanage controlvm Zammad poweroff
vboxmanage unregistervm Zammad

0 comments on commit 1f93c76

Please sign in to comment.