Book Image

Mastering Redmine - Second Edition

By : ANDRIY LESYUK
Book Image

Mastering Redmine - Second Edition

By: ANDRIY LESYUK

Overview of this book

Redmine is not only one of the popular open source project management applications but also one of the best project hosting and issue tracking solutions. This book is an update of our previous successful edition, Mastering Redmine. This book is a comprehensive guide that will give you a detailed practical understanding on how to effectively manage, monitor and administer complex projects using Redmine. You will get familiar with the concept of Issue Tracking and will get to know why and what makes Redmine one of the best issue trackers. Another main part of Redmine functionality, which is Managing projects shows why this is one of the best applications for project hosting. Furthermore, you will learn more about Redmine rich text formatting syntax, access control and workflow and time Tracking. Towards the end, you will unleash the power of custom fields and guides to show how to customize Redmine without breaking upgrade compatibility. By the end of the book, you will have a deep practical understanding on how to effectively monitor and manage large scale and complex projects using Redmine.
Table of Contents (19 chapters)
Mastering Redmine Second Edition
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Quick Syntax Reference
Index

Email integration


Redmine email integration can be considered to consist of two components: email delivery (notifications) and email retrieval.

Email delivery

Most likely, if you open the Email notifications tab on a recently installed Redmine, you will get the following message:

This message clearly states that you can't fix this issue through the web interface. First, we need to modify the mentioned configuration file and then we can get back here. So, it's time to open the console.

The configuration.yml file

In the config subdirectory of the Redmine root directory, you will find the configuration.yml.example file. Copy (or just rename) it to configuration.yml:

$ cp configuration.yml.example configuration.yml

Now, open this file in your favorite console editor.

As you can see, it is divided into three blocks: default, production, and development. The production and development blocks are for environment-specific configuration and the default block combines the configuration options of all environments...