Migrate to pipenv for dependency management

Pipfile

@@ -0,0 +1,17 @@
+[[source]]
+name = "pypi"
+url = "https://pypi.org/simple"
+verify_ssl = true
+
+[dev-packages]
+pylint = "*"
+yapf = "*"
+
+[packages]
+bcrypt = "==3.1.6"
+flask-sqlalchemy = "==2.4.0"
+flask-cors = "==3.0.8"
+flask = "==1.0.3"
+
+[requires]
+python_version = "3.7"

README.md

@@ -17,19 +17,21 @@ Example config:
         // see https://docs.sqlalchemy.org/en/13/core/engines.html#database-urls
         "allow_signup": false, // whether to allow /api/signup or not
         "loglevel": 0, // 0: errors, 1: warnings, 2: info
-        "domain": "https://your.domain.tld" // full domain with HTTPS
-        // needed for CORS
+        "domain": "https://your.domain.tld" // full domain with HTTPS, needed for CORS
     }
 
 If there are environment variables `AMBER_DATABASE` / `AMBER_ALLOW_SIGNUP` /
-`AMBER_LOGLEVEL`, `AMBER_DOMAIN` set, the program will respect them and use
+`AMBER_LOGLEVEL` / `AMBER_DOMAIN` set, the program will respect them and use
 over the values provided with the config file.
 
 #### Dependencies
 
 This app directly depends on `flask`, `flask-sqlalchemy`, `flask-cors`, and
 `bcrypt`.
 
+`requirements.txt` is left only so that pipenv is not needed while building the
+app in Docker. Please use pipenv in development.
+
 #### Running in Docker
 
 The Dockerfile included with the project assumes that:
@@ -40,7 +42,10 @@ the app without a reverse proxy won't work because of the current uwsgi
 configuration).
 
 If you have to/prefer to use MariaDB, etc, you'll have to add the necessary
-Python packages to the Docker image by hand.
+Python packages to the Docker image by hand. See [SQLAlchemy docs][SAd] for
+details.
+
+[SAd]: https://docs.sqlalchemy.org/en/13/core/engines.html#database-urls
 
 #### Licenses