So it could easily be shared and updated when needed. This was a rather easy step, just listing the plugins that are still necessary, then finding their last stable version (if-any) that are compatible with Redmine 2.6.Īs this Redmine might not be the only one we have to deploy I decided to group the plugins we use in a Github repository Yay, a working Redmine stack! The plugins Sudo /opt/bitnami/ctlscript.sh restart apache Sudo /opt/bitnami/apps/redmine/bnconfig -disable_banner 1 Let’s do itĪll the following assume you are using a bitnami stack deployed under: So new OS, new Version, Update plugins, Missing plugins, new plugins… hopefully we did not change the Database too. Ubuntu 12.04 Running VirtualBox and DockerĪlso, quite a few plugins where added from the beginning, not all still in use so some plugins would have to be removed as well.Our Redmine instance running quite a few plugins, upgrading to Redmine 3.0 wasn’t an option for compatibility issue, Now having a racked-server in our building data-center running VMs and docker apps, that was definitely our new host. Redmine 2.5 (Stack was installed from the Bitnami native installer).Windows Server 2008 R2 (The version does not actually matter). Our Redmine server was firstly set-up on an available Windows Computer, and kept evolving from there. On this week nice adventure, I decided to have a clean, up-to-date instance of Redmine that would better fit in the current company infrastructure. Of the company that falls into my current responsibilities and to ensure the knowledge can be transferred properly. Some of the upcoming changes for me at work pushed to review all processes and infrastructure
0 Comments
Leave a Reply. |