moose-cli 0.5.23__py3-none-manylinux_2_28_aarch64.whl → 0.6.180__py3-none-manylinux_2_28_aarch64.whl
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.
Potentially problematic release.
This version of moose-cli might be problematic. Click here for more details.
- {moose_cli-0.5.23.data → moose_cli-0.6.180.data}/scripts/moose-cli +0 -0
- {moose_cli-0.5.23.dist-info → moose_cli-0.6.180.dist-info}/METADATA +38 -17
- moose_cli-0.6.180.dist-info/RECORD +4 -0
- moose_cli-0.5.23.dist-info/RECORD +0 -4
- {moose_cli-0.5.23.dist-info → moose_cli-0.6.180.dist-info}/WHEEL +0 -0
|
Binary file
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: moose-cli
|
|
3
|
-
Version: 0.
|
|
3
|
+
Version: 0.6.180
|
|
4
4
|
Summary: Build tool for moose apps
|
|
5
5
|
Home-Page: https://www.fiveonefour.com/moose
|
|
6
6
|
Author: Fiveonefour Labs Inc. <support@fiveonefour.com>
|
|
@@ -14,39 +14,44 @@ Project-URL: repository, https://github.com/514labs/moose
|
|
|
14
14
|
|
|
15
15
|
<a href="https://docs.fiveonefour.com/moose/"><img src="https://raw.githubusercontent.com/514-labs/moose/main/logo-m-light.png" alt="moose logo" height="100px"></a>
|
|
16
16
|
|
|
17
|
+
[](https://www.fiveonefour.com)
|
|
17
18
|
[](https://www.npmjs.com/package/@514labs/moose-cli?activeTab=readme)
|
|
18
|
-
[](https://join.slack.com/t/moose-community/shared_invite/zt-2fjh5n3wz-cnOmM9Xe9DYAgQrNu8xKxg)
|
|
20
|
+
[](https://docs.fiveonefour.com/moose/getting-started/quickstart)
|
|
21
|
+
[](LICENSE)
|
|
21
22
|
|
|
22
23
|
# MooseStack
|
|
23
24
|
|
|
24
|
-
**Developer toolkit for building real-time analytical backends in Typescript and Python** — MooseStack
|
|
25
|
+
**Developer toolkit for building real-time analytical backends in Typescript and Python** — MooseStack brings data engineering best practices and a modern web development DX to any engineer building on data infra.
|
|
25
26
|
|
|
26
|
-
MooseStack
|
|
27
|
+
MooseStack modules offer a type‑safe, code‑first developer experience layer for popular open source analytical infrastructure, including [ClickHouse](https://clickhouse.com/), [Kafka](https://kafka.apache.org/), [Redpanda](https://redpanda.com/), and [Temporal](https://temporal.io/).
|
|
28
|
+
|
|
29
|
+
MooseStack is designed for:
|
|
30
|
+
1. Software engineers integrating analytics & AI into their apps, and leaning into real-time / OLAP infrastructure best practices
|
|
31
|
+
2. Data engineers building software & AI applications on their data infra, and leaning into software development best practices
|
|
27
32
|
|
|
28
33
|
## Why MooseStack?
|
|
29
34
|
|
|
30
|
-
- **
|
|
31
|
-
- **
|
|
32
|
-
- **
|
|
35
|
+
- **Git-native development**: Version control, collaboration, and governance built-in
|
|
36
|
+
- **Local-first experience**: Full mirror of production environment on your laptop with `moose dev`
|
|
37
|
+
- **Schema & migration management**: typed schemas in your application code, with transparent migration support
|
|
33
38
|
- **Code‑first infrastructure**: Declare tables, streams, workflows, and APIs in TS/Python -> MooseStack wires it all up.
|
|
34
39
|
- **Modular design**: Only enable the modules you need. Each module is independent and can be adopted incrementally.
|
|
35
|
-
- **
|
|
40
|
+
- **AI copilot friendly**: Designed from the ground up for LLM-powered development
|
|
36
41
|
|
|
37
42
|
## MooseStack Modules
|
|
38
43
|
|
|
39
44
|
- [Moose **OLAP**](https://docs.fiveonefour.com/moose/olap): Manage ClickHouse tables, materialized views, and migrations in code.
|
|
40
|
-
- [Moose **Streaming**](https://docs.fiveonefour.com/moose/streaming): Real‑time
|
|
45
|
+
- [Moose **Streaming**](https://docs.fiveonefour.com/moose/streaming): Real‑time ingest buffers and streaming transformation functions with Kafka/Redpanda.
|
|
41
46
|
- [Moose **Workflows**](https://docs.fiveonefour.com/moose/workflows): ETL pipelines and tasks with Temporal.
|
|
42
47
|
- [Moose **APIs**](https://docs.fiveonefour.com/moose/apis): Type‑safe ingestion and query endpoints with auto‑generated OpenAPI docs.
|
|
43
|
-
-
|
|
48
|
+
- MooseStack Tooling: [Moose **Deploy**](https://docs.fiveonefour.com/moose/deploying), [Moose **Migrate**](https://docs.fiveonefour.com/moose/migrate), [Moose **Observability**](https://docs.fiveonefour.com/moose/metrics)
|
|
44
49
|
|
|
45
50
|
## Quickstart
|
|
46
51
|
|
|
47
52
|
Also available in the Docs: [5-minute Quickstart](https://docs.fiveonefour.com/moose/getting-started/quickstart)
|
|
48
53
|
|
|
49
|
-
Already running Clickhouse: [Getting Started with Existing Clickhouse](https://docs.fiveonefour.com/moose/getting-started/
|
|
54
|
+
Already running Clickhouse: [Getting Started with Existing Clickhouse](https://docs.fiveonefour.com/moose/getting-started/from-clickhouse)
|
|
50
55
|
|
|
51
56
|
### Install the CLI
|
|
52
57
|
|
|
@@ -73,6 +78,16 @@ moose dev
|
|
|
73
78
|
|
|
74
79
|
MooseStack will start ClickHouse, Redpanda, Temporal, and Redis; the CLI validates each component.
|
|
75
80
|
|
|
81
|
+
## Deploy with Boreal
|
|
82
|
+
|
|
83
|
+
The easiest way to deploy your MooseStack Applications is to use [Boreal](https://www.fiveonefour.com/boreal) from 514 Labs, the creators of Moose. Boreal provides zero-config deployments, automatic scaling, managed or BYO infrastructure, monitoring and observability integrations.
|
|
84
|
+
|
|
85
|
+
[Get started with Boreal →](https://www.fiveonefour.com/boreal)
|
|
86
|
+
|
|
87
|
+
## Deploy Yourself
|
|
88
|
+
|
|
89
|
+
MooseStack is open source and can be self-hosted. If you're only using MooseOLAP, you can use the Moose library in your app for schema management, migrations, and typed queries on your ClickHouse database without deploying the Moose runtime. For detailed self-hosting instructions, see our [deployment documentation](https://docs.fiveonefour.com/moose/deploying).
|
|
90
|
+
|
|
76
91
|
## Examples
|
|
77
92
|
|
|
78
93
|
### TypeScript
|
|
@@ -157,14 +172,20 @@ consumption_api = ConsumptionApi[RequestParams, DataModel]("get-api-route", quer
|
|
|
157
172
|
- [Temporal](https://temporal.io/) (workflow orchestration)
|
|
158
173
|
- [Redis](https://redis.io/) (internal state)
|
|
159
174
|
|
|
175
|
+
## Community
|
|
176
|
+
|
|
177
|
+
[Join us on Slack](https://join.slack.com/t/moose-community/shared_invite/zt-2fjh5n3wz-cnOmM9Xe9DYAgQrNu8xKxg)
|
|
160
178
|
|
|
161
|
-
##
|
|
179
|
+
## Cursor Background Agents
|
|
162
180
|
|
|
163
|
-
|
|
181
|
+
MooseStack works with Cursor's background agents for remote development. The repository includes a pre-configured Docker-in-Docker setup that enables Moose's Docker dependencies to run in the agent environment.
|
|
164
182
|
|
|
165
|
-
|
|
183
|
+
### Quick Setup
|
|
184
|
+
1. Enable background agents in Cursor
|
|
185
|
+
2. The environment will automatically build with Docker support
|
|
186
|
+
3. Run `moose dev` or other Moose commands in the agent
|
|
166
187
|
|
|
167
|
-
|
|
188
|
+
For detailed setup instructions and troubleshooting, see [Docker Setup Documentation](.cursor/DOCKER_SETUP.md).
|
|
168
189
|
|
|
169
190
|
## Contributing
|
|
170
191
|
|
|
@@ -0,0 +1,4 @@
|
|
|
1
|
+
moose_cli-0.6.180.dist-info/METADATA,sha256=GqIxCfOAiLyv3SQtWQxf6JgJy-tYiHV5tODi4vRwc6w,8403
|
|
2
|
+
moose_cli-0.6.180.dist-info/WHEEL,sha256=mWFjYkNxH8sb2dkdeHAFc92wsay6-dYHLKDsSojj9OI,106
|
|
3
|
+
moose_cli-0.6.180.data/scripts/moose-cli,sha256=1kv-PXf7JIhNiL01yxNbLlhe-eTlXTiPfe43EkUpoMc,34717768
|
|
4
|
+
moose_cli-0.6.180.dist-info/RECORD,,
|
|
@@ -1,4 +0,0 @@
|
|
|
1
|
-
moose_cli-0.5.23.dist-info/METADATA,sha256=psgfgHnLPsXAA9U3tpJledfne9SuMY7CUwP0GMpLAfc,7366
|
|
2
|
-
moose_cli-0.5.23.dist-info/WHEEL,sha256=mWFjYkNxH8sb2dkdeHAFc92wsay6-dYHLKDsSojj9OI,106
|
|
3
|
-
moose_cli-0.5.23.data/scripts/moose-cli,sha256=jiXmecn2bQ78-RmInYetCzch9SqCUT7nK1lE5wI5IBU,27551200
|
|
4
|
-
moose_cli-0.5.23.dist-info/RECORD,,
|
|
File without changes
|