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: src/content/docs/client/upgrade.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ This upgrade method will only work if your repository is a fork!
20
20
:::
21
21
22
22
<Steps>
23
-
1. If you have not already, click [here](https://github.com/xp-technologies-dev/p-stream/fork) to fork the P-Stream Github repository.
23
+
1. If you have not already, click [here](https://github.com/jenish094/p-stream/fork) to fork the P-Stream Github repository.
24
24
25
25
2. Paste the below file into your repository's root `/.github/workflows` directory
26
26
@@ -62,7 +62,7 @@ Your instance should now be automatically updated to the latest version.
62
62
You can manually update by executing the following commands in the root directory of the repository you have created, you would have to do this every time a push occurs to stay up-to-date:
@@ -75,6 +75,6 @@ git push -f # Force push to your origin main branch
75
75
76
76
You will need the latest version of the proxy worker. Redeploy a new worker using [our self-hosting guide](/pstream-docs/proxy/deploy).
77
77
78
-
After you have the new worker, you will need to [get the new P-Stream deployment files](https://github.com/p-stream/xp-technologies-dev/releases/latest). **You CANNOT use the non-PWA version**. To upgrade safely without any complications, you need to update with `P-Stream.pwa.zip`, Not the non-PWA version.
78
+
After you have the new worker, you will need to [get the new P-Stream deployment files](https://github.com/p-stream/jenish094/releases/latest). **You CANNOT use the non-PWA version**. To upgrade safely without any complications, you need to update with `P-Stream.pwa.zip`, Not the non-PWA version.
79
79
80
80
In the future, you will **ALWAYS** need to go with the PWA option. You cannot downgrade to non-PWA version without facing many caching complications.
@@ -57,7 +57,7 @@ This method is for advanced users who want full control over their deployment. W
57
57
Manually installing the proxy on your server. You may want to use an automated package manager like nixpacks to do this.
58
58
59
59
<Steps>
60
-
1. Clone the repo on your server `git clone https://github.com/xp-technologies-dev/simple-proxy`
60
+
1. Clone the repo on your server `git clone https://github.com/jenish094/simple-proxy`
61
61
62
62
2. Navigate to the directory `cd simple-proxy`
63
63
@@ -82,7 +82,7 @@ You'll need to configure port forwarding and firewall settings. Good luck.
82
82
83
83
Cloudflare has a generous free plan, so you don't need to pay anything unless you get thousands of users.
84
84
85
-
[](https://deploy.workers.cloudflare.com/?url=https://github.com/xp-technologies-dev/simple-proxy)
85
+
[](https://deploy.workers.cloudflare.com/?url=https://github.com/jenish094/simple-proxy)
86
86
87
87
<Steps>
88
88
1. Create a GitHub account at https://github.com if you don't have one.
@@ -112,7 +112,7 @@ Cloudflare has a generous free plan, so you don't need to pay anything unless yo
112
112
113
113
Netlify has a very generous free plan, so you'll be able to host your proxy for free unless you get hundreds of users.
114
114
115
-
[](https://app.netlify.com/start/deploy?repository=https://github.com/xp-technologies-dev/simple-proxy)
115
+
[](https://app.netlify.com/start/deploy?repository=https://github.com/jenish094/simple-proxy)
116
116
117
117
<Steps>
118
118
1. Create a GitHub account at https://github.com/signup if you don't have one already.
0 commit comments