You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/Deploy.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,9 +13,9 @@ React-admin is a framework to build [Single Page Applications](https://developer
13
13
14
14
**Warning**: If you chose Next.js or Remix, you **have to use a dynamic web server** (e.g. CloudFlare pages, Vercel, etc.).
15
15
16
-
With the default configuration of React-admin, that you can have using [`create-react-admin`](./CreateReactAdmin.md), you are already configured to run `yarn build` or `npm run build` to compile your application with [`vite`](https://vite.dev).
16
+
With the default configuration of React-admin, that you can have using [`create-react-admin`](./CreateReactAdmin.md), you can run `yarn build` or `npm run build` to compile your application with [`vite`](https://vite.dev).
17
17
18
-
This builds your application in the `dist` directory in application root. Let's have a look to what's in there:
18
+
This builds your application in the `dist` directory at the application root. Let's have a look to what's in there:
19
19
20
20
```tree
21
21
dist/
@@ -28,7 +28,7 @@ dist/
28
28
29
29
As you can see, your app is contained in a single Javascript file, used in a simple `index.html`. To deploy your application, you just need to serve this directory with all URLs handled by `index.html`.
30
30
31
-
There are multiple easy ways to deploy your app automatically to various hosts which does not require you to setup a web server manually. Some of these are addressed in this page.
31
+
There are multiple ways to deploy your app automatically to various hosts which does not require you to setup a web server manually. Some of these are addressed in this page.
32
32
33
33
## Deploy With GitHub Actions And GitHub Pages
34
34
@@ -95,9 +95,9 @@ This workflow will run everytime you push or merge something in the main branch
95
95
96
96
## Deploy With GitHub Actions to Cloudflare
97
97
98
-
To deploy to [Cloudflare Pages](https://pages.cloudflare.com/), you will need to have a [Cloudflare](https://www.cloudflare.com/) account. First you will need to retrieve your account ID from Cloudflare, the documentation on how to retrieve it is available on the [Cloudflare documentation](https://developers.cloudflare.com/fundamentals/account/find-account-and-zone-ids/)
98
+
To deploy to [Cloudflare Pages](https://pages.cloudflare.com/), you need to have a [Cloudflare](https://www.cloudflare.com/) account. First, retrieve your account ID from Cloudflare, the documentation on how to retrieve it is available on the [Cloudflare documentation](https://developers.cloudflare.com/fundamentals/account/find-account-and-zone-ids/)
99
99
100
-
Then, you will need to create a new API token from your [Cloudflare Profile page](https://dash.cloudflare.com/profile/api-tokens):
100
+
Then, create a new API token from your [Cloudflare Profile page](https://dash.cloudflare.com/profile/api-tokens):
101
101
- First click on `Create Token`
102
102
- Then on the `Edit Cloudflare Workers` template
103
103
- Select your organization inside the `Account Resources`
0 commit comments