I'm using the blacklabelops/crowd Docker image as a baseline and auto-generating the crowd.cfg.xml file in the ENTRYPOINT script for my image so it contains our server ID, license, and database settings.
I'm having trouble figuring out how to initialize the database though -- when Crowd starts up, it doesn't create the schema, instead generating errors in the DB logs because the requested tables don't exist.
Is there a way to specify all relevant parameters at startup so Crowd will initialize if settings don't exist and use existing settings if the database is found? Or do I have to run a bootstrap container and manually configure Crowd before I can launch my runtime containers for an HA solution?
Hi @Gordon Shankman,
Indeed there is no headless setup for Crowd at the moment. However, the approach you've taken with generating crowd.cfg.xml, looks like a way to go.
In order to overcome the problem with empty database, I would suggest doing a backup and then reapplying it on a fresh DB before Crowd is started. It can be a DB dump from a previous startup as Crowd will automatically upgrade DB schema and data to a version you currently run.
You've mentioned HA solution you are building with docker containers. I guess it is more disaster recovery mode then active-active clustering?
Did you tried our Crowd Data Center for HA capabilities in Active - Active cluster mode?
Hope that helps,
Do you own more than one Server or Data Center product? Do you have challenges provisioning users across your Atlassian products? Are you spending a lot of time integrating each Atlassian product wit...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs