Cache directory in multi server environment

[Andreas Weidenhaupt]

Hello everyone,

we want to run IPBoard on a load-balanced multi server environment. We're having four web servers, each of them with an indentical installation of the IPBoard software. Uploads are shared between servers via NFS.

Now my question is: What about the cache directory? It seems like IPBoard is creating files for templates, language packs and some more in that directory. I'm worried that e.g. when we update a template in the ACP it will be only updated on a single server (the server I'm currently on) and the other 3 will keep an outdated cache file forever. What's the best practice to deal with the cache directory in a multi server environment?

Additional question: Is it possible to (re)build the cache from a console command? (The same as "Tools&Settings > Cache Management > Rebuild All" in ACP does)

Thanks in advance!

[Aiwa]

You can rebuild the skin cache via ACP > Look and Feel > Template Tools > Recache skinsets.

Languages from ACP > Look and Feel > Manage Languages > green arrows to the right of each language.

You would want to make sure your /cache directory is also updated between servers. You may also want to include /public/style_css, and public/style_images

[Andreas Weidenhaupt]

Thanks for your answer. Two more questions to make it clear:

You can rebuild the skin cache via ACP > Look and Feel > Template Tools > Recache skinsets.

Languages from ACP > Look and Feel > Manage Languages > green arrows to the right of each language.

There's no way to do it via console? Would be great if we could automate the cache initialization for our deployment script.

You would want to make sure your /cache directory is also updated between servers. You may also want to include /public/style_css, and public/style_images

So if we share the cache directory via NFS between servers, it will be fine? That doesn't create any problems with the forum software?

[Aiwa]

No, there isn't a CLI script unfortunately.

I've not used NFS in a webserver production instance, but if it works similar to rsync, then that wouldn't be a problem. As long as each server has access to the most up to date information, you're fine.

Maybe set up a CRON to ensure each servers cache is updated every day during off peak hours. If any changes are made during the day, you could manually run a re-sync.

[Andreas Weidenhaupt]

What a quick reply! Thanks for your help.