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

Do we want to fully support codespaces? #152

Closed
nabuskey opened this issue Feb 19, 2024 · 1 comment
Closed

Do we want to fully support codespaces? #152

nabuskey opened this issue Feb 19, 2024 · 1 comment

Comments

@nabuskey
Copy link
Collaborator

GH codespaces is a good way to get started on a project: https://github.com/features/codespaces

It pretty much provisions a VM, then allows you to run w/e on it. You can forward a local port to an external endpoint provided by GH as well.

Having full support for codespaces allows people new to the project to click a button in this project and start playing around with it. I think it's a good way to make it easier for people to get started.

It does come with complications though. See: #148 (comment)

Is it worthwhile to fully support this? By fully support, I mean allow for users to run this trough their web browsers.

@nimakaviani
Copy link
Contributor

certainly very useful and I see this as an easy way to demo and get users excited about the idpbuilder. That said, I dont think this is something we will want to burn cycles from core contributors on at this point. Let's leave it as an open issue, and if there are interested individuals who would want to pick this up, we can support them.

@nabuskey nabuskey closed this as completed Mar 4, 2024
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

No branches or pull requests

2 participants