Skip to content

Add devcontainer configuration #129

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

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

dracco1993
Copy link

Description

Add configuration for docker vscode devconatienr

BONUS:

  • Add .dockerignore to decrease synced file traffic and improve performance when using docker
  • Add .gitattributes to tell git to use the correct linefeeds, regardless of platform
  • Add .github/PULL_REQUEST_TEMPLATE.md to maintain a reasonable standard for PRs
    • This was shamelessly pulled from another project I help work on, The Blue Alliance (template)
    • It doesn't have anything to do with the rest of this PR, so I can pull it out if desired; I really just included it as a potential starting point

Motivation and Context

It helps makes development more straight forward for new contributors.


VsCode devContainer:

Bottom left, click the blue "Open a Remote Window" icon:
image
Next click "Reopen in Container":
image


GitHub Codespaces:

This configuration also allows for 1-click style setup using GitHub Codespaces!
After clicking the + Codespace button here you'll be up and running!
image

Hosted codespace automatically installs dependencies and starts the project:
image
image

How Has This Been Tested?

Locally, and through GitHub Codespaces.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change API specifications or require data migrations)

@alan412
Copy link
Collaborator

alan412 commented Jun 30, 2025

Thank you for this, but right now we are focused on getting to MVP (minimum viable product) so it can go into the hands of teams for testing.

Until we have that, things are changing so fast that we won't be pulling in PRs for other features. I am keeping this open so that we can look at it after we have an MVP out to teams.

@alan412 alan412 added this to the after_mvp milestone Jun 30, 2025
@alan412 alan412 removed this from the after_mvp milestone Jun 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants