TL;DR: Eine Neuinstallation geht in der Regel einfacher. Falls man es trotzdem probieren will, dann sollte man an ein Backup denken und einigermaßen wissen, wie man mit Dependency-Problemen bei der Paketinstallation umzugehen hat.
Der Anfang ist wie üblich:
You can configure Redmine to use an LDAP or Active Directory server as login backend. Whenever a new user has been successfully authenticated against this service, a new entry in the Redmine's user table is created.
A side effect of this is that you can't work with users that have not logged in into your instance, yet.
To solve this I've created a small python script that can be used to periodically synchronize the users table with your directory services:
This article might not longer be relevant as a new opensource client called "openfortivpn" exists that utilized the SSLVPN feature of Fortigate instead of IPSec. See my new article Connecto to Fortigate VPN with OpenfortiVPN.
This article might be relevant to you if you have problems connecting to a FortiGate IPSec VPN with Linux (vpnc). For example, when using NetworkManager, you might see something like this in syslog:
Use "tee" as editor:
$ (echo "Daily autocommit. Stats:"; hg diff | diffstat) | hg commit --config ui.editor=tee
Daily autocommit. Stats:
b/bar | 1 +
foo | 1 +
2 files changed, 2 insertions(+)
With bash and printf: