search

mailcow / mailcow-dockerized

mailcow: dockerized - 🐮 + 🐋 = 💕
https://mailcow.email
GNU General Public License v3.0
8.52k stars 1.14k forks source link

Dev environment instructions #5081

Open felixoi opened 1 year ago

felixoi commented 1 year ago

Summary

I started my first PR (#4968) and wrote the code on a Hetzner VM testing with real domains, IPs etc.. What's the best way to make changes/test the changes for mailcow in development? Is there a working 100% local setup? I cannot find any instructions on that topic in this repo and it's much needed IMO.

Motivation

All contributors would benefit and it would lower the contribution barrier.

Additional context

No response

felixoi commented 1 year ago

No one of the team has a comment on this? I'd really like to finish #4968.

MAGICCC commented 1 year ago

I use a dedicated VM to test things

FreddleSpl0it commented 1 year ago

If you require a fully functional mailcow, it is recommended to deploy a mailcow specifically for development purposes. This is the approach we follow. Everyone has their own mailcow just for development.

However, if I work on the UI for example, a locally deployed mailcow is sufficient for my needs.