![]()
But a good tool should separate configuration from application source code. So such kind of configuration was not really intended. #Bitnami redmine slow when creating editing issues update#You will be recommended to edit Redmine's sources! That is very dangerous as next update will overwrite your configuration. In Trac there is only one such file you need to look at: trac.ini.Ĭonfiguration is broken: E.g consider creating custom routes in Redmine, that show the start wiki page and not the project overview as first page. Last but not least, whenever I administer a Trac project I love to edit PLAIN-TEXT configuration files. See below, there is an extra paragraph on multiple project support. Additionally, often it is stated that Redmine supports multiple projects, so its easier to setup a new project and configuration is not duplicated. I don't feel good with this but at least it works.Īdministration is not easy, considering making a backup: In Trac this is a one-liner, in Redmine, you have to backup: configuration, attached files and database content all separately. Some people suggest RVM providing virtual ruby environments, where you can have multiple Rails versions installed next to each other, which is not possible with apt-get. But what I hate most about those software package management systems beside the systems package-management is, that you have to care for updates and all other stuff separately. However, this was as easy as described on the homepage. #Bitnami redmine slow when creating editing issues install#I advise you to install via gem and bundler. #Bitnami redmine slow when creating editing issues upgrade#This is the reason that you must configure your apt-get or aptitude not to upgrade certain dependencies. Redmine's dependencies are fixed, so new library versions might not work.Of course fixes in Debian stable is done, the package versions are so outdated in stable, that newer versions of Redmine will not work. Debian had 5 security holes at the beginning of 2013 (January), where some still unfixed in unstable and testing.As configuration is not separated from application code, whenever you get package updates, they will overwrite your changes.You cannot use Debian/Ubuntu package system for production use But Redmine has some serious drawbacks over Trac: Latest versions I used in production were: Trac 1.0.1 and Redmine 2.2.3. I've used Trac a long time over 7 years by now. there shouldn't be hundreds of plugins to be installed before getting a usable project management software up and running (base installation should have most features).installation should be as easy as possible.wiki / internal blog (i.e., knowledge management).Right now, I cannot find any up-to-date or reliable comparison between both systems and thus cannot wage which one is better (maybe both are equally good).ĭoes anyone of you have recent experience in one or even both of these systems and can point out some (big) advantages/disadavantages of either Redmine or Trac (or even both)? Moreover, I read in some earlier posts from 20 that many projects had switched to Redmine. Originally, we planned for using TRAC but then I got aware of REDMINE. I'm working in research and my bioinformatics work group needs a project management software for keeping track of multiple projects (Linux environment). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |