Remove setup-dev.md file and keep the relevant part in the main README

Signed-off-by: Guillaume Bourque <[email protected]>

Author: bougui

README.md

@@ -144,10 +144,19 @@ The described process is automated in one of the ways below (it allow to install
  - **Also coming soon:** Create virtual machines in AWS.
 
 
-
 ## How to Start Working with the Code
 
-Please have a look at [Dev Setup](docs/source/setup-dev.md)
+The preferred method of setting up the development environment is to use the **devcontainers**.
+All configuration files for VSCode and [Gitpod](https://gitpod.io) are already placed in this repository.
+If you are new to the concept of devcontainers in combination with VSCode [here](https://code.visualstudio.com/docs/remote/containers) is a good article about it.
+
+Simply clone this repository and VSCode will most likely ask you to open it in the devcontainer, if you have the correct extension("ms-vscode-remote.remote-containers") installed.
+If VSCode didn't ask to open it, open the command palette and use the `Remote-Containers: Rebuild and Reopen in Container` command.
+
+If you want to use Gitpod simply use this [link](https://gitpod.io/#https://github.com/hyperledger/indy-node/tree/main)
+or if you want to work with your fork, prefix the entire URL of your branch with  `gitpod.io/#` so that it looks like `https://gitpod.io/#https://github.com/hyperledger/indy-node/tree/main`.
+
+**Note**: Be aware that the config files for Gitpod and VSCode are currently only used in the `main` branch!
 
 
 ## Continuous Integration and Delivery

docs/source/index.rst

@@ -22,7 +22,7 @@ Welcome to Hyperledger Indy Node's documentation!
    ci-cd.md
    indy-file-structure-guideline.md
    write-code-guideline.md
-   setup-dev.md
+