|
7 | 7 |
|
8 | 8 | ## Contents
|
9 | 9 |
|
| 10 | +- [Config not saving](#config-not-saving) |
10 | 11 | - [Refused to Connect in Web Content View](#refused-to-connect-in-modal-or-workspace-view)
|
11 | 12 | - [404 On Static Hosting](#404-on-static-hosting)
|
12 | 13 | - [404 from Mobile Home Screen](#404-after-launch-from-mobile-home-screen)
|
|
45 | 46 |
|
46 | 47 | ---
|
47 | 48 |
|
| 49 | +## Config not saving |
| 50 | + |
| 51 | +### Possible Issue 1: Unable to call save endpoint from CDN/static server |
| 52 | +If you're running Dashy using a static hosting provider (like Vercel), then there is no Node server, and so the save config action will not work via the UI. |
| 53 | +You'll instead need to copy the YAML after making your changes, and paste that into your `conf.yml` directly. If you've connected Vercel to git, then these changes will take effect automatically, once you commit your changes. |
| 54 | +Look here for more information: [https://dashy.to/docs/deployment#deploy-to-cloud-service](https://dashy.to/docs/deployment#deploy-to-cloud-service) |
| 55 | + |
| 56 | +If you're running on Netlify, there are some cloud functions which take care of all the server endpoints (like status checking), so these will work as expected. |
| 57 | + |
| 58 | +See also [#1465](https://github.com/Lissy93/dashy/issues/1465) |
| 59 | + |
| 60 | +### Possible Issue 2: Unable to save |
| 61 | +In Docker, double check that the file isn't read-only, and that the container actually has permissions to modify it. You shouldn't really be running it as a root user, and I'm not sure if it will work if you do- |
| 62 | + |
| 63 | +### Possible Issue 3: Saved but not updating |
| 64 | +After saving, the frontend will recompile, which may take a couple seconds (or a bit longer on a Pi or low-powered device). If it doesn't recompile, you can manually trigger a re-build. |
| 65 | + |
| 66 | +--- |
| 67 | + |
48 | 68 | ## `Refused to Connect` in Modal or Workspace View
|
49 | 69 |
|
50 | 70 | This is not an issue with Dashy, but instead caused by the target app preventing direct access through embedded elements.
|
@@ -538,7 +558,7 @@ export NODE_OPTIONS=--openssl-legacy-provider
|
538 | 558 | ```
|
539 | 559 |
|
540 | 560 | For more info, see [webpack/webpack#14532](https://github.com/webpack/webpack/issues/14532) and [nodejs/node#40455](https://github.com/nodejs/node/issues/40455).
|
541 |
| -This occours because [Node 17+](https://medium.com/the-node-js-collection/node-js-17-is-here-8dba1e14e382) no longer supports MD4 as hash function, we're in the process of upgrading Dashy dependencies to all use SHA1 for hashing bundle IDs. |
| 561 | +This occurs because [Node 17+](https://medium.com/the-node-js-collection/node-js-17-is-here-8dba1e14e382) no longer supports MD4 as hash function, we're in the process of upgrading Dashy dependencies to all use SHA1 for hashing bundle IDs. |
542 | 562 |
|
543 | 563 | ---
|
544 | 564 |
|
|
0 commit comments