Skip to content

Commit eef0c0a

Browse files
committed
Adjustments
1 parent 49485c3 commit eef0c0a

File tree

2 files changed

+4
-30
lines changed

2 files changed

+4
-30
lines changed

docs/advanced.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -241,9 +241,9 @@ jobs:
241241
# Bring up stack and run healthchecks
242242
trap 'docker compose down' ERR
243243
docker compose up --detach
244-
docker compose exec -T caddy curl -fsS http://caddy:80/healthcheck
244+
docker compose exec -T caddy curl -fsS http://caddy:80/healthz
245245
# Add more healthchecks here
246-
# docker compose exec -T caddy curl -fsS http://api:8080/healthcheck
246+
# docker compose exec -T caddy curl -fsS http://api:8080/healthz
247247
# docker compose exec -T caddy curl -fsS http://postgrest:3000/
248248
249249
- name: Flip traffic

docs/gettingstarted.md

Lines changed: 2 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,6 @@ installed](https://docs.docker.com/get-docker/) before you begin.
1414

1515
## 1. Get SuperStack
1616

17-
### Option 1: Use the Template (Easiest)
18-
1917
Click [Use this template](https://github.com/explodinglabs/superstack/generate)
2018
and create a new repository (e.g. `myapp-backend`) on GitHub.
2119

@@ -26,30 +24,6 @@ git clone https://github.com/yourname/myapp-backend.git
2624
cd myapp-backend
2725
```
2826

29-
### Option 2: Clone and Track Upstream (Advanced)
30-
31-
If you want to keep SuperStack’s Git history and pull upstream changes later,
32-
clone SuperStack:
33-
34-
```sh
35-
git clone https://github.com/explodinglabs/superstack.git myapp-backend
36-
cd myapp-backend
37-
```
38-
39-
[Create your own repo](https://github.com/new), then:
40-
41-
```sh
42-
git remote rename origin upstream
43-
git remote add origin https://github.com/yourname/myapp-backend.git
44-
git push -u origin main
45-
```
46-
47-
You can now pull upstream changes with:
48-
49-
```sh
50-
git pull upstream main
51-
```
52-
5327
## 2. Configure Environment Variables
5428

5529
Copy the example environment file:
@@ -69,12 +43,12 @@ The `.env` file is used to set secrets, passwords, keys, etc.
6943
docker compose up -d
7044
```
7145

72-
That's it – your backend is live.
46+
That's it – your backend is ready for development.
7347

7448
Test it with:
7549

7650
```sh
77-
$ curl http://localhost:8000/healthcheck
51+
$ curl http://localhost:8000/healthz
7852
OK
7953
```
8054

0 commit comments

Comments
 (0)