Memcache
Permalink
Is there a way to configure 5.7.x to use memcached as the caching backend? I'm trying to configure Concrete5 to run on Google AppEngine, and the only references I can find are for the 5.6 version of Concrete, which doesn't help too much, as the configuration is quite different now. When I start the app, it creates a Memcached folder in the root application folder. This is not writable at runtime on GAE.
You can see herehttps://github.com/concrete5/concrete5/blob/5.7.x/web/concrete/src/S... the session factory only check if the handler is set to database or not.
When it's other than database, it takes the, which only supports files as it seems....
It's a pretty big step back in my opinion.
When it's other than database, it takes the
NativeFileSessionHandler
It's a pretty big step back in my opinion.
I am having massive issues with new host. They use memcached and the sessions aren't working. Nightmare as i have just moved 21 sites to them.
see:
https://www.concrete5.org/community/forums/customizing_c5/access-den...
see:
https://www.concrete5.org/community/forums/customizing_c5/access-den...
I have seen this across more and more hosts now. So my default option is to change to using database sessions. (see above)
I originally reported it was slower, but further testing has shown minimal performance load.
Good luck!
I originally reported it was slower, but further testing has shown minimal performance load.
Good luck!
This might help you out. https://github.com/hissy/scaling-concrete5...
Found this from a very useful community resource page that just got posted.http://documentation.concrete5.org/developers/appendix/community-pr...
Found this from a very useful community resource page that just got posted.http://documentation.concrete5.org/developers/appendix/community-pr...
i think this is when you are using a memcache server that is different form your own server, but i could be wrong.
I am having the same issue. I have just upgraded our hosting to a cluster and it now breaks with the error:
It turns out they use memcache. So the file sessions don't work.
I have found a dirty workaround that changes the sessions to work via the database, but it is very slow for me.
1. Create a file /application/config/concrete.php (if it doesn't exist).
2. Add this:
Changing it to memcache or memcached doesn't appear to work.
Anyone with any advice on getting it to work with memcache?
K