Separate bb2 dev stuff from README.md

Author: dtisza1

README-bb2-dev.md

@@ -0,0 +1,30 @@
+# Blue Button 2.0 Sample Application Development Documentation
+
+## Introduction
+
+This README contains information related to developing the SDK.
+
+It is intended for BB2 team members or others performing sample application development work.
+
+## Run selenium tests in docker
+
+Configure the remote target BB2 instance where the tested app is registered (as described above "Running the Back-end & Front-end")
+
+Change your `callback_url` configuration to use `server` instead of `localhost`. For example:
+```JSON
+    "callback_url": "http://server:3001/api/bluebutton/callback/"
+```
+
+You will also need to add this URL to your `redirect_uris` list in your application's configuration on the BB2 Sandbox UI.
+
+Go to local repository base directory and run docker compose as below:
+
+docker-compose -f docker-compose.selenium.yml up --abort-on-container-exit
+
+Note: --abort-on-container-exit will abort client and server containers when selenium tests ends
+
+Note: You may need to clean up already existing Docker containers, if you are having issues or have changed your configuration file.
+
+## Visual trouble shoot
+
+Install VNC viewer and point browser to http://localhost:5900 to monitor web UI interactions

README.md

@@ -66,20 +66,6 @@ Debugging server component
 --------------------------
 debugpy remote debugging enabled on port 5678 for server in docker compose, developer can attach to server from IDE e.g. vscode.
 
-## Run selenium tests in docker
-
-Configure the remote target BB2 instance where the tested app is registered (as described above "Running the Back-end & Front-end")
-
-Go to local repository base directory and run docker compose as below:
-
-docker-compose -f docker-compose.selenium.yml up --abort-on-container-exit
-
-Note: --abort-on-container-exit will abort client and server containers when selenium tests ends
-
-## Visual trouble shoot
-
-Install VNC viewer and point browser to http://localhost:5900 to monitor web UI interactions
-
 Error Responses and handling:
 -----------------------------
 [See ErrorResponses.md](./ErrorResponses.md)