This fixes the case, where you bind-mount your own tileboard source directory into the dev container.
Apparently, the node-sass module is compiled for the specdific machine.
This seems to result in the `node-sass` executable not being found in the container, if the `node_modules` folder was compiled on a different machine (OS?).
By adding node-sass globally in the container, it can be found even with a bind-mounted `tileboard-source` directory.
So, here we go with a PR for the nightly images. **They will need to have a nightly (at least) run of the pipeline.**
I have also included a script and modifications to `drone.yml`, which I believe should serve well as a check-for-changes. But I have no way to check this in your drone environment. ~~And I have not (yet) checked it locally, either. I just copied things over from my GitHub setup.~~ (Update: The script works for me locally.)
Could you have a look and let me know, what needs to be changed from your point of view?
(I don't know Gitea too well... If there's an option to let you write into this feature branch, I'll enable it.)
fixes#4
Co-authored-by: dev-docker <akloeckner@users.noreply.github.com>
Co-authored-by: Florian Brinker <mail+gitlab@f-brinker.de>
Reviewed-on: fbrinker/docker-tileboard#5
Co-authored-by: akloeckner <akloeckner@noreply.example.org>
Co-committed-by: akloeckner <akloeckner@noreply.example.org>
This introduces:
* an explicit check for the existence of the latest version tag
* This way, we don't need to bother to have `nightly` or `dev` tags in place. The new check works by `curl` failing, if the target tag does not exist.
* more verbose output
* This was just for debugging actually, but I believe it might help in the future.
* input parameters to the `build.sh` script
* This allows for using the script also from other repos. I'd like to keep trying things without having to ask you for checking in Drone.io...
dev-docker
akloeckner
Florian Brinker