DB volumes persists after bring down demo project.

[MohanNarayana]

Issue Description

Create a demo and bring it down using docker-compose down. It retains the volumes. The next demo that is created still points to the previous data volumes and gives misleading messages while creating user and shop.

Steps to Reproduce

1. Create a new demo from scratch using reaction create-project demo demo1. Create a user with username [email protected] and a shop.
2. Next cd demo1, docker-compose down and check for volumes using docker volume ls, you will find demo1_mongo-db4demo
3. cd .. and create a new demo using reaction create-project demo demo2. Create the same user with username [email protected], it gives a user exists error from GraphQL. Try creating a different user, it prompts for new shop creation. When you click create shop it gives an Access denied error from GraphQL.

Possible Solution

Two different demos should be working independently as we are currently not imposing any limits on demo. Following dev platform we could limit it to one demo per installation.

[MohanNarayana]

The issue is not with creating a secondary demo. It is with recreating another demo with the same name after bringing it down. The DB volume will persists even after bringing the demo down and deleting the demo directory. Creating a new demo with the same name will use the previously created DB volume. This behavior is fine but the user should be let know to remove the docker volume if they want a demo from scratch (without old data).