Hmm, since this ticket changes the default location of where the allura data lives, this could break existing deployments that choose to upgrade.
It would be nice to address this somehow, but I'm not sure how. These proposed changes are definitely a step above and required for a macos deployment, so we definitely want them, but we don't want to confuse/annoy loyal allura-ites. --- ** [tickets:#8399] Broken Docker Setup Guide and Config** **Status:** open **Milestone:** unreleased **Created:** Mon Oct 25, 2021 09:13 PM UTC by Dillon Walls **Last Updated:** Mon Oct 25, 2021 09:14 PM UTC **Owner:** nobody I tried following the [docker setup guide](https://forge-allura.apache.org/docs/getting_started/installation.html) on my macbook and almost immediately ran into trouble. There were a few things going on: - Docker changed how it works with virtualbox and docker-machine - macOS prevents even sudo from creating `/allura-data` - A recent upgrade of the `gunicorn` package to v20.x.x broke the `[server:main]` configs in our \*.ini files. I have created a branch which fixes these things and hopes to clarify a few points in the docs. dw/8399 --- 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.
