Jens Krämer wrote this nice guide to deploying and maintaining Redmine the right way. This is basically a combination of the official Redmine documentation with a variety of guides on deploying and running a generic Ruby on Rails application. The solution is rightfully focusing on git, combining the upstream patches with your own changes. And given that this is “the right way”, you don’t even have to have any of your own changes. Just being prepared for some is good.
Once you’ve setup the proper environment, you can further automate the deployment of Redmine with Capistrano. If you don’t use Capistrano for whatever reason – no worries, the process is easily adoptable to whatever build/deploy tool you are using.
We use Redmine for our project management needs in the office. It works pretty well, but there are, as with anything, a few rough corners. One thing in particular that I was trying to figure out is how to use tables in Wiki pages, issues, etc.
The official documentation says that tables are not supported and you need to use HTML. Yuck. I do, of course, know how to mark up tables in HTML, but that’s definitely not the most pleasant of experiences. Especially if you need to modify them later. So I dug deeper.
It turns out that the documentation is outdated. Modern Redmine versions (we are on 3.3.0) use the redcarpet library for parsing Markdown, which supports tables just fine. Here is an example of the Markdown that you can use in pretty much any textarea field:
| Header 1 | Header 2 |
| --- | --- |
| Row 1 Cell 1 | Row 1 Cell 2 |
| Row 2 Cell 1 | Row 2 Cell 2 |
And it’ll render as a table just fine. The dashed line separating headers should have at least 3 dashes for the parser to understand it correctly. But you can extend the dashes for the whole width of the column.
It’s been a while since I posted an update on our infrastructure tools, so here goes one. (I know, ideally, it should be on our company’s blog, but we haven’t finished that part of the site yet).
Continue reading “Infrastructure update : GitHub, BitBucket, HipChat, TeamworkPM and Redmine”
CandyCane – Redmine ticketing system port to CakePHP
I just patched up my first Ruby application (Redmine). Made it do what I wanted, but didn’t enjoy any of it.
When configuring Redmine project management to send email notifications, using Exim MTA, you might end up with test emails bouncing due to no recipients specified. It’s a bit tricky to debug, but, fortunately, quite easy to fix. The problem comes from different implementations of “-t” option handling for /usr/sbin/sendmail. Redmine uses this option to specify on the command line to specify message recipients However, Exim by default uses a different behavior, where it gets recipients from the message headers, and removes from that list recipients which are provided using the “-t” command line option.
The solution to the problem is a very simple – just add the following line to your /etc/exim/exim.conf file, as per this FAQ:
extract_addresses_remove_arguments = false