Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate static sites into a specialized internal upstream node #169

Open
renoirb opened this issue May 20, 2015 · 0 comments
Open

Migrate static sites into a specialized internal upstream node #169

renoirb opened this issue May 20, 2015 · 0 comments

Comments

@renoirb
Copy link
Member

renoirb commented May 20, 2015

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant