fix: Update CLI Commands in Python, Go, and Next.js (#700)

Signed-off-by: Achanandhi-M <[email protected]>

Author: Achanandhi-M

src/components/QuickStartList.js

@@ -299,7 +299,7 @@ const quickstarts = [
   },
 
   {
-    title: "NextJS + SQL",
+    title: "NextJS + Postgres",
     language: "JS/TS",
     server: "Local",
     description:

versioned_docs/version-2.0.0/quickstart/nextjs-postgres.md

@@ -1,7 +1,7 @@
 ---
 id: samples-nextjs
 title: NextJs Sample Application
-sidebar_label: NextJS + SQL
+sidebar_label: NextJS + PostgreSQL
 description: The following sample app to test Keploy integration capabilities using NextJS,Drizzle and Postgres.
 tags:
   - NextJs

versioned_docs/version-3.0.0/quickstart/go-fasthttp-postgres.md

@@ -234,8 +234,6 @@ keploy record -c "./app"
 Keep an eye out for the `-c` flag! It's the command charm to run the app. Whether you're using `go run main.go` or the binary path like `./app`, it's your call.
 If you're seeing logs that resemble the ones below, you're on the right track:
 
-![Testcase](/img/fasthttp-postgress-test.png)
-
 Alright! With the app alive and kicking, let's weave some test cases. Making some API calls! Postman, Hoppscotch,
 
 or even the classic curl - take your pick!

versioned_docs/version-3.0.0/quickstart/nextjs-postgres.md

@@ -1,7 +1,7 @@
 ---
 id: samples-nextjs
 title: NextJs Sample Application
-sidebar_label: NextJS + SQL
+sidebar_label: NextJS + PostgreSQL
 description: The following sample app to test Keploy integration capabilities using NextJS,Drizzle and Postgres.
 tags:
   - NextJs

versioned_docs/version-3.0.0/quickstart/python-fastapi-twilio.md

@@ -59,7 +59,7 @@ docker build -t fastapi-twilio:1.0 .
 Capture the test-cases-
 
 ```shell
-keploy record -c "docker run -p 8000:8000 --name fastapi-twilio fastapi-twilio:1.0"
+keploy record -c "docker run -p 8000:8000 --name fastapi-twilio --network keploy-network fastapi-twilio:1.0"
 ```
 
 🔥**Make some API calls**. Postman, Hoppscotch or even curl - take your pick!
@@ -222,7 +222,7 @@ Want to see if everything works as expected?
 Time to put things to the test 🧪
 
 ```shell
-keploy test -c "docker run -p 8000:8000 --name fastapi-twilio fastapi-twilio:1.0" --delay 10
+keploy test -c "docker run -p 8000:8000 --name fastapi-twilio --network keploy-network fastapi-twilio:1.0" --delay 10
 ```
 
 > The `--delay` flag? Oh, that's just giving your app a little breather (in seconds) before the test cases come knocking.

versioned_docs/version-3.0.0/quickstart/samples-echo.md

@@ -46,12 +46,6 @@ Using the docker-compose file we will start our postgres instance:-
 docker compose up
 ```
 
-#### Creating Docker Volume
-
-```bash
-docker volume create --driver local --opt type=debugfs --opt device=debugfs debugfs
-```
-
 ### Capture the Testcases
 
 Now, we will create the binary of our application:-
@@ -159,12 +153,12 @@ Using the docker-compose file we will start our Postgres instance:-
 docker-compose up -d
 ```
 
-> **Since we are using docker to run the application, we need to update the `postgres` host on line 28 in `main.go`, update the host to `localhost`.**
+> **Since we are using docker to run the application, we need to update the `postgres` host on line 40 in `main.go`, update the host to `localhost`.**
 
 Now, we will create the binary of our application:-
 
 ```go
-go build -cover
+go build echo-psql-url-shortener
 ```
 
 ### Capture the Testcases
@@ -173,8 +167,6 @@ go build -cover
 sudo -E PATH=$PATH keploy record -c "./echo-psql-url-shortener"
 ```
 
-![Testcase](/img/echo-postgress-run-testcase.png?raw=true)
-
 ### Generate testcases
 
 To genereate testcases we just need to make some API calls. You can use Postman, Hoppscotch, or simply curl
@@ -214,7 +206,7 @@ Now both these API calls were captured as a testcase and should be visible on th
 Now that we have our testcase captured, run the test file.
 
 ```shell
-sudo -E PATH=$PATH keploy record -c "./echo-psql-url-shortener" --delay 10
+sudo -E PATH=$PATH keploy test -c "./echo-psql-url-shortener"
 ```
 
 So no need to setup dependencies like mongoDB, web-go locally or write mocks for your testing.

versioned_docs/version-3.0.0/quickstart/samples-go-gin-mongo.md

@@ -252,9 +252,7 @@ keploy record -c "go run main.go handler.go"
 Keep an eye out for the `-c `flag! It's the command charm to run the app. Whether you're using `go run main.go handler.go` or the binary path like `./test-app-url-shortener`, it's your call.
 If you're seeing logs that resemble the ones below, you're on the right track:
 
-   <img src="/docs/img/code-snippets/keploy-record-docker.png" alt="Keploy Record Test case" width="100%" />
-  
-  Alright! With the app alive and kicking, let's weave some test cases. Making some API calls! Postman, Hoppscotch, or the classic curl - pick your wand.
+Alright! With the app alive and kicking, let's weave some test cases. Making some API calls! Postman, Hoppscotch, or the classic curl - pick your wand.
 
 #### Generate shortened url
 
@@ -386,8 +384,6 @@ keploy test -c "docker compose up" --container-name "ginMongoApp" --delay 10
 
 Your results should be looking all _snazzy_, like this:
 
-<img src="/docs/img/code-snippets/url-shortner-test-result.png" alt="Sample Keploy Test Result Gin MongoDB" width="100%" style={{ borderRadius: '5px' }}/>
-
 Did you spot that, the ts (timestamp) is showing some differences? Yep, time has a way of doing that! 🕰️
 
 Worry not, just add the ever-changing fields (like our **ts** here) to the **noise parameter** to **dodge those assertions**.