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

Improve Dockerfile #135

Merged
merged 4 commits into from
Nov 21, 2022
Merged

Improve Dockerfile #135

merged 4 commits into from
Nov 21, 2022

Conversation

jsf9k
Copy link
Member

@jsf9k jsf9k commented Nov 4, 2022

🗣 Description

This pull request makes several small improvements to the repo's Dockerfile.

💭 Motivation and context

I have been using these improvements in descendants of cisagov/skeleton-docker as I skeletonize them, so it makes sense to go ahead and push the changes upstream.

🧪 Testing

All automated tests pass.

✅ Pre-approval checklist

  • This PR has an informative and human-readable title.
  • Changes are limited to a single goal - eschew scope creep!
  • All relevant type-of-change labels have been added.
  • I have read the CONTRIBUTING document.
  • These code changes follow cisagov code standards.
  • All new and existing tests pass.

@jsf9k jsf9k added the improvement This issue or pull request will add or improve functionality, maintainability, or ease of use label Nov 4, 2022
@jsf9k jsf9k self-assigned this Nov 4, 2022
@jsf9k jsf9k force-pushed the improvement/dockerfile branch from 0afd230 to 98d58be Compare November 4, 2022 04:11
@jsf9k jsf9k added the blocked This issue or pull request is awaiting the outcome of another issue or pull request label Nov 4, 2022
@jsf9k jsf9k marked this pull request as ready for review November 4, 2022 04:14
Copy link
Member

@dav3r dav3r left a comment

Choose a reason for hiding this comment

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

Very nice 🌹

Copy link
Member

@mcdonnnj mcdonnnj left a comment

Choose a reason for hiding this comment

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

Strong work backporting some of the common things we do downstream 💪💪💪 I have some suggestions for your consideration.

Dockerfile Show resolved Hide resolved
Dockerfile Show resolved Hide resolved
Dockerfile Show resolved Hide resolved
Dockerfile Show resolved Hide resolved
Copy link
Member

@dav3r dav3r left a comment

Choose a reason for hiding this comment

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

👍 👍

I'm fine with any of the proposed options for the authors label.

@jsf9k jsf9k removed their assignment Nov 15, 2022
@mcdonnnj mcdonnnj force-pushed the improvement/dockerfile branch from 90b1c72 to 2a72bf6 Compare November 21, 2022 23:17
@mcdonnnj mcdonnnj merged commit 6f639fe into develop Nov 21, 2022
@mcdonnnj mcdonnnj deleted the improvement/dockerfile branch November 21, 2022 23:25
mcdonnnj added a commit that referenced this pull request Nov 22, 2022
I accidentally clobbered these changes when I was updating
#135 for merge. This restores the changes made
during review as well as fixing a missed reference to the CISA_USER
argument.

Co-authored-by: Shane Frasier <jeremy.frasier@trio.dhs.gov>
mcdonnnj added a commit that referenced this pull request Nov 22, 2022
I accidentally clobbered these changes when I was updating
#135 for merge. This restores the changes made
during review as well as fixing a missed reference to the CISA_USER
argument.

Co-authored-by: Shane Frasier <jeremy.frasier@trio.dhs.gov>
Sallenmoore pushed a commit to Sallenmoore/foundryvtt-docker that referenced this pull request Jun 18, 2023
I accidentally clobbered these changes when I was updating
cisagov/skeleton-docker#135 for merge. This restores the changes made
during review as well as fixing a missed reference to the CISA_USER
argument.

Co-authored-by: Shane Frasier <jeremy.frasier@trio.dhs.gov>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked This issue or pull request is awaiting the outcome of another issue or pull request improvement This issue or pull request will add or improve functionality, maintainability, or ease of use
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants