gnoscope/Makefile at main · gnoverse/gnoscope · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
.PHONY: test e2e qa qa-report screenshots run install dev build awesome awesome-check

build:
	CGO_ENABLED=0 go build -o gnoscope .

run:
	CGO_ENABLED=0 go run .

install:
	CGO_ENABLED=0 go install .

test:
	go test ./...

# Browser tests. Separate from `test` because they need Node and a browser,
# which the binary never does — see e2e/README.md.
e2e:
	cd e2e && npm ci && npx playwright install --with-deps chromium && npx playwright test

# A QA and performance pass over a RUNNING deployment, by hand, not in CI.
# `test` and `e2e` answer "did this change break the code"; this answers "is
# every page still drawing on the real host, and has anything got slower".
# Every run is recorded under qa/results/ and qa-report pivots them into a
# table. See qa/README.md.
qa:
	cd e2e && npm ci
	node qa/run.mjs $(ARGS)

qa-report:
	node qa/report.mjs $(ARGS)

# Reproducible screenshots of every page, rendered against the e2e fixture into
# docs/images/review/. For reviewing a frontend change without checking the
# branch out — CI uploads them as artifacts on any PR touching pkg/web/frontend/.
#
# Not the README images: those come from scripts/screenshots.sh against a real
# database snapshot, because a README wants a chain with enough history to look
# like something and this wants to be identical run to run.
screenshots:
	cd e2e && npm ci && npx playwright install --with-deps chromium && npm run screenshots

dev:
	goloop . -- go run .

# Refreshes pkg/registry/data/awesome.json from gnoverse/awesome-gno, the
# community's own list of what is being built on gno.land. The snapshot is
# committed and embedded, so a build that cannot reach GitHub still builds and
# two readers a minute apart see the same page; the cost is that it is only as
# fresh as the last time somebody ran this. `awesome-check` answers whether it
# is behind, without writing, and ignores the synced date because that moves on
# its own. Neither is run by CI: a red build because somebody else edited their
# README is a build nobody here can fix.
awesome:
	go run ./cmd/awesome-sync

awesome-check:
	go run ./cmd/awesome-sync --check