1
1
# How to hack on this
2
2
3
3
## Releasing Docs for new Telepresence Versions
4
- If you are only making changes to the ` docs/ ` directory and those changes
5
- aren't ready to go out immediately (for example, if they are for a future
6
- telepresence release), please make those changes in the
7
- [ telepresence repository] ( https://github.com/telepresenceio/telepresence ) .
8
-
9
- If you are making changes to more than the ` docs/ ` and those changes are
10
- for a future release, merge those changes into a branch ` rel/x.y.z ` .
11
-
12
- When it is time to do a telepresence release, the docs will be pushed to
13
- the [ docs repo] ( https://github.com/telepresenceio/docs ) . From there, you can
14
- create (or checkout if it already exists) a ` rel/x.y.z ` branch on this repo
15
- and run ` make pull-docs ` . Once you merge that PR, the website will update
16
- with the docs for the new release.
17
4
18
5
## Local development quickstart
19
6
@@ -29,10 +16,11 @@ Commands of interest:
29
16
yarn install # Install dependencies in to ./node_modules/
30
17
31
18
# Development
19
+ export NODE_OPTIONS=--openssl-legacy-provider
32
20
yarn run gatsby develop # Serve a hot-reloading development-build at http://localhost:8000/
33
21
yarn run gatsby repl # Run a Node.js REPL in the Gatsby environment
34
22
yarn run eslint . # Run the linter
35
- make pull-docs # Update ./docs/ from ambassador-docs .git
23
+ make pull-docs # Update ./docs/ from telepresenceio/telepresence .git
36
24
37
25
# Production or production-like
38
26
yarn run gatsby build # Build a production-build, writing it to ./public/
@@ -191,11 +179,10 @@ So we should upgrade Gatsby and associated plugins, and then turn
191
179
192
180
The docs-build machinery in of ` package.json ` , ` gatsby-config.js ` ,
193
181
` gatsby-node.js ` , ` src/assets/ ` and ` src/components/ ` seem obviously
194
- want be a separate reusable module, so that these things don't need to
195
- be manually kept in-sync between getambassador.io, telepresence.io,
196
- and emissaryingress.io. This seems to be mostly obvious an trival to
197
- do... except for I can't figure how to handle
198
- ` src/templates/doc-page.js ` to where it's sufficiently
182
+ want to be a separate reusable module, so that these things don't need to
183
+ be manually kept in-sync between telepresence.io, and telepresence.
184
+ This seems to be mostly obvious an trival to do... except for I can't
185
+ figure how to handle ` src/templates/doc-page.js ` to where it's sufficiently
199
186
parametarized/pluggable, or a way to make it possible to plug in the
200
187
site-specific one.
201
188
0 commit comments