Confirmed users
9,511
edits
QA/Execution/Web Testing/SUMO/Tips and Pointers: Difference between revisions
QA/Execution/Web Testing/SUMO/Tips and Pointers (view source)
Revision as of 00:16, 23 April 2009
, 23 April 2009no edit summary
No edit summary |
|||
| Line 11: | Line 11: | ||
SUMO (prod and staging) caches JS/CSS via Citrix [http://citrix.com/English/ps2/products/product.asp?contentID=21679 NetScalers], [http://www.danga.com/memcached/ memcached], and [http://www.smarty.net/faq.php#5 Smarty] | SUMO (prod and staging) caches JS/CSS via Citrix [http://citrix.com/English/ps2/products/product.asp?contentID=21679 NetScalers], [http://www.danga.com/memcached/ memcached], and [http://www.smarty.net/faq.php#5 Smarty] | ||
* If you can't see a fix on staging, ask IT to check and see what its latest SVN revision # is. | * If you can't see a fix on staging, ask IT to check and see what its latest SVN revision # is. | ||
** During a rollout to production, if you don't see fixes applied to production, it might be a [http://stackoverflow.com/questions/119444/locking-binary-files-using-git-version-control-system stale git lock]; ask IT to clear it | ** During a rollout to production, if you don't see fixes applied to production, it might be a [http://stackoverflow.com/questions/119444/locking-binary-files-using-git-version-control-system stale git lock]; ask IT to clear it (though this should be fixed by Reed's Nagios script) | ||
==User account roles== | ==User account roles== | ||