-
Notifications
You must be signed in to change notification settings - Fork 4
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
Provide a bleeding edge version #10
base: main
Are you sure you want to change the base?
Conversation
@@ -22,7 +22,8 @@ RUN set -x && apt-get update && \ | |||
cd $DRUPAL_COMPOSER_ROOT && \ | |||
composer require drush/drush || \ | |||
# Try drush 11.x-dev if the above fails. | |||
composer require drush/drush:11.x-dev && \ | |||
composer require drush/drush:11.x-dev || \ | |||
composer require drush/drush:13.x-dev && \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reverse order.
docker build \ | ||
--build-arg DRUPAL_VERSION=$(BLEEDING_EDGE_VERSION) \ | ||
--build-arg PHP_VERSION=$(D11_PHP_VERSION) \ | ||
-t $(DESTINATION_DOCKER_IMAGE):$(BLEEDING_EDGE_TAG) . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works, but re-creates the bleeding edge one once per existing tag, which is suboptimal (even with all layers cached).
Need to learn more about Makefiles to avoid it.
Didn't do extensive testing of the image, but there might be some permissions issues on settings.php
, and drush site-install
is not working (might be not our issue, or might be related to the permissions)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this may run on every version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we could just add a dev
tag that is that uses HEAD of recommended-project?
@@ -56,7 +59,7 @@ targets: ## Print out the available make targets. | |||
.PHONY: push-image | |||
push-image: tag ## Push the tagged images to the docker registry. | |||
# # Push the images. | |||
docker push --all-tags ${DESTINATION_DOCKER_IMAGE} | |||
#docker push --all-tags ${DESTINATION_DOCKER_IMAGE} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this might have snuck in?
docker build \ | ||
--build-arg DRUPAL_VERSION=$(BLEEDING_EDGE_VERSION) \ | ||
--build-arg PHP_VERSION=$(D11_PHP_VERSION) \ | ||
-t $(DESTINATION_DOCKER_IMAGE):$(BLEEDING_EDGE_TAG) . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this may run on every version.
This should provide an image of the latest -dev release.