Restored requirements and updated doc (#113)

* Restored requirements.txt

* Updated README with pipenv

README.md

@@ -18,18 +18,34 @@ microservices with Python which handles cross-cutting concerns:
 
 # How to run the scaffold
 
-## Instalation
+## Installation
+
+### Install with virtualenv
 ```bash
 virtualenv --python=python[3.6|3.7|3.8] venv
 source venv/bin/activate
 pip install -r requirements.txt
 ```
 
+### Install with pipenv
+```bash
+pip install pipenv
+pipenv install
+```
+
+#### Advantages over plain pip and requirements.txt
+[Pipenv](https://pipenv.readthedocs.io/en/latest/) generates two files: a `Pipfile`and a `Pipfile.lock`.
+* `Pipfile`: Is a high level declaration of the dependencies of your project. It can contain "dev" dependencies (usually test related stuff) and "standard" dependencies which are the ones you'll need for your project to function
+* `Pipfile.lock`: Is the "list" of all the dependencies your Pipfile has installed, along with their version and their hashes. This prevents two things: Conflicts between dependencies and installing a malicious module.
+
+For a more in-depth explanation please refer to  the [official documentation](https://pipenv.readthedocs.io/en/latest/).
+
 ## Run your python script
 ```bash
 python manage.py runserver
 ```
 
+
 ## Check the result
 
 Your default endpoints will be in this url:

requirements-tests.txt

@@ -0,0 +1,6 @@
+-r requirements.txt
+coveralls==1.10.0
+coverage==5.0.2
+nose==1.3.7
+pylint==2.4.4
+tox==3.14.3

requirements.txt

@@ -0,0 +1,6 @@
+Flask-SQLAlchemy==2.4.1
+SQLAlchemy==1.3.12
+Flask-Script==2.0.6
+py-ms==2.1.0
+marshmallow==3.3.0
+marshmallow-sqlalchemy==0.21.0