File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -169,9 +169,9 @@ There are two types of fixtures that are used to test that migrations don't
169
169
break existing Coder deployments:
170
170
171
171
* Partial fixtures
172
- [ ` migrations/testdata/fixtures ` ] ( ../coderd/database/migrations/testdata/fixtures )
172
+ [ ` migrations/testdata/fixtures ` ] ( ../../ coderd/database/migrations/testdata/fixtures )
173
173
* Full database dumps
174
- [ ` migrations/testdata/full_dumps ` ] ( ../coderd/database/migrations/testdata/full_dumps )
174
+ [ ` migrations/testdata/full_dumps ` ] ( ../../ coderd/database/migrations/testdata/full_dumps )
175
175
176
176
Both types behave like database migrations (they also
177
177
[ ` migrate ` ] ( https://github.com/golang-migrate/migrate ) ). Their behavior mirrors
@@ -194,7 +194,7 @@ To add a new partial fixture, run the following command:
194
194
```
195
195
196
196
Then add some queries to insert data and commit the file to the repo. See
197
- [ ` 000024_example.up.sql ` ] ( ../coderd/database/migrations/testdata/fixtures/000024_example.up.sql )
197
+ [ ` 000024_example.up.sql ` ] ( ../../ coderd/database/migrations/testdata/fixtures/000024_example.up.sql )
198
198
for an example.
199
199
200
200
To create a full dump, run a fully fledged Coder deployment and use it to
You can’t perform that action at this time.
0 commit comments