- simpler to use
- lighter dependency (or no dependency at all, depending on python distribution)
- retrocompatible
virtualenv package from pip to acheive virtual environment feature is no longer
needed, except for projects which need to support py2, which is no longer our
case.
Also, reword "virtualenv" to "virtual environment" in doc, to avoid confusion
with pip package name.
Ref #483
* Reorganize "Contributing" documentation to be more accessible to new contributors
The following changes were done:
- move "How to contribute" first, and "Set up a dev environment" as the
second section. This way, a new contributor has access to the most
general information first, instead of the very specific "dev
environment" documentation.
- reduce "How to contribute" / "As a developer" by moving the part about
tests to a new "Contributing as a developer" section (see below). This
way, all types of contributions get roughly the same amount of text in
the first "How to contribute" section.
- add a new "Contributing as a developer" section, which lists items that
are useful when preparing a code contribution (running tests, formatting
code, create database migration). These items were moved either from
"How to contribute" or from "Set up a dev environment".
* Add brief documentation about updating and adding tests
Co-authored-by: Baptiste Jonglez <git@bitsofnetworks.org>
* Replace the settings table with multiple sections.
It's easier to read, and easier to maintain. Fixes#251.
* Document external mail server configuration.
Fixes#278
* Add a `make update-translations` command
To collect new strings to be translated from code.
Totally cheated on @Glandos commands :-)
Ref #336
Ref https://github.com/spiral-project/ihatemoney/issues/336#issue-322069517
* Document translation process
Fix#336
* Drop noisy location comments from .po files
Fix#339
* Drop .pot header
As it serves no purpose with our translation workflow.
.po header could be removed also, but pybabel has no option for that.
Ref #339
PyMySQL is more difficult to install since its version 0.9 since it now depends
on *cryptography* lib, which in turns depends on OpenSSL and Python dev files.
See https://github.com/PyMySQL/PyMySQL/issues/697
- Use exec to run gunicorn and avoid creating a new process.
- Add the possibility to pass any additional parameters to
gunicorn.
- Use only one gunicorn worker by default as the usual way to
scale the app in production would be to use the scale command
of the cluster scheduler. Additional workers could still be
added by passing the "-w" gunicorn parameter to docker run.
