You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Distributing weechat as a container should become the recommended way to run it. Still at this moment we only have this repository which is used to build containers, not to publish them.
configure pipelines for building
assure containers endup on docker.io and quay.io, both have ability to automatically build containers, so a GHA push strategy may not be required.
Yes for now, nothing is automated.
I thought that with 3/4 version per year, I could still do it manually, but I'll check to automate this.
Adversiting on the containers, yes of course, once they are available.
Recommending to run weechat in a container, I'm not for. What's the goal behind? Using packages from distributions or compiling sources is for me the right way to use WeeChat. Of course container is just an extra option, but I don't get the point to recommend this by default.
Distributing weechat as a container should become the recommended way to run it. Still at this moment we only have this repository which is used to build containers, not to publish them.
docker.io
andquay.io
, both have ability to automatically build containers, so a GHA push strategy may not be required.The text was updated successfully, but these errors were encountered: