Skip to content

Commit 0a17785

Browse files
committed
add instructions for local instance
1 parent da8c2c7 commit 0a17785

File tree

1 file changed

+12
-15
lines changed

1 file changed

+12
-15
lines changed

README.md

Lines changed: 12 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,17 @@
11
# DevRev Docs
22

3-
Tagging a release on this repository will update the following clients:
3+
Merging a change in this repository will update the following clients:
44

5-
- [API Docs](https://devrev.docs.buildwithfern.com)
6-
7-
## What is in this repository?
5+
- [API Docs](https://developer.devrev.ai)
86

97
This repository contains
108

119
- DevRev's `Public` OpenAPI spec & `Beta` OpenAPI spec
1210
- Fern configuration
1311

14-
## What is in the API Definition?
12+
## API definition
1513

16-
The API Definition contains an OpenAPI specification adapted to be compatible with Fern.
14+
The API Definition contains an OpenAPI specification adapted to be compatible with Fern. The specs are in `/fern/apis`.
1715

1816
To make sure that the definition is valid, you can use the Fern CLI.
1917

@@ -22,9 +20,9 @@ npm install -g fern-api # Installs CLI
2220
fern check # Checks if the definition is valid
2321
```
2422

25-
## What are generators?
23+
## Generators
2624

27-
Generators read in your API Definition and output artifacts (e.g. the TypeScript SDK Generator) and are tracked in [generators.yml](./fern/api/generators.yml).
25+
Generators read in your API Definition and output artifacts (the TypeScript SDK Generator) and are tracked in [generators.yml](./fern/api/generators.yml).
2826

2927
To trigger the generators run:
3028

@@ -33,15 +31,14 @@ To trigger the generators run:
3331
fern generate --version <version>
3432
```
3533

36-
## Upgrading Fern
37-
You can use the following command to upgrade fern to the latest version:
38-
```bash
39-
fern upgrade --rc
34+
## Run a local instance
35+
36+
In the root of this repository:
37+
```
38+
cd custom-implementation/ && npm i && npm run build && cd ..
39+
fern docs dev
4040
```
4141

4242
### Troubleshooting
4343

4444
If you run into errors, you can add the ` --log-level debug` flag to get more information.
45-
46-
If you get a 403 error, you may need to first run `fern login`. You might also need to be added
47-
to the Vellum org in Fern, which requires contacting the fern team in #fern-x-vellum in Slack.

0 commit comments

Comments
 (0)