beenull
/
b1gMail
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Run your own email service. For you, your organization — or for everyone.
113 Commits 1 Branch 8 Tags 11 MiB
PHP 55.4%
Smarty 21.4%
JavaScript 11.5%
CSS 8%
HTML 3.7%
Go to file
Sebijk dfb82c6ef1 fix undefined array key strike 2023-11-03 08:29:05 +01:00
.github/ISSUE_TEMPLATE Update issue templates 2022-02-12 00:05:57 +01:00
dev-docker create a docker template for development 2023-10-14 14:24:25 +02:00
servertest initial import 2022-02-06 14:27:29 +01:00
src fix undefined array key strike 2023-11-03 08:29:05 +01:00
tools switch to json instead serialize + base64 2023-10-14 14:19:41 +02:00
.gitignore add gitignore 2022-02-06 14:30:32 +01:00
AUTHORS initial import 2022-02-06 14:27:29 +01:00
LICENSE initial import 2022-02-06 14:27:29 +01:00
README.md create a docker template for development 2023-10-14 14:24:25 +02:00

README.md


b1gMail 7.4 OpenSource version


Email for your website, Modern user interface, Easy to administrate


About b1gMail

A big thanks goes to b1gMail founder Patrick Schlangen. He released b1gMail as freeware back then and since version 6 it was commercial. With version 7.4.1 the license is changed to GPL and all proprietary components were removed.

Getting started

It is recommended to install the b1gMail developer copy on a local web server, e.g. standard Apache/PHP/MySQL on Linux or Wamp on Windows. Even better results on Windows can be achieved with a WSL setup. If you use Docker, you can also use our docker template in docker-dev.

In order to install a development environment, proceed as follows:

  1. Clone the repository
  2. Go to src/serverlib/ and copy config.default.inc.php to config.inc.php and copy version.default.inc.php to version.inc.php.
  3. Remove the file lock in src/setup/
  4. Open the folder src in your web browser, e.g. http://localhost/b1gMail/src/
  5. Follow the setup instructs

Staying up to date

When pulling new changes from the server, you will need to update your database structure in case it changed. In order to do so, you can use the tools/db_sync.php script or log in to the ACP of your b1gMail development copy, go to "Tools" -> "Optimize" and chose "Check structure". Let the ACP fix any issues it found.

Contributing

You want to contribute to the b1gMail code? Great! In order to do so, it's probably the best idea to fork the b1gMail repository here and start creating your own commits. As soon as you feel the commit is mature and you would like to integrate it into the b1gMail code base, create a merge request to the main repository and we will review it.

Basic guidelines for commits

  • Adhere to the b1gMail coding style
  • If your commit requires database structure changes, include the updated database structure in the commit (you can export it using the tools/db_struct.php tool)
  • If your commit requires other DB changes (i.e. change values), include update code in the update script (it should be executed when updating to the next major version)

Migrating from the commercial to the GPL version

look at b1gMail Wiki.

Installation

look at b1gMail Wiki.