https://redmine.gc.cuny.edu/https://redmine.gc.cuny.edu/favicon.ico2016-07-25T19:00:07ZCUNY Graduate Center - Project Tracking SystemCUNY Academic Commons - Bug #5836: Memcached caching strategy on new serverhttps://redmine.gc.cuny.edu/issues/5836?journal_id=245122016-07-25T19:00:07ZBoone Gorgesboone@gorg.es
<ul></ul><p>Thanks, Ray. The same thing had occurred to me, but I didn't open a ticket for it.</p>
<p>Using the DB_NAME as a cache key salt sounds like a good and easy strategy for us. On our current setup, it's not possible that two sites with the same DB_NAME will be sharing the same Memcached space. I don't know that an infix like ':dev:' is necessary for this purpose, but I'm happy to be convinced otherwise.</p>
<p>You want to go ahead and make the change? This is probably something that can go in our version-controlled wp-config.php file.</p> CUNY Academic Commons - Bug #5836: Memcached caching strategy on new serverhttps://redmine.gc.cuny.edu/issues/5836?journal_id=245242016-07-26T16:10:45ZRaymond Hoh
<ul></ul><blockquote>
<p>I don't know that an infix like ':dev:' is necessary for this purpose, but I'm happy to be convinced otherwise.</p>
</blockquote>
<p>My reason for adding this is if we decide to enable Memcached on the dev server (<code>/DEV_WWW/html/commons/www/</code>) as well.</p>
<p>Are we going to try and emulate the production environment on the dev server? If we're not going to enable Memcached there, then we do not need to add the <code>:dev:</code> / <code>:prod:</code> suffix.</p> CUNY Academic Commons - Bug #5836: Memcached caching strategy on new serverhttps://redmine.gc.cuny.edu/issues/5836?journal_id=245252016-07-26T16:55:51ZBoone Gorgesboone@gorg.es
<ul><li><strong>Assignee</strong> changed from <i>Boone Gorges</i> to <i>Raymond Hoh</i></li></ul><blockquote>
<p>My reason for adding this is if we decide to enable Memcached on the dev server (/DEV_WWW/html/commons/www/) as well.</p>
</blockquote>
<p>Gotcha. This makes sense. Yes, we are going to use Memcached on LDV1, but it'll be using memory space on LDV1 - there will be no interaction with the production Memcached server.</p>
<p>However, you're right that it'd be best practice, moving forward, to use a salt that includes something about the environment type. We already have an ENV_TYPE constant that I use to display the little red flag on non-production sites. What do you think about using a sanitized version of that? That way it'll be one less thing to remember to change if switching between environments.</p> CUNY Academic Commons - Bug #5836: Memcached caching strategy on new serverhttps://redmine.gc.cuny.edu/issues/5836?journal_id=245262016-07-26T17:14:05ZRaymond Hoh
<ul></ul><blockquote>
<p>What do you think about using a sanitized version of that? That way it'll be one less thing to remember to change if switching between environments.</p>
</blockquote>
<p>Done. Let me know what you think of <a href="https://github.com/cuny-academic-commons/cac/commit/4572759d98882a17bb345f146e534d36307d9c00" class="external">commit 4572759</a>.</p> CUNY Academic Commons - Bug #5836: Memcached caching strategy on new serverhttps://redmine.gc.cuny.edu/issues/5836?journal_id=245282016-07-26T17:45:15ZBoone Gorgesboone@gorg.es
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>Perfect. Thanks, Ray!</p>