You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
For upgrading a Crowd installation I'd like to install the new version in parallel to the old one.
Then I'd create a remote Crowd directory in the new Crowd that connects to the old Crowd.
With this setup I could switch over my applications one after another to the new Crowd without having to shut them down all at once.
When the last application is using the new Crowd I'd like to cut the connection to the old one and turn the remote directory into a standalone internal one.
Is this possible?
The answer below is totally unsupported and you could potentially lose your data.
But if you really wanted to try it, you could just open up your database and look at the "cwd_directory" table. Find the row that you want to edit and change impl_class to: com.atlassian.crowd.directory.InternalDirectory
and lower_impl_class to: com.atlassian.crowd.directory.internaldirectory
change the directory_type to: INTERNAL
This may work.
Again, please be aware of the risks before doing this.