Juan Carlos Mejías Rodríguez
Juan Carlos Mejías Rodríguez
I like the first approach: releasing your *next * branch as a 1.x version and releasing the Go code as a 2.x version. This way all the contributions you made...
Hi @tortuetorche. I have got another idea: - Revert the Go-related commits in `master` back to 3326a0. - Merge your `next` branch into `master`. - Cherry-pick Go-related commits into a...
OK, I just started the import into psuapp/psu. It should not take long.
It's been importing the project for eight hours. I removed the project and reimported it, just in case.
Please let's keep the discussion about migration to GitLab on #19, this issue's topic is CI.
@tortuetorche I started reviewing in depth your latest changes to the `next` branch here in GitHub and the ones on CI and documentation in GitLab. To be honest, I have...
As migration to GitLab #19 is not going as expected I am considering using another of the available CI solutions like Travis CI, Circle CI, Drone.io. Whatever is chosen, it...
Something like ```bash docker run -v $(pdw)/docker-compose.yml:/docker-compose.yml -e ACTION="deploy" -e PORTAINER_USER="admin" -e PORTAINER_PASSWORD="password" -e PORTAINER_URL="http://portainer.example.com" -e PORTAINER_STACK_NAME="mystack" -e DOCKER_COMPOSE_FILE="docker-compose.yml" greenled/portainer-stack-utils psu ``` ```bash docker run -v $(pdw)/docker-compose.yml:/docker-compose.yml greenled/portainer-stack-utils psu -a...
@tortuetorche any thoughts on this?
My first attempt: *The Wrapper's Wrapper* for project name and `ww` for executable name.