- **status**: open --> closed - **Comment**: Docs at [forge-allura hosting setup]
--- ** [tickets:#8366] Move forge-allura self-hosting to new VM** **Status:** closed **Milestone:** unreleased **Labels:** asf **Created:** Mon Jun 15, 2020 12:38 AM UTC by Dave Brondsema **Last Updated:** Sun Jul 19, 2020 06:16 PM UTC **Owner:** nobody Very slow performance on our own self-hosting (this site) has occurred, often because of a process called "blocky.py" which I reported to Apache Infra at: https://issues.apache.org/jira/browse/INFRA-20414 and they also created https://issues.apache.org/jira/browse/INFRA-20427 They are recommending we upgrade to a new VM with new OS and config management which should fix it. The current VM `allura-vm2` setup notes are here: https://docs.google.com/document/d/1d0fiws7qVyjf-nfcqsIyFqzAsbUqm2yR66bJx6GtZKk/edit and https://issues.apache.org/jira/browse/INFRA-13262 --- 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.
