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
At this time, we copy to frontend node the static websites files, but that should change.
Idea is to follow conventions created in #115 where we have an internal web server listening only to private network and that frontend type servers proxies requests to.
So far we only had the homepage as a static site and it’s hosted on the same VM as MediaWiki.
Maybe its time we aggregate static sites into one "upstream" role like we would do with a dynamic site backend but to serve only static files.
Note Even though specs.webplatform.org are also static html pages, we’ll let a specialized upstream ("upstream-specs") handle them since we have publican who takes care of refreshing the pages. We should therefore not touch specs.webplatform.org/publican in this work item.
The text was updated successfully, but these errors were encountered:
At this time, we copy to frontend node the static websites files, but that should change.
Idea is to follow conventions created in #115 where we have an internal web server listening only to private network and that frontend type servers proxies requests to.
So far we only had the homepage as a static site and it’s hosted on the same VM as MediaWiki.
Maybe its time we aggregate static sites into one "upstream" role like we would do with a dynamic site backend but to serve only static files.
Sites that could benefit:
Note Even though specs.webplatform.org are also static html pages, we’ll let a specialized upstream ("upstream-specs") handle them since we have publican who takes care of refreshing the pages. We should therefore not touch specs.webplatform.org/publican in this work item.
The text was updated successfully, but these errors were encountered: