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

More explanation on self-hosted #41

Closed
dio opened this issue Nov 4, 2019 · 10 comments

Comments

@dio
Copy link

@dio dio commented Nov 4, 2019

I'm not sure what is self-hosted in this table. I just want to use an Ubuntu VM.

image

@taiyosogawa

This comment has been minimized.

Copy link
Contributor

@taiyosogawa taiyosogawa commented Nov 4, 2019

Hi dio,

Self-hosted environments are a "bring your own" device option to create an environment on your machine. You can learn more about them here.

@taiyosogawa

This comment has been minimized.

Copy link
Contributor

@taiyosogawa taiyosogawa commented Nov 4, 2019

If you're just looking for an Ubuntu VM, you can just refer to the Standard/Premium pricing depending on your HW spec needs. Thanks for asking and let us know if you have any other questions!

@jkeech jkeech added the documentation label Nov 4, 2019
@scottymcraig

This comment has been minimized.

Copy link

@scottymcraig scottymcraig commented Nov 4, 2019

I'm not sure if that's what he's asking - I had a similar question but assumed that it was not possible. I think he is asking if you can create a self-hosted environment without a GUI - for example, if I have a box hosted somewhere that is just running Ubuntu server, can I stand up an instance without having a full Visual Studio Code instance on it (since there's no GUI).

@taiyosogawa

This comment has been minimized.

Copy link
Contributor

@taiyosogawa taiyosogawa commented Nov 4, 2019

Ah, I see your point - thanks for asking.

Presently, running the "Register" command via a full instance of VS Code is the only supported flow, but the scenario you described of hosting a server without a GUI is on the product roadmap.

@dmitshur

This comment has been minimized.

Copy link

@dmitshur dmitshur commented Nov 5, 2019

I was just asking the same question about headless servers on Twitter.

FWIW, I found that it is possible to install VS Code and the VS Online extension via command line (i.e., see https://code.visualstudio.com/docs/setup/linux and https://code.visualstudio.com/docs/editor/extension-gallery#_command-line-extension-management), but I didn't find a way to configure the VS Online extension. That seems to need a GUI right now.

@scottymcraig

This comment has been minimized.

Copy link

@scottymcraig scottymcraig commented Nov 5, 2019

@taiyosogawa If you are looking for feedback on what users would prefer happen soon, I would vote for this. Simply because I would love to use this functionality, but I already have my own infrastructure and don't need to spin up a new VM for this, which would be cost prohibitive for me.

I realize you all are swamped with requests, but just my two cents 😄

@taiyosogawa

This comment has been minimized.

Copy link
Contributor

@taiyosogawa taiyosogawa commented Nov 5, 2019

@dmitshur @scottymcraig, thanks for connecting the conversation on Twitter and sharing the features that would help you most. I'm excited about your interest in self-hosted environments and your feedback is immensely helpful in helping us prioritize. We've created a tracking item for command-line functionality, and I've linked to this item to capture all the support.

@OneCyrus

This comment has been minimized.

Copy link

@OneCyrus OneCyrus commented Nov 6, 2019

but should self-hosted environments just be available in the browser version of vscode? or do we need internal network connectivity for this to work?

because currently i get Failed to connect to the remote extension host server

@taiyosogawa

This comment has been minimized.

Copy link
Contributor

@taiyosogawa taiyosogawa commented Nov 6, 2019

@OneCyrus, you should be able to connect to a self-hosted environment via the browser (no special setup beyond an internet connection required). Sorry to hear it didn't work for you. 😞

We've seen some failures on the first connection but subsequent successful connections, so I've created a tracking issue for that. The same happens on the first connection after upgrading your version of VS Code or switching to/from insiders.

If you think you're seeing something different, we can create a separate issue.

@taiyosogawa

This comment has been minimized.

Copy link
Contributor

@taiyosogawa taiyosogawa commented Nov 11, 2019

It looks like we have separate tracking issues for the points brought up in this thread. To help us keep things organized, I'm going to close this one, but let me know if I've missed anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants
You can’t perform that action at this time.