@servicetitan/docs-anvil-uikit-contrib 25.0.1-canary.0 → 25.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,35 @@
1
+ ---
2
+ id: backendless
3
+ title: Backendless
4
+ ---
5
+
6
+ Backendless lets you develop the frontend in the monolith app without running the backend.
7
+
8
+ ## Setup
9
+
10
+ 1. `cd` to your **app** project, then to `Clients/Web`
11
+ 2. Run `npm start`
12
+ 3. Run `npm run wwwroot` (admin or sudo rights are required to generate a trusted HTTPS certificate during the first run)
13
+ 4. In a browser, open https://next.servicetitan.com/manage (or any other current environment), and login with your ServiceTitan credentials.
14
+ 5. Open the developer console (**CTRL+Shift+J** on PC or **CMD+OPT+J** on Mac), and run `backendless.start()`
15
+ 6. The ST page should reload and you should now see the Backendless logo
16
+ 7. Have a happy development! 🙂
17
+
18
+ To deactivate Backendless, you can run `backendless.end()` or unregister the Backendless service worker via the developer tools.
19
+
20
+ *If you find any issues or have additional questions, please post them in the [#dev-backendless](https://servicetitan.slack.com/archives/C018D8C088L) Slack channel.*
21
+
22
+ ## Troubleshooting
23
+
24
+ ### WSL Certificate
25
+
26
+ If you are using WSL2 on Windows, and are running `npm run wwwroot` from within WSL, you may experience an issue with your browser in Windows not trusting the certificate that gets generated and used for localhost.
27
+
28
+ One solution is to run `npm run wwwroot` from Windows instead of WSL, so that the certificate will get correctly installed and trusted within Windows.
29
+
30
+ There is another, longer solution that will allow you to continue running the script from within WSL after some setup.
31
+ 1. Run `npm run wwwroot` within WSL first, so that WSL will know it generated a certificate already. Those certificates will likely be added to `/home/[UBUNTU_USERNAME]/.config/https-localhost/localhost.crt`.
32
+ 2. Run `npm run wwwroot` within Windows. This may require you cloning the repo again from Windows, and will require node to be installed on Windows. This will add certificates to `C:\Users\[USERNAME]\AppData\Roaming\https-localhost`.
33
+ 3. Copy the **localhost.crt** and **localhost.key** from `C:\Users\[username]\AppData\Roaming\https-localhost` to `/home/[UBUNTU_USERNAME]/.config/https-localhost/localhost.crt`. The WSL mount can be accessed from Windows via `\\wsl$\Ubuntu\home\[UBUNTU_USERNAME]]\.config\https-localhost\localhost.crt`.
34
+
35
+ From then on, you should be able to run `npm run wwwroot` directly from WSL with no issues, because it is serving using the certificate generated from Windows and Windows trusts that certificate.
package/package.json CHANGED
@@ -1,15 +1,13 @@
1
1
  {
2
2
  "name": "@servicetitan/docs-anvil-uikit-contrib",
3
- "version": "25.0.1-canary.0",
3
+ "version": "25.0.1",
4
4
  "description": "",
5
5
  "repository": {
6
6
  "type": "git",
7
7
  "url": "https://github.com/servicetitan/anvil-uikit-contrib.git",
8
8
  "directory": "packages/docs"
9
9
  },
10
- "files": [
11
- "docs"
12
- ],
10
+ "files": ["docs"],
13
11
  "publishConfig": {
14
12
  "access": "public"
15
13
  },
File without changes
File without changes