-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider deployment alternatives for Alpaca #731
Comments
Doesn't API-X need |
Yeah, that's the main monkey wrench we need to find a solution for. It would probably require a coordinated effort with API-X. |
On second thought, I guess that would only be an issue if API-X changed out of karaf, too. Otherwise we could still provide that as a bundle. |
The thing is sharing the authN info. |
Living with Karaf for now |
For the sake of ISLE 8, I've investigated dropping Karaf and running our camel routes as Spring Boot apps. FWIW, works pretty well! We could just run all our routes as fat jars and just be done with Karaf if we want. 💨 |
This remains highly relevant due to the changes in Jena with Alpaca. We are going to be forced to do this sooner or later. |
See relevant slack discussion: https://islandora.slack.com/archives/CLL691ESC/p1632509255032900 |
Deploying Alpaca and API-X in the same Karaf container is proving problematic: fcrepo4-labs/fcrepo-api-x#149. I'm interested in investigating alternatives like Spring Boot or plain ol' Felix to create fat jars for each package in Alpaca. The translation should be pretty straightforward. It's more of changes to the XML files and build procedures more than anything else.
The text was updated successfully, but these errors were encountered: