- **status**: in-progress --> review
- **Comment**:
https://sourceforge.net/p/activitystream/code/merge-requests/1/ and
allura:db/8015 Will require an activitystream release and increment in
requirements.txt
To test with allura, set `activitystream.ming.auto_ensure_indexes = false` in
the .ini file. Then check on what mongo operations happen with these commands:
~~~~
use activitystream;
// capture all operations
db.setProfilingLevel(2);
// run this before & after restarting the webserver and hitting an activity
page. Ensure count doesn't go up now.
db.system.profile.find({op: 'insert', ns:
'activitystream.system.indexes'}).count();
// return to normal
db.setProfilingLevel(1);
~~~~
---
** [tickets:#8015] Activitystream needs ming config option**
**Status:** review
**Milestone:** unreleased
**Labels:** sf-current activitystreams sf-2
**Created:** Mon Nov 02, 2015 03:13 PM UTC by Dave Brondsema
**Last Updated:** Thu Nov 12, 2015 05:56 PM UTC
**Owner:** Dave Brondsema
Allura uses the Activitystreams library and choses to use its Ming backend
(specified in `Allura/setup.py`). Ming's `auto_ensure_indexes` setting
defaults to true, but we should have a way to specify that as false for
Activitystream.
Ideally we'd be able to pass through any additional params, just like the
regular ming configuration that Allura uses for its own allura & project-data
connections.
---
Sent from forge-allura.apache.org because [email protected] 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.
