You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current implementation uses wordpress:latest docker image, which uses Apache web server internally. So, we have the following request flow:
user browser -> nginx -> apache -> php -> wordpress
it would be nice to get rid of Apache web server. Probably, we may reuse nginx, which we have because of nginx-proxy-companion. In that case we will have the following flow:
user browser -> nginx -> php fpm -> wordpress
This change reduces needed computational resources.
This discussion was converted from issue #52 on August 05, 2021 11:51.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
Current implementation uses
wordpress:latest
docker image, which uses Apache web server internally. So, we have the following request flow:it would be nice to get rid of Apache web server. Probably, we may reuse
nginx
, which we have because ofnginx-proxy-companion
. In that case we will have the following flow:This change reduces needed computational resources.
Beta Was this translation helpful? Give feedback.
All reactions