Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introducing Local/Remote release deployments #92

Merged
merged 1 commit into from
Mar 29, 2017

Conversation

maneta
Copy link

@maneta maneta commented Mar 29, 2017

In this PR we introduce the possibility to deploy local or remote release to the docker registry

@EricWittmann
Copy link
Member

Nice. Just read the docs on ADD vs. COPY for a dockerfile. Looks like this was easier than you thought it would be eh? :)

@EricWittmann EricWittmann merged commit cfe4fac into Apicurio:master Mar 29, 2017
@@ -16,8 +17,15 @@ all: build
update: build push

build: ## Build docker image with name LOCAL_IMAGE (NAME:RELEASE_VERSION).
docker build -f $(THISDIR_PATH)/Dockerfile -t $(LOCAL_IMAGE) $(PROJECT_PATH) \
--build-arg RELEASE_VERSION=$(RELEASE_VERSION)
@if [ -f "./front-end/quickstart/target/api-design-studio-${RELEASE_VERSION}-quickstart.zip" ] || [ ${LOCAL_RELEASE} == "true" ]; then \
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I Could set the RELEASE_PATH variable in the subshell, but doing it replicating the docker build command it improves readability

@maneta
Copy link
Author

maneta commented Mar 29, 2017

yes it was :)

@maneta maneta deleted the feature/flexible_docker_deploy branch March 29, 2017 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants