You are browsing a read-only backup copy of Wikitech. The live site can be found at wikitech.wikimedia.org

Talk:Blubber/Download: Difference between revisions

From Wikitech-static
Jump to navigation Jump to search
imported>Pablo Grass (WMDE)
(→‎Docker image: new section)
 
imported>SBassett
 
Line 3: Line 3:
There is a [https://docker-registry.wikimedia.org/v2/wikimedia/blubber/tags/list docker image for blubber as a micro service] - this runs a web service.
There is a [https://docker-registry.wikimedia.org/v2/wikimedia/blubber/tags/list docker image for blubber as a micro service] - this runs a web service.
Are there any plans for a docker image containing blubber as a binary? Are there objective reasons against such approach? This would allow for blubber to be used as part of our development tool chain (being dependent only on docker/docker-compose) without making it a system requirement the individual dev needs to ensure manually.
Are there any plans for a docker image containing blubber as a binary? Are there objective reasons against such approach? This would allow for blubber to be used as part of our development tool chain (being dependent only on docker/docker-compose) without making it a system requirement the individual dev needs to ensure manually.
== Change install instructions to 'go install' ==
"'go get' is no longer supported outside a module."
...the go binary tells me.  It appears <code>go install https://repo/uri@version</code> is now the preferred method, outside of a module?

Latest revision as of 18:47, 27 May 2022

Docker image

There is a docker image for blubber as a micro service - this runs a web service. Are there any plans for a docker image containing blubber as a binary? Are there objective reasons against such approach? This would allow for blubber to be used as part of our development tool chain (being dependent only on docker/docker-compose) without making it a system requirement the individual dev needs to ensure manually.

Change install instructions to 'go install'

"'go get' is no longer supported outside a module."

...the go binary tells me. It appears go install https://repo/uri@version is now the preferred method, outside of a module?