- **status**: review --> in-progress - **Reviewer**: Dave Brondsema - **Comment**:
Do we need all the language stuff? I don't think we really use it, and it's a lot of files, 196K. Other unnecessary stuff like currency and fields like admin_subscribed etc might be nice to clean up if we wanted. But we don't need to worry about make it as minimal as possible either, just seemed like lang files were quite a lot to add. docker-compose says: > Warning: the mapping "solr_config/allura:/opt/solr/server/solr/allura" in the > volumes config for service "solr" is ambiguous. In a future version of > Docker, it will designate a "named" volume (see > https://github.com/docker/docker/pull/14242). To prevent unexpected > behaviour, change it to "./solr_config/allura:/opt/solr/server/solr/allura" The "Mention chmod in the docs" commit can probably be changed to go into the fairly new `init-docker-dev.sh` --- ** [tickets:#7907] Use standardized solr installation** **Status:** in-progress **Milestone:** unreleased **Labels:** sf-4 sf-current 42cc **Created:** Mon Jun 29, 2015 03:25 PM UTC by Dave Brondsema **Last Updated:** Fri Dec 04, 2015 03:39 PM UTC **Owner:** Igor Bondarenko We have a hacky setup for solr (both step-by-step and docker install): * we wget solr, instead of using a system package * we copy our schema into the solr example dir * we run `start.jar` directly instead of a service For docker, we should be able to use a solr image that somebody else has set up. For the step-by-step we should use system packages and perhaps borrow ideas from the solr container's Dockerfile. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
