Multiple Web Servers

[siddharth]

Hi All,

Those have done multiple web servers setup, can you please answer the below.

1) What are the folders that needs to be shared among all web servers
2) You are storing session via Redis or files, if so what is the variable used for Redis in settings.php

 

[Rodolfo]

With V3.20 you don't need to mount drives to scale the application.

• Use external storage for user uploads (n servers)
• Use external asset storage for avatar/logo/backgrounds
• Use CDN for website assets js/css
• Use redis for sessions

By following that there's no filesystem mounting required, at all.

2) You are storing session via Redis

tcp://etc for save path, redis for save handler.

 

[siddharth]

Use external storage for user uploads (n servers)

This is done

• Use external asset storage for avatar/logo/backgrounds

I believe you are referring to AWS S3, is there any other solution for this?

Use CDN for website assets js/css

This can be done

• Use redis for sessions

Got it

 

[siddharth]

I tried editing the settings.php files with these variable

For checking Redis

'session.save_handler' => 'redis',
'session.save_path' => 'tcp://IP:6379',

For checking custom files folder

'session.save_handler' => 'files',
'session.save_path' => '/xxxx',

When I add these variables to settings.php , site is giving out HTTP error 500.

Can someone advise where those variables need to be added?

Error in the Log: "PHP message: PHP Parse error: syntax error, unexpected '=>' (T_DOUBLE_ARROW), expecting ']'

 

[siddharth]

Update: Able to make the Session worked via both Files and Redis method. You have to edit the main php.ini file, but looking for some document to get it worked via settings.php or at the application level. It will be better if it is added in the Chevereto admin area to enter the Redis Server IP, Redis Database number to be used, and Port.

 

[Rodolfo]

It will be better if it is added in the Chevereto admin area to enter the Redis Server IP, Redis Database number to be used, and Port.

Chevereto uses enviroment variables, which is way more optimal. Something like the session handler can't be configured at dashboard level, because it is user layer and it relies in the session system.