Also make sure appropriate indexes are defined.
For reference, here are my settings from production.ini:
activitystream.master = mongodb://10.58.1.24:27017
activitystream.database = activitystream
activitystream.activity_collection = activities
activitystream.node_collection = nodes
activitystream.enabled = true
activitystream.recording.enabled = true
setup.py has the Ming storage driver installed by default. To fall back to the default (pymongo), comment out these lines in Allura/setup.py:
driver = activitystream.storage.mingstorage:MingStorage
To do functional testing, create a new project and some new users. For now, the home page of the project and users is still their activity page. Trying making at least one of the users watch a project and follow another user. "Do stuff" on the project(s) or with the users to make activities (comments, new artifacts, etc), then confirm that the activities show up on the appropriate timelines. To recap the logic:
You can switch back and forth between pymongo and ming at will (needs setup.py develop). I ran all the Allura tests using both.
Fixed tests to handle Ming not being available, as well as setup.py missing the activitystream.storage package, merged, and now waiting on pythontree to be updated.