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/how-to/websites-on-ipfs/deploy-github-action.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ The IPFS Deploy Action makes no assumptions about your build process. Whether yo
33
33
Before you begin, make sure you have:
34
34
35
35
1. A GitHub repository with your static web application
36
-
2. A [Storacha](https://storacha.network) account or an IPFS Node (Kubo or IPFS Cluster) with the RPC endpoint publicly reachable (see [this guide](../how-to/kubo-rpc-tls-auth.md) for instructions on how to secure the Kubo RPC endpoint with TLS and authentication)
36
+
2. A [Storacha](https://storacha.network) account or an IPFS Node (Kubo or IPFS Cluster) with the RPC endpoint publicly reachable (see [this guide](../kubo-rpc-tls-auth.md) for instructions on how to secure the Kubo RPC endpoint with TLS and authentication)
37
37
38
38
This guide will use Storacha for simplicity. If you have an IPFS Node, you can skip the Storacha setup and use your own node instead.
39
39
@@ -268,7 +268,7 @@ Your site will be accessible through:
268
268
2. Set up proper caching for your dependencies to speed up builds
269
269
3. Consider using multiple IPFS providers for redundancy
270
270
4. Use environment-specific configurations when needed
0 commit comments