update index.md text and gce diagram - #92
Conversation
| # Code & Config | ||
|
|
||
| All code lives on Github in the [wbstack org](https://github.com/wbstack). | ||
| All code lives on Github in the [wbstack org](https://github.com/wbstack) or the [wmde org](https://github.com/wmde) |
There was a problem hiding this comment.
From the point of view of "wbstack" the software that can deploy multiple wikibases via the k8s seutp, i beleive "all code" still lives on github?
Only the wmde wikibase.cloud deployment repo i believe is on the wmde org?
So perhaps just linking to that deploy repo makes sense?
And or link to a specific filtered list of repos on the wmde org if there are indeed more
There was a problem hiding this comment.
Given how rarely this is updated I'm not keen to enumerate what appears to be en exhaustive list which is then likely to get out of date.
I believe there are 3 vaguely relevant repos in the wmde org:
- wmde/wbaas-deploy
- wmde/wbaas-backup
- wmde/wikibase-cloud-status (no code that really lands in the cluster)
| The only current deployment of this stack is [wikibase.cloud](https://wikibase.cloud). | ||
|
|
||
|  | ||
|  |
There was a problem hiding this comment.
Mentioned elsewhere, but it might be neat to first move the diagram to a file name such as tech-overview-gce-k8s.drawio.svg
And then change it from there in antoehr commit, so that the github diff image visualization can be used to see the differences
There was a problem hiding this comment.
Yes! I would like this, but I won't block merging by requiring it's done.
outdooracorn
left a comment
outdooracorn
left a comment
There was a problem hiding this comment.
From what I can tell, these changes look correct.
I've left some comments for possible improvements to this diagram, but I won't block this PR on them.
| The only current deployment of this stack is [wikibase.cloud](https://wikibase.cloud). | ||
|
|
||
|  | ||
|  |
There was a problem hiding this comment.
Yes! I would like this, but I won't block merging by requiring it's done.
There was a problem hiding this comment.
Some of the images aren't loading in the full-screen view of this for me (e.g. mariadb, argocd, helmfile), but they do in the small preview, so I assume it's okay.
There was a problem hiding this comment.
The 3-way-ish arrow between the mediawiki group, the api-backend, and the query-gateway is confusing to me. Looking at the "From API" text and a little bit of domain knowledge, I'm assuming that the query-gateway calls the api-backend and the fact it is touching the mediawiki group to api-backend line means nothing? However, this was present in the original diagram, so I won't block this PR.
There was a problem hiding this comment.
The platform-nginx now calls the api-backend in order to route to mediawiki. Should this be on the diagram?
3 participants
No description provided.