I had some debugging to do, so I wanted a straightforward way to build new images. Since the Dockerfiles everytime got the already uploaded images from dockerhub, instead of using the actual sourcecode, it was a tedious task unless I move the docker context two up, so it could access the code directly (and add it to the image without calling dockerhub).
Though not sure if this behaviour is intended.
(And somehow some debugging-stuff for my other issue polluted into this. Though it does not break anything, so I keep it there)
Copy .env.default to .env, modify if you want to use your own dockerhub-repos, and then start with: make build (and possibly make publish) to get the latest version (though no tests if taiga-contrib-openid-authstill works with that specific taiga-front/-back version done!)
robrotheram
commented
3 months ago
I had some debugging to do, so I wanted a straightforward way to build new images. Since the Dockerfiles everytime got the already uploaded images from dockerhub, instead of using the actual sourcecode, it was a tedious task unless I move the docker context two up, so it could access the code directly (and add it to the image without calling dockerhub).
Though not sure if this behaviour is intended.
(And somehow some debugging-stuff for my other issue polluted into this. Though it does not break anything, so I keep it there)
Copy
.env.defaultto.env, modify if you want to use your own dockerhub-repos, and then start with:make build(and possiblymake publish) to get the latest version (though no tests iftaiga-contrib-openid-authstill works with that specifictaiga-front/-backversion done!)use at you own risk