- Mentioned In
- T180021: Security review for extension Wikispeech
T235844: Collect tasks related code and security review
T194014: Leave Wikispeech ready for deployment
- Mentioned Here
- T183780: Elhuyar - Wikispeech - eu
T180015: ☂ Deploy Wikispeech on beta cluster
T151877: Set up puppet role for TTS server
T180021: Security review for extension Wikispeech
So, Operations can you tell @Lokal_Profil whether docker-compose is a valid deployment strategy? Or if they need to do so something else...
A valid deployment strategy for production ? No, it is not. It's fine for Mediawiki-vagrant of course, but it can't really lead to work that is reusable in production (which might or might not be the end goal, I am not sure yet, but I guess it is per T180015)
Deployment via containers to our production Kubernetes cluster is probably an option. The containers themselves will need to be built using the tooling that SRE and Release-Engineering-Team are creating for the Release Pipeline project. As far as I understand it, Mathoid is now using this system (Release Pipeline (Blubber) + helm) for deployment. I can't find any comprehensive overview of setting up a new project this way, but that seems kind of reasonable since I think there is only one thing that has actually been made to use the pipeline so far.
I think the goal here would be to write a blubber file and have the service then deployed ot labs in a similar way to the wikidata termbox service.
@Tarrow tells me that right now the details of how we do that are in https://github.com/wikimedia/wikibase-termbox/tree/master/infrastructure (this is a mirror, actual code on gerrit)