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

Prompt a user for their Connect URL #22

Closed
tnederlof opened this issue Feb 15, 2023 · 2 comments · Fixed by #36
Closed

Prompt a user for their Connect URL #22

tnederlof opened this issue Feb 15, 2023 · 2 comments · Fixed by #36
Labels
enhancement New feature or request

Comments

@tnederlof
Copy link
Contributor

Many users that set up Workbench will also have a Connect server they would like to have set as the default to make it easier on their users deploying to Connect. This step is often missed/not included and wbi is an excellent opportunity to set this from the beginning.

The Workbench Admin Guide specifies setting the default-rsconnect-server option in rsession.conf.

  1. Ask if the user has a Connect server they would like to use as the default
  2. If they have Connect then prompt for a URL and save that as the default-rsconnect-server option
@tnederlof tnederlof added the enhancement New feature or request label Feb 15, 2023
@samcofer
Copy link
Contributor

I'm wondering if we should push this issue a little bit: rstudio/rsconnect-jupyter#217

Not sure it's directly related, but seems like it would be a nice quality of life improvement to only need to set this once.

@tnederlof
Copy link
Contributor Author

Good call, I never realized it wasn't pulling from that field. I know there is a big Jupyter Notebook change that just came out that will break this extension going forward. Its prob worth checking with Workbench team what there plans are (is this going to be abandoned for a new package, etc).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants