redis-smq-web-ui 9.0.0-next.17 → 9.0.0-next.18

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.
@@ -14,7 +14,7 @@
14
14
  <link rel="icon" href="./favicon.ico" />
15
15
  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
16
16
  <title>RedisSMQ Web UI</title>
17
- <script type="module" crossorigin src="./assets/index-DI_TzeXY.js"></script>
17
+ <script type="module" crossorigin src="./assets/index-CQF1KVB2.js"></script>
18
18
  <link rel="stylesheet" crossorigin href="./assets/index-CfNyRs3J.css">
19
19
  </head>
20
20
  <body>
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "redis-smq-web-ui",
3
- "version": "9.0.0-next.17",
3
+ "version": "9.0.0-next.18",
4
4
  "description": "Web UI for RedisSMQ: monitor and manage queues, messages, and consumers.",
5
5
  "author": "Weyoss <weyoss@protonmail.com>",
6
6
  "license": "MIT",
@@ -45,7 +45,7 @@
45
45
  "./package.json": "./package.json"
46
46
  },
47
47
  "peerDependencies": {
48
- "redis-smq-common": "^9.0.0-next.17"
48
+ "redis-smq-common": "^9.0.0-next.18"
49
49
  },
50
50
  "dependencies": {
51
51
  "@vee-validate/zod": "4.15.1",
@@ -76,9 +76,9 @@
76
76
  "vite-plugin-node-polyfills": "0.24.0",
77
77
  "vite-plugin-vue-devtools": "8.0.2",
78
78
  "vue-tsc": "3.1.1",
79
- "redis-smq": "^9.0.0-next.17",
80
- "redis-smq-rest-api": "^9.0.0-next.17",
81
- "redis-smq-common": "^9.0.0-next.17"
79
+ "redis-smq": "^9.0.0-next.18",
80
+ "redis-smq-rest-api": "^9.0.0-next.18",
81
+ "redis-smq-common": "^9.0.0-next.18"
82
82
  },
83
83
  "scripts": {
84
84
  "dev": "run-p run-dev-server run-api-server",
package/docs/README.md DELETED
@@ -1,63 +0,0 @@
1
- [RedisSMQ Web UI](../README.md) / Documentation
2
-
3
- # RedisSMQ Web UI - Documentation
4
-
5
- ## Quick start
6
-
7
- Use the [RedisSMQ Web Server](/packages/redis-smq-web-server/README.md) to serve the UI and either mount the REST API in-process or proxy to an external instance.
8
-
9
- - In-process API (default):
10
- - UI at http://localhost:8080/
11
- - API at http://localhost:8080/api
12
- - Proxy to an external REST API:
13
- - UI is served locally
14
- - API/docs/assets are forwarded to the upstream API
15
-
16
- Examples:
17
-
18
- ```bash
19
- # Default (UI at /, API at /api)
20
- npx redis-smq-web-server
21
-
22
- # Serve under a sub-path (e.g., behind a reverse proxy)
23
- npx redis-smq-web-server --base-path /redis-smq
24
-
25
- # Proxy API/docs/assets to an external REST API
26
- npx redis-smq-web-server --api-proxy-target http://127.0.0.1:7210
27
- ```
28
-
29
- See [RedisSMQ Web Server](/packages/redis-smq-web-server/README.md) for CLI options such as:
30
-
31
- - `--port`
32
- - `--base-path`
33
- - `--api-proxy-target`
34
- - Redis connection and logging options (used only when hosting the API in-process)
35
-
36
- ## Configuration and routing
37
-
38
- - Base path
39
- - When served by [RedisSMQ Web Server](/packages/redis-smq-web-server/README.md), basePath controls where the UI and local API/docs are mounted.
40
- - Examples:
41
- - basePath = / → UI at /, API at /api, Swagger UI at /docs
42
- - basePath = /redis-smq → UI at /redis-smq, API at /redis-smq/api, Swagger UI at /redis-smq/docs
43
-
44
- - API endpoint
45
- - With an embedded API (no proxy): the server mounts the REST API alongside the UI under <basePath>/api.
46
- - With a proxy target: the server forwards <basePath>/api, <basePath>/docs, and <basePath>/assets to the configured upstream URL.
47
-
48
- - Standalone/static hosting (advanced)
49
- - If hosting the UI assets yourself:
50
- - Serve the SPA with history fallback (so client-side routes work on refresh).
51
- - Ensure the public base path matches where you host the app.
52
- - Proxy API requests to the REST API under the same public base path (e.g., <basePath>/api).
53
- - Expose <basePath>/docs and <basePath>/assets if you want Swagger UI and API schema accessible.
54
- - Note: [RedisSMQ Web Server](/packages/redis-smq-web-server/README.md) already handles these concerns and is the simplest path.
55
-
56
- ## Deploying behind a reverse proxy
57
-
58
- - Set a public sub-path using the web server’s --base-path (e.g., `/redis-smq`).
59
- - Forward both the UI and API prefixes through your proxy:
60
- - `/redis-smq` → web server
61
- - If proxying the API to an external service, combine with --api-proxy-target:
62
- - Client → reverse proxy → web server (`/redis-smq`)
63
- - Web server proxies `/redis-smq/api`, `/redis-smq/swagger` → external API
Binary file