Anyone having fun writing Dockerfiles and might want to do that for my #mvoCI? It should not be difficult, it's a #golang project, so buidling and running it should be trivial. Config and database file could be interesting though, these would need to be persistently stored.
I can't be bothered to spend more time in this weird syntax.
Bonus points for making it so, that is explains what is is doing.
[#]docker
=> More informations about this toot | More toots from snaums@kif.rocks
@snaums You got a link to the project?
And does it need cgo?
=> More informations about this toot | More toots from morre@chaos.social
@morre It does need cgo.
https://codeberg.org/snaums/mvoCI
=> More informations about this toot | More toots from snaums@kif.rocks
@snaums @morre Does it need CGO just for sqlite? Or are there other dependencies needing CGO?
=> More informations about this toot | More toots from dolanor@hachyderm.io
@dolanor yes for sqlite and for pthreads. @morre
=> More informations about this toot | More toots from snaums@kif.rocks
@snaums @morre why do you need pthreads?
=> More informations about this toot | More toots from dolanor@hachyderm.io
@dolanor because I wanted real threads* as build-threads not just go-routines, which may or may not be real threads. //cc @morre
=> More informations about this toot | More toots from snaums@kif.rocks
@snaums @morre OK, so my first step for build in Go is to make sure to avoid CGO, especially when building on alpine. It's just a headache I'd rather avoid.
Anyway, I still don't know why you need pthread, but it seems a requirement, so we will have to get the extra annoyance of CGO and buildflags, etc.
I will try to make some Dockerfile that would work for your project.
Ping me if I totally forgot, since.
=> More informations about this toot | More toots from dolanor@hachyderm.io This content has been proxied by September (3851b).Proxy Information
text/gemini