akosiaris added a comment.

  For what is worth, the idea that Daniel explains above, would solve the issue 
for now without the need to move to kubernetes, satisfying multiple of the 
requirements without requiring significant effort.
  
  The following from the task description are satisfied:
  
  [X] Teams that manage / own the sites should be able to update the content of 
the site
  [X] The hosting location can be pointed to from sub paths of 
query.wikidata.org (and similar flexible locations). For WDQS this could be 
done in the WDQS nginx server config
  [X] Does CDN cache purging need to be considered at all (setting the correct 
`Cache-control` HTTP header in the apache config would solve this).
  
  The following aren't, but were marked by yours truly as SHOULD, not MUST to 
begin with. In the interest of moving forward and providing a solution I think 
it's ok.
  
  [ ] Support for structured logging to stdout to allow debugging issues via 
our ELK stack should be a requirement.
  [ ] Support for exporting metrics via prometheus or statsd should be a 
requirement.

TASK DETAIL
  https://phabricator.wikimedia.org/T264710

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: akosiaris
Cc: JMeybohm, CDanis, Dzahn, Gehel, dcausse, Joe, akosiaris, Tarrow, Aklapper, 
WMDE-leszek, Addshore, wkandek, CBogen, Akuckartz, darthmon_wmde, Nandana, 
Namenlos314, jijiki, Lahi, Gq86, Lucas_Werkmeister_WMDE, GoranSMilovanovic, 
Mahir256, QZanden, EBjune, merbst, LawExplorer, Salgo60, _jensen, rosalieper, 
Scott_WUaS, Jonas, Xmlizer, jkroll, Wikidata-bugs, Jdouglas, aude, Tobias1984, 
Manybubbles, Lydia_Pintscher, Mbch331
_______________________________________________
Wikidata-bugs mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Reply via email to