site cache and load balancing

Quote from: opengeek at Oct 05, 2011, 08:46 AM

Be aware that there are still some outstanding issues with using cache_db in all releases of MODX Revo so far.

Thanks for the heads up! I'll disable the db_cache.

Do you think there will be a big leap when 2.2 comes out in terms of upgrading from 2.1.3?
At the moment I am setting up a shared core (with a view to adding multiple manager installs).
Also how do you update multiple modx installs that have a shared core, given that I wont be able to run the setup on the various envirnments, just on our test enviornment.

Quote from: jusmeig at Oct 05, 2011, 09:27 AM

Do you think there will be a big leap when 2.2 comes out in terms of upgrading from 2.1.3?

Shouldn't be, though there will certainly be some differences, like how the Files tree and MODX Browser work with files (introduction of Media Sources).

Quote from: jusmeig at Oct 05, 2011, 09:27 AM

At the moment I am setting up a shared core (with a view to adding multiple manager installs).
Also how do you update multiple modx installs that have a shared core, given that I wont be able to run the setup on the various envirnments, just on our test enviornment.

You have to update each configuration by uploading setup to all the appropriate places. Also be aware that all configurations will share the packages and components directory as there is not yet support for multiple workspaces in MODX. This means you will have to update the packages on each configuration as well and be careful not to use different versions of the same component on different configurations. Once we do support multiple workspaces and simultaneous multi-configuration core upgrades, these kind of shared core scenarios will be much more practical.

thanks man,
To be honest I dont expect to update the componenets very often.

TinyMCE ticks the box for about 90% of our needs, anything else will be CMPs, plugins and snippets on a per project basis.

Only fully get this now....but this is excellent shite...
The Registry DB approach is excellent, and yet so simple and powerful.
Going to try implement the plugins you have listed here, thanks for posting.

Example from here: http://rtfm.modx.com/display/revolution20/modRegistry#modRegistry-RegisteringLoadBalancedWebNodesforRemoteCommands

Appears to be working.
When the RemoteCommands plugin runs:
one line gets put into modx_register_messages with the ip of the instance.

However when SendClearCache plugin runs:
Nothing happens really! What is the expect action of this.
Does the code need tweaking or should it work straight from the above?

SendClearCache should register a message to "clearcache" for each IP that is registered by RemoteCommands. RemoteCommands will look for these messages targeted to the current IP and execute them (i.e. clearcache).

Quote from: opengeek at Dec 01, 2011, 10:40 AM

SendClearCache should register a message to "clearcache" for each IP that is registered by RemoteCommands. RemoteCommands will look for these messages targeted to the current IP and execute them (i.e. clearcache).

Got this working (I think)
Found this on git, one you did recently it seems:
https://gist.github.com/1261818

This code worked fine.
I could verify the messages getting set correctly, and the regiter plugin picked up the message, and ran the refresh.

One question. Is the clearcache plugin on run when I choose:
Site -> Clear cache

Or is it run each time a resource is saved etc?

Quote from: jusmeig at Dec 01, 2011, 10:47 AM

One question. Is the clearcache plugin on run when I choose:
Site -> Clear cache

Or is it run each time a resource is saved etc?

It is only written/registered to run when choosing Site -> Clear Cache, but could easily be modified to attach to other events and trigger remote cache clearing when saving Resources, Elements or any other action in the manager.

No this is actually how I want it to run, only when the user clears the cache via Site.
Have yet to test on production...but one step closer now
Thanks for help.