Consolidate Java/JS sections

sis0k0 · sis0k0 · commit d87855ba9239 · 2025-11-17T09:41:23.000+01:00
diff --git a/docs/10-intro.mdx b/docs/10-intro.mdx
@@ -22,8 +22,11 @@ In the navigation bar, you will notice some icons. Here are their meanings:
 ## Requirements
 
 * Google Chrome installed
-* GitHub account
-* Ensure your laptop can access GitHub and GitHub Codespaces (sometimes corporate VPNs block these sites!)
+* For GitHub Codespaces
+    * GitHub account
+    * Ensure your laptop can access GitHub and GitHub Codespaces (sometimes corporate VPNs block these sites!)
+* Alternatively, for Instruqt
+    * Ensure your laptop can access the [Instruqt lab environment](https://mdb.link/instruqt-library).
 
 ## Hardware requirements
 
diff --git a/docs/50-demo-app/2-start-app.mdx b/docs/50-demo-app/2-start-app.mdx
@@ -41,16 +41,11 @@ Let it run for a few minutes as it prepares your environment. It will clone the
 Again, this might take a few minutes. It's a great time to grab a coffee. ☕️
 :::
 
-### Access the library website
-
-Once the environment loads, you may see the following warning:
-
-<Screenshot url="https://github.com/mongodb-developer/library-management-system" src="img/screenshots/50-demo-app/2-start-app/7-visit-page.png" alt="A warning in the codespace saying 'You are about to access a development port served by someone's codespace'" />
-
-You're seeing this warning because the development server is running on a publicly forwarded port, and GitHub shows a security notice anytime someone accesses a public port. Even in your own codespace, GitHub displays it just to confirm you intended to open that external-facing URL.
+Once the command finishes, the application will be running on port 5400.
 
-Click "Continue" to load the library application website. Once it loads, you're ready to move on to the next step.
+In the *Terminal* tab at the bottom, look for the line `Server is running on port: 5400`. If it appears, the Node.js API for the library application is up and ready to serve requests.
 
+<Screenshot url="https://github.com/mongodb-developer/library-management-system" src="img/screenshots/50-demo-app/3-configure/1-running.png" alt="The terminal panel" />
 
 </TabItem>
 
@@ -69,47 +64,33 @@ Let it run for a few seconds as it prepares your environment. It will clone the
 Again, this might take a few minutes. It's a great time to grab a coffee. ☕️
 :::
 
-<Screenshot url="https://github.com/mongodb-developer/library-management-system" src="img/screenshots/50-demo-app/2-start-app/2-codespace-java.png" alt="The codespace" />
+Once the command finishes, the application will be up and running on port 5400.
 
-:::warning
-Right now, you should see an error message in the console, as we haven't configured the app yet. Don't worry, you'll get it up and running in a few minutes.
-:::
-
-### Set the MongoDB connection
-To run the application in GitHub Codespaces, you now need to set the MongoDB connection string before starting the server.
-In the terminal of your Codespace, run:
-```
-export MONGODB_URI="<YOUR_CONNECTION_STRING>"
-```
-After setting the environment variable, start the application again with:
-```
-mvn spring-boot:run
-```
+<Screenshot url="https://github.com/mongodb-developer/library-management-system" src="img/screenshots/50-demo-app/2-start-app/6-app-started.png" alt="App is started on port 5000" />
 
-<Screenshot url="https://github.com/mongodb-developer/library-management-system" src="img/screenshots/50-demo-app/2-start-app/5-set-environments.png" alt="Set environment variable" />
-Once the command finishes, the application will be up and running on port 5000.
+</TabItem>
+</Tabs>
 
-<Screenshot url="https://github.com/mongodb-developer/library-management-system" src="img/screenshots/50-demo-app/2-start-app/6-app-started.png" alt="App is started on port 5000" />
+### Access the library website
 
-### Expose the server port
+Once the environment loads, you may see the following warning:
 
-To get the application working in that environment, there is one small change you need to make to the codespace. You need to expose the port where the server is running.
+<Screenshot url="https://github.com/mongodb-developer/library-management-system" src="img/screenshots/50-demo-app/2-start-app/7-visit-page.png" alt="A warning in the codespace saying 'You are about to access a development port served by someone's codespace'" />
 
-Look for the *Ports* tab at the bottom of the IDE.
+You're seeing this warning because the development server is running on a publicly forwarded port, and GitHub shows a security notice anytime someone accesses a public port. Even in your own codespace, GitHub displays it just to confirm you intended to open that external-facing URL.
 
-<Screenshot url="https://github.com/mongodb-developer/library-management-system" src="img/screenshots/50-demo-app/2-start-app/3-ports.png" alt="The Ports tab" />
+Click "Continue" to load the library application website. 
 
-Once you click on the tab, you'll see a list of ports. Right-click on the port `Server (5000)` row. Then, select "Port Visibility" and "Public."
+<Screenshot url="https://github.com/mongodb-developer/library-management-system" src="img/screenshots/50-demo-app/3-configure/2-reload.png" alt="The refresh icon" />
 
-<Screenshot url="https://github.com/mongodb-developer/library-management-system" src="img/screenshots/50-demo-app/2-start-app/4-port-visibility.png" alt="The Port Visibility menu" />
+You should see the application with some books listed now.
 
-You'll see the text in the *Visibility* column change to `Public`.
+### Open the client in a new window
 
-That's it! You're now ready to move to the next section.
+If you accidentally close the Client or want to open it in a separate tab/window go to the Ports tab, hover over Client and a world icon should appear. Click it and the client will open in a new tab.
 
+<Screenshot url="https://github.com/mongodb-developer/library-management-system" src="img/screenshots/50-demo-app/3-configure/open-client.png" alt="Click to open the client app" />
 
-</TabItem>
-</Tabs>
 
 ## 🦸 Option 3: Run locally
 
@@ -163,10 +144,10 @@ npm start
 <TabItem value="java" label="☕️ Java Spring Boot">
 
 1. Before starting the backend, switch to the java-server project.
-```
+    ```
     git checkout java-server
-```
-This command moves you into the correct project folder that contains the Java backend code.
+    ```
+    This command moves you into the correct project folder that contains the Java backend code.
 
 2. Set the MongoDB connection string as an environment variable:
    - On Linux / macOS:
diff --git a/docs/50-demo-app/3-configure.mdx b/docs/50-demo-app/3-configure.mdx
diff --git a/docs/50-demo-app/3-explore.mdx b/docs/50-demo-app/3-explore.mdx
@@ -0,0 +1,15 @@
+import Screenshot from "@site/src/components/Screenshot";
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+# 👐 Explore the Dataset
+
+Now that your environment is set up, you can explore it.
+
+## Local MongoDB instance
+
+The database you'll be using in this exercise is a local MongoDB Atlas deployment running inside the codespace's sandbox.
+
+To explore the database and the imported dataset, click the leaf icon on the left sidebar to open the MongoDB extension. You’ll see a preset connection called **"Library DB"**. Expand it and browse the collections in the **library** database.
+
+You can open the pre-loaded documents in the collections. For example, expand the `books` collection and open a document of your choice. This will open a JSON preview of the document in the editor. You can even edit the document in the editor - saving the file will update the document in the database.
diff --git a/docs/60-schema-validation/2-validate-users.mdx b/docs/60-schema-validation/2-validate-users.mdx
@@ -6,26 +6,12 @@ import TabItem from '@theme/TabItem';
 
 In this exercise, you will explore the pre-written JSON validation schema for the `users` collection, run a script to apply it to the collection, and test the schema validation by inserting a document that does not match the schema.
 
-## Database user permissions
-
-To update the validator for any database collection, your database user must have admin privileges. Follow these steps to ensure your user has the correct permissions:
-
-1. Open the [Atlas UI](https://cloud.mongodb.com?utm_campaign=devrel&utm_source=workshop&utm_medium=cta&utm_content=developer.day&utm_term=project.phoenix).
-2. In the left-hand menu, navigate to **Network Settings** and select "Database Access."
-3. Locate your database user in the list. Check the **MongoDB Roles** column for the role of the user you are using for this workshop. If the role is not **atlasAdmin@admin**, you will need to update it.
-4. If the role is not **atlasAdmin@admin**, click "Edit" button next to the user.
-5. Scroll down to the **Database User Privileges** section and expand the **Built-in Role** dropdown.
-6. Select "Atlas admin" from the dropdown menu.
-7. Click "Update User" to save the changes.
-
-Atlas will deploy the change in a few seconds.
-
 ## Explore the JSON schema
 
 <Tabs groupId="server">
 <TabItem value="node" label="🚀 NodeJS/Express">
 
-The JSON schema for the `users` collection is stored in the `server/src/schema-validation/apply-schema.ts` [file](https://github.com/mongodb-developer/library-management-system/blob/main/server/src/schema-validation/apply-schema.ts). Open the file in your GitHub codespace and examine the schema.
+The JSON schema for the `users` collection is stored in the `server/src/schema-validation/apply-schema.ts` [file](https://github.com/mongodb-developer/library-management-system/blob/main/server/src/schema-validation/apply-schema.ts). Open the file and examine the schema.
 
 </TabItem>
 
diff --git a/docs/70-indexing/1-create-compound-index.mdx b/docs/70-indexing/1-create-compound-index.mdx
@@ -139,12 +139,9 @@ As soon as the application starts, you will see log entries showing the creation
 
 ## Verify that the index is created
 
-1. Open the **VS Code extension** (leaf icon) from the sidebar on the left.
-1. Click **Add Connection**.
-1. In the welcome screen, click **Connect** under the **Connect with Connection String** section.
-1. Enter the MongoDB connection string from your Atlas cluster, making sure to replace the **password placeholder**.
-1. Press **Enter**.
-1. In the sidebar, you should now see your database. Expand the **library** database, then the **issueDetails** collection, and finally select **Indexes**.
+1. Open the **MongoDB extension** (leaf icon) from the sidebar on the left.
+1. Click on **Library DB** to connect to the local MongoDB Atlas deployment.
+1. Expand the **library** database, then the **issueDetails** collection, and finally select **Indexes**.
 
 <Screenshot url="https://github.com/mongodb-developer/library-management-system" src="img/screenshots/70-indexing/2-index-vscode.png" alt="VS Code Extension showing the collection indexes" />
 
