docker-mailserver
is OpenSource. That means that you can contribute on enhancements, bug fixing or improving the documentation in the Wiki.
When opening an issue, please provide details use case to let the community reproduce your problem.
Please start the mail server with env DMS_DEBUG=1
and paste the ouput into the issue.
├── config # User: personal configurations
├── target # Developer: default server configuration, used when building the image
└── test # Developer: integration tests to check that everything keeps working
You want to add a feature? Feel free to start creating an issue explaining what you want to do and how you're thinking doing it. Other users may have the same need and collaboration may lead to better results.
The development workflow is the following:
- Fork project and clone your fork
- Create a branch using
git checkout -b branch_name
(you can useissue-xxx
if fixing an existing issue) - Run
git submodule init
andgit submodule update
to get the BATS submodules - Code :-)
- Add integration tests in
test/tests.bats
- Use
make
to build image locally and run tests - Document your improvements in
README.md
or Wiki depending on content - Commit, push and make a pull-request
- Pull-request is automatically tested on Travis
- When tests are green, a review may be done
- When changed are validated, your branch is merged into
master
master
is automatically tested on Travis- Docker builds a new
latest
image