Suggestion: vscode remote container support

[laurb9]

What does this do

Add support for Visual Studio Code with In-Container Development.

Why

• Makes it easy to start developing prebid-server on any OS that supports Docker, without having to install any other dependencies on the host. Developing in a container isolates the dev environment from the host and is easy to reset or duplicate for checking other PRs etc.

I've added a small VSCODE.md for orientation.

The rest are applicable to on-host vscode development too:

• There is an in-IDE visual debugger
• Individual tests can be run or debug directly from the IDE.
• Style is enforced by the Golang plugin (naming, comments, imports, errors etc). The Golang plugin for VSCode is maintained by the Google folks.

Here is a screenshot showing most of the features in a squeezed window.

One drawback that I noticed is that if the container is cpu-limited, and it usually is, the tests will need a timeout longer than 10min sometimes to avoid failures.

[SyntaxNode]

I think this is a cool dev setup. I also think this won't be what everyone wants to work with. How do you feel about adding this primarily as markdown with sample json file contents along with instructions?

[laurb9]

I think this is a cool dev setup. I also think this won't be what everyone wants to work with. How do you feel about adding this primarily as markdown with sample json file contents along with instructions?

Can the sample files be in .devcontainer ? :) I can remove the extra .vscode stuff.

I don't mind this not being merged at all, as I wrote it's just a suggestion; but from my experience, spinning up the IDE with dependencies and the right extensions to get to trying out changes, would've been a decent bonus when I started.

[stale]

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

[bsardo]

I agree this is pretty cool and I think it's worth merging as long as it's opt-in.

[SyntaxNode]

We (finally) got around to discussing this PR. We think it's great to offer guidance for devs who want to use this feature. Let's just leave the default vscode setup alone for now.