Skip to content

Commit b810a76

Browse files
committed
linting and fixes
1 parent 4cd89fb commit b810a76

File tree

2 files changed

+8
-9
lines changed

2 files changed

+8
-9
lines changed

content/guides/use-case/pre-seeding.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -206,21 +206,21 @@ Make sure you stop any running Postgres containers (along with volumes) to preve
206206

207207
It is important to note that the port mapping to the host is only necessary if you want to connect to the database from non-containerized programs. If you containerize the service that connects to the DB, you should connect to the database over a custom bridge network.
208208

209-
3. Bring up the Compose service.
209+
4. Bring up the Compose service.
210210

211211
Assuming that you've placed the `seed.sql` file in the same directory as the Dockerfile, execute the following command:
212212

213213
```console
214214
$ docker compose up -d --build
215215
```
216216

217-
4. It’s time to verify if the table `users` get populated with the data.
217+
5. It’s time to verify if the table `users` get populated with the data.
218218

219219
```console
220220
$ docker exec -it my_postgres_db psql -h localhost -U postgres sampledb
221221
```
222222

223-
```
223+
```sql
224224
sampledb=# select * from users;
225225
id | name | email
226226
----+-------+-------------------
@@ -229,8 +229,8 @@ Make sure you stop any running Postgres containers (along with volumes) to preve
229229
3 | Gamma | [email protected]
230230
(3 rows)
231231
232-
sampledb=#
233-
```
232+
sampledb=#
233+
```
234234

235235

236236
## Pre-seeding the database using JavaScript code

content/guides/use-case/wiremock.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,7 @@ Follow the steps to setup a non-containerized Node application:
160160
```
161161
162162
163-
3. Start the Node server
163+
4. Start the Node server
164164
165165
Before you start the Node server, ensure that you have already installed the node packages listed in the package.json file by running `npm install`.
166166
@@ -183,7 +183,7 @@ Follow the steps to setup a non-containerized Node application:
183183
The output indicates that your Node application has successfully started.
184184
Keep this terminal window open.
185185
186-
4. Test the Mocked API
186+
5. Test the Mocked API
187187
188188
Open a new terminal window and run the following command to test the mocked API:
189189
@@ -204,11 +204,10 @@ Follow the steps to setup a non-containerized Node application:
204204
> [!TIP]
205205
> Before you proceed to the next step, ensure that you stop the node application service.
206206

207-
## Use a Live API in production to fetch real-time weather data from AccuWeather.
207+
## Use a Live API in production to fetch real-time weather data from AccuWeather
208208

209209
To enhance your Node.js application with real-time weather data, you can seamlessly integrate the AccuWeather API. This section of the guide will walk you through the steps involved in setting up a non-containerized Node.js application and fetching weather information directly from the AccuWeather API.
210210

211-
212211
1. Create an AccuWeather API Key
213212

214213
Sign up for a free AccuWeather developer account at[https://developer.accuweather.com/](https://developer.accuweather.com/). Within your account, create a new app by selecting `MY APPS` on the top navigation menu to get your unique API key.

0 commit comments

Comments
 (0)