Yeh sounds good! If someone does the heavy lifting on the first pass, I can help take a 2nd pass on migrating / deploying the instance I maintain and clean up any leftovers.
Yeh sounds good! If someone does the heavy lifting on the first pass, I can help take a 2nd pass on migrating / deploying the instance I maintain and clean up any leftovers.
Indiehosters image repo is archived 😢 https://lab.libreho.st/libre.sh/docker/discourse/
Another source of inspiration (not updated in 5 years? 😭) https://github.com/0ex/discourse-kiss
Discourse is also hosting its own image! discourse/discourse. It's already working, and according to this message by one of the team members, it will be officially supported soon.
I just made a local chaos of this recipe and got it running, but it does require renaming some env vars. Unfortunately, the Bitnami image seems unavailable, so I can't easily test if this will upgrade.
Discourse is also hosting its own image! `discourse/discourse`. It's already working, and according to [this message](https://meta.discourse.org/t/is-docker-image-discourse-discourse-considered-safe-and-production-ready/380646/21) by one of the team members, it will be officially supported soon.
I just made a local chaos of this recipe and got it running, but it does require renaming some env vars. Unfortunately, the Bitnami image seems unavailable, so I can't easily test if this will upgrade.
Holy cow @dannygroenewegen, amazing! If you prepare the breaking release changes in a PR, I can give it a chaos deploy on my bitnami deployment? It would be so great to dig ourselves out of this deprecated image shitstorm!
Holy cow @dannygroenewegen, amazing! If you prepare the breaking release changes in a PR, I can give it a chaos deploy on my `bitnami` deployment? It would be *so* great to dig ourselves out of this deprecated image shitstorm!
oh I missed this issue before. that discourse itself now has an image is even better than the self-published image i thought might have been necessary. I was already mucking with this as autonomic is trying to get all its stuff up to date, so I can continue and take a look at using the real discourse/discourse now
oh I missed this issue before. that discourse itself now has an image is even better than the self-published image i thought might have been necessary. I was already mucking with this as autonomic is trying to get all its stuff up to date, so I can continue and take a look at using the real `discourse/discourse` now
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Yeh sounds good! If someone does the heavy lifting on the first pass, I can help take a 2nd pass on migrating / deploying the instance I maintain and clean up any leftovers.
Indiehosters image repo is archived 😢 https://lab.libreho.st/libre.sh/docker/discourse/
Another source of inspiration (not updated in 5 years? 😭) https://github.com/0ex/discourse-kiss
I guess adopting the librehosters image into
coop-cloud-chaos-patchsis one option.Discourse is also hosting its own image!
discourse/discourse. It's already working, and according to this message by one of the team members, it will be officially supported soon.I just made a local chaos of this recipe and got it running, but it does require renaming some env vars. Unfortunately, the Bitnami image seems unavailable, so I can't easily test if this will upgrade.
Holy cow @dannygroenewegen, amazing! If you prepare the breaking release changes in a PR, I can give it a chaos deploy on my
bitnamideployment? It would be so great to dig ourselves out of this deprecated image shitstorm!oh I missed this issue before. that discourse itself now has an image is even better than the self-published image i thought might have been necessary. I was already mucking with this as autonomic is trying to get all its stuff up to date, so I can continue and take a look at using the real
discourse/discoursenow