Page MenuHomePhabricator

Phonos should have its own shellbox deployment for production
Closed, DeclinedPublic

Description

[...] Note that (I think I said this elsewhere), Phonos should have its own shellbox deployment for production.

(placeholder, assuming Community-Tech won't be responsible for setting that up? 😺)

Event Timeline

(though, we won't need shellbox in production as Google can return MP3s directly...)

I would suggest creating a task like T289226 (or just copying the checklist to here). You will need a root (probably in serviceops) to do the initial token creation and setup, but after that deployment of the shellbox can be done by anyone with MW deployment access.

The main reason I suggest a different Shellbox deployment is because I expect the request pattern of Phonos to be pretty different (more requests but much faster) from Score/lilypond or "media" (uploads) so it merits a different amount of resources. And it's just easier to track and monitor as a separate deployment.

(though, we won't need shellbox in production as Google can return MP3s directly...)

[offtopic] Is there a separate task we can track the reliance on a proprietary service instead of using a free software solution?

(though, we won't need shellbox in production as Google can return MP3s directly...)

[offtopic] Is there a separate task we can track the reliance on a proprietary service instead of using a free software solution?

T307624: [16 hours] Investigate: Options of TTS engines. Some of us (myself included) were passionate about pushing for FOSS but from the options we found, Google performed extraordinarily better and supports many more languages. The Language team who will eventually takeover ownership of Phonos also seemed more keen to use Google than having to maintain/update third-party code. At any rate, Phonos was designed in such a way that we can add more engines if we find one better than Larynx and eSpeak, which we already support. For now, I believe the decision has been made that we're going with Google.

That said, as Sammy says I suppose we don't need to worry about Shellbox deployment for this initial launch, but it's great you raised this because I'm not sure we were aware that this step was necessary.

(though, we won't need shellbox in production as Google can return MP3s directly...)

[offtopic] Is there a separate task we can track the reliance on a proprietary service instead of using a free software solution?

Remaining [offtopic] here, but I'd quite like to see if we can maintain https://larynx-tts.wmcloud.org/openapi — perhaps I'll request a WMCS project for it and chuck a load of compute power at a VM and see how the maximum settings sound (as the generation time at that level tends to be fairly long on even moderately spec'd VMs)

Thanks both, I've filed T317274: Use free software implementation for Phonos on Wikimedia sites and copied your comments there. Unsure if this task should stay open or be declined if it's not actually needed yet?

Thanks both, I've filed T317274: Use free software implementation for Phonos on Wikimedia sites and copied your comments there. Unsure if this task should stay open or be declined if it's not actually needed yet?

Thanks for filing that @Legoktm — I'll close this task off