Change Details

In T264710#6562678, T264710#6573814 and T264710#6586070 as part of {T264710} it was decided that the query ui and querybuilder ui would be deployed on the "static sites" infrastructure. See https://wikitech.wikimedia.org/wiki/Microsites This ticket currently serves as a placeholder for the #wikidata_query_builder team to use when needed. The wdqs GUI build is being added to the microsite infrastructure in https://gerrit.wikimedia.org/r/c/operations/puppet/+/637552 The microsite infrastructure simply serves files from disk that are fetched from git via puppet. When the WDQS UI is deployed a the directory `/srv/org/wikidata/query` will already be populated on the server. Per Lydia in T266703#6590996 the querybuilder will need to live at `/srv/org/wikidata/query/querybuilder` Possible approaches: - Use a single -deploy git repo and have both the WDQS UI and the query builder source repositories build into the respective location. One in `/` and the other in `/querybuilder` - Need to make sure that the WDQS UI build doesn't override the other build output - Have 2 git repos fetched in puppet? - These might end up conflicting with each other as they need to live inside each other

In T264710#6562678, T264710#6573814 and T264710#6586070 as part of {T264710} it was decided that the query ui and querybuilder ui would be deployed on the "static sites" infrastructure. See https://wikitech.wikimedia.org/wiki/Microsites This ticket currently serves as a placeholder for the #wikidata_query_builder team to use when needed. The wdqs GUI was moved to microsites in {T266702} Similar steps will be needed for the querybuilder deployment. Per Lydia in T266703#6590996 the querybuilder will need to live at `/srv/org/wikidata/query/querybuilder` [] Create a repository containing the built code to be deployed (and needed infrastructure / build process around that) [] Puppet change adding the site to microsites [] Test that the site is accessible inside the cluster [] Change the traffic layer so that public access is given at the correct path for the site [] Puppet tests for the microsite [] Update microsites docs page on wikitech stating this site is deployed on microsites

In T264710#6562678, T264710#6573814 and T264710#6586070 as part of {T264710} it was decided that the query ui and querybuilder ui would be deployed on the "static sites" infrastructure. See https://wikitech.wikimedia.org/wiki/Microsites This ticket currently serves as a placeholder for the #wikidata_query_builder team to use when needed. The wdqs GUI build is being addwas moved to the microsite infrastructures in https://gerrit.wikimedia.org/r/c/operations/puppet/+/637552{T266702} The microsite infrastructure simply serves files from disk that are fetched from git via puppet. When the WDQS UI is deployed a the directory `/srv/org/wikidata/query` will already be populated on the serverSimilar steps will be needed for the querybuilder deployment. Per Lydia in T266703#6590996 the querybuilder will need to live at `/srv/org/wikidata/query/querybuilder` Possible approaches:[] Create a repository containing the built code to be deployed (and needed infrastructure / build process around that) [] Puppet change adding the site to microsites - Use a single -deploy git repo and have both the WDQS UI and the query builder source repositories build into the respective location. One in `/` and the other in `/querybuilder`[] Test that the site is accessible inside the cluster - Need to make sure that the WDQS UI build doesn't override[] Change the traffic layer so that public access is given at the other build outputcorrect path for the site - Have 2 git repos fetched in puppet?[] Puppet tests for the microsite - Thes[] Update might end up conflicting with each other as they need to live inside each othercrosites docs page on wikitech stating this site is deployed on microsites