@@ -81,20 +81,20 @@ Over time, we should track which items are useful and which don't get any traffi
81
81
82
82
## Installation and setup
83
83
84
- 1 . Use Git to clone this repository.
85
- 1 . Go to GitHub and navigate to [ Settings / Personal access tokens / Tokens (classic) ] ( https://github.com/settings/tokens ) .
86
- Despite the UI suggesting you should use the new fine-grained tokens, generate a ** classic token ** with scopes ** repo ** and ** write : packages ** .
87
- Keep the token somewhere safe .
88
- Then run the following command and use your GitHub username together with the token as credentials:
89
- ```
90
- npm login --scope=@apify-packages --registry=https://npm.pkg.github.com --auth-type=legacy
91
- ```
92
-
93
- > [!IMPORTANT]
94
- > Read [#909](https://github.com/apify/apify-docs/issues/909) to understand why this is needed.
95
- > If you work at Apify and can install packages prefixed with `@apify-packages`, you can skip this step .
96
- 1. Run `npm install`.
97
- 1. Run `npm start`. The website should open at <http://localhost:3000>.
84
+ 1 . Use Git to clone this repository.
85
+ 2 . If you work at Apify and can install packages prefixed with ` @apify-packages ` , you can skip this step .
86
+ Otherwise go to GitHub and navigate to [ Settings / Personal access tokens / Tokens ( classic) ] ( https://github.com/settings/tokens ) .
87
+ Despite the UI suggesting you should use the new fine-grained tokens, generate a ** classic token** with scopes ** repo ** and ** write : packages ** .
88
+ Keep the token somewhere safe.
89
+ Then run the following command and use your GitHub username together with the token as credentials:
90
+
91
+ ``` bash
92
+ npm login --scope=@apify-packages --registry=https://npm.pkg.github.com --auth-type=legacy
93
+ ```
94
+
95
+ Read [ # 909 ] ( https://github.com/apify/apify-docs/issues/909 ) if you want to understand why this is needed .
96
+ 3 . Run ` npm install ` .
97
+ 4 . Run ` npm start ` . The website should open at < http://localhost:3000 > .
98
98
99
99
This is sufficient to work on the main content, i.e. the Academy and Platform docs.
100
100
If you want to also work on the other parts of the docs, you may want to first join them all together using Nginx.
0 commit comments