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

[FEAT] Expose bind-addr, auth, password and cert as environment variables #169

Closed
1 task done
csvke opened this issue Jan 24, 2024 · 5 comments
Closed
1 task done

Comments

@csvke
Copy link

csvke commented Jan 24, 2024

Is this a new feature request?

  • I have searched the existing issues

Wanted change

Expose bind-addr, auth, password and cert as environment variable

Reason for change

Have such environment variables to avoid manually changing the ~/.config/code-server/config.yaml file as per Tailscale’s configuration suggestion so one can access code-server securely using tailscale.

Proposed code change

No response

@csvke csvke added the enhancement New feature or request label Jan 24, 2024
Copy link

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@csvke csvke changed the title [FEAT] <title>Expose bind-addr, auth, password and cert as environment variable [FEAT] Expose bind-addr, auth, password and cert as environment variable Jan 24, 2024
@csvke csvke changed the title [FEAT] Expose bind-addr, auth, password and cert as environment variable [FEAT] Expose bind-addr, auth, password and cert as environment variables Jan 24, 2024
@LinuxServer-CI
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

@drilus
Copy link

drilus commented Apr 10, 2024

This is a good idea

@LinuxServer-CI
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

@LinuxServer-CI LinuxServer-CI closed this as not planned Won't fix, can't repro, duplicate, stale Jul 10, 2024
@LinuxServer-CI LinuxServer-CI moved this from Issues to Done in Issue & PR Tracker Jul 10, 2024
Copy link

github-actions bot commented Aug 9, 2024

This issue is locked due to inactivity

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Development

No branches or pull requests

3 participants