Smoke-testing plugins during upgrade process

One solution to the pain of installing plugins is to move to a two container configuration. This let’s you build and rebuild new containers while your old one merrily continues.

I’ve mostly written a discourse-setup that will do a two container install. That keeps the site from going down in a rebuild and means that if it fails you can figure out the problem without the pressure of a broken site.

I’ve not quite completed it because I actually have enough work now that I’m not looking for projects. Also, the implications of supporting another configuration seem daunting. Will people know that instead of “rebuild app” they will “rebuild web”? Do we change and make this the default configuration? What about all of the old ones with a single container?

I’ve not been so successful in making the transition from one to two container configurations seemless, though a simple backup and restore isn’t that difficult to do manually.

7개의 좋아요

It’s a ton of work making the move, I agree it is a better setup, but making the move is pain :mount_fuji:

2개의 좋아요

여기서 PR 환영 태그를 제거했습니다. 사이트 설정을 통해 플러그인 비활성화를 이미 지원하고 있으므로, 기존 시스템에 대한 개선은 대규모 재설계가 필요하며, 이는 분명히 pr-welcome의 범주에 해당하지 않습니다.