From ba1258247cc77b9a07309c3559de0f8f0d742350 Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Thu, 21 Aug 2025 13:37:35 +0000 Subject: [PATCH 1/4] Update branding references from "Moose Stack" to "MooseStack" Co-authored-by: mitchell --- apps/framework-docs/src/pages/moose/deploying.mdx | 4 ++-- .../pages/moose/deploying/deploying-with-docker-compose.mdx | 2 +- apps/framework-docs/src/pages/moose/index.mdx | 4 ++-- apps/framework-docs/src/pages/moose/metrics.mdx | 4 ++-- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/apps/framework-docs/src/pages/moose/deploying.mdx b/apps/framework-docs/src/pages/moose/deploying.mdx index 020e6a9ec8..bd144a03eb 100644 --- a/apps/framework-docs/src/pages/moose/deploying.mdx +++ b/apps/framework-docs/src/pages/moose/deploying.mdx @@ -15,12 +15,12 @@ import { Cloud } from "lucide-react"; Once you've finished developing your Moose application locally, the next step is to deploy your Moose app into production. You have two options: - Self-host your Moose application on your own servers -- Use the [Boreal Cloud hosting platform](https://www.fiveonefour.com/boreal) (from the makers of the Moose Stack) +- Use the [Boreal Cloud hosting platform](https://www.fiveonefour.com/boreal) (from the makers of MooseStack) -Want this managed in production for you? Check out Boreal Cloud (from the makers of the Moose Stack). +Want this managed in production for you? Check out Boreal Cloud (from the makers of MooseStack). ## Getting Started With Self-Hosting diff --git a/apps/framework-docs/src/pages/moose/deploying/deploying-with-docker-compose.mdx b/apps/framework-docs/src/pages/moose/deploying/deploying-with-docker-compose.mdx index f8f60c62f5..4b23fe258c 100644 --- a/apps/framework-docs/src/pages/moose/deploying/deploying-with-docker-compose.mdx +++ b/apps/framework-docs/src/pages/moose/deploying/deploying-with-docker-compose.mdx @@ -772,7 +772,7 @@ sudo vim /etc/systemd/system/moose-stack.service ``` [Unit] -Description=Moose Stack +Description=MooseStack Requires=docker.service After=docker.service diff --git a/apps/framework-docs/src/pages/moose/index.mdx b/apps/framework-docs/src/pages/moose/index.mdx index 0898a51128..21e230241d 100644 --- a/apps/framework-docs/src/pages/moose/index.mdx +++ b/apps/framework-docs/src/pages/moose/index.mdx @@ -367,7 +367,7 @@ Each module is independent and can be used on its own. You can start with one ca - [Temporal](https://temporal.io/) (Workflow Orchestration) - [Redis](https://redis.io/) (Internal State Management) - -Want this managed in production for you? Check out Boreal Cloud (from the makers of the Moose Stack). + +Want this managed in production for you? Check out Boreal Cloud (from the makers of MooseStack). diff --git a/apps/framework-docs/src/pages/moose/metrics.mdx b/apps/framework-docs/src/pages/moose/metrics.mdx index 153e609d4f..d5a9bb725b 100644 --- a/apps/framework-docs/src/pages/moose/metrics.mdx +++ b/apps/framework-docs/src/pages/moose/metrics.mdx @@ -165,8 +165,8 @@ SENTRY_DSN=https://your-sentry-dsn RUST_BACKTRACE=1 ``` - -Want this managed in production for you? Check out Boreal Cloud (from the makers of the Moose Stack). + +Want this managed in production for you? Check out Boreal Cloud (from the makers of MooseStack). From 8b36ce78a5c467ea4bd33a87e2cf1abe589f7693 Mon Sep 17 00:00:00 2001 From: Johanan Ottensooser Date: Thu, 21 Aug 2025 09:34:14 -0700 Subject: [PATCH 2/4] Update index.mdx --- apps/framework-docs/src/pages/moose/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/framework-docs/src/pages/moose/index.mdx b/apps/framework-docs/src/pages/moose/index.mdx index 21e230241d..247049f20e 100644 --- a/apps/framework-docs/src/pages/moose/index.mdx +++ b/apps/framework-docs/src/pages/moose/index.mdx @@ -367,7 +367,7 @@ Each module is independent and can be used on its own. You can start with one ca - [Temporal](https://temporal.io/) (Workflow Orchestration) - [Redis](https://redis.io/) (Internal State Management) - + Want this managed in production for you? Check out Boreal Cloud (from the makers of MooseStack). From 06cddba4a0ba3b4c7a2dea344d9a7bf2da7e9354 Mon Sep 17 00:00:00 2001 From: Johanan Ottensooser Date: Thu, 21 Aug 2025 09:34:51 -0700 Subject: [PATCH 3/4] Update metrics.mdx --- apps/framework-docs/src/pages/moose/metrics.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/framework-docs/src/pages/moose/metrics.mdx b/apps/framework-docs/src/pages/moose/metrics.mdx index d5a9bb725b..ec77f03b3d 100644 --- a/apps/framework-docs/src/pages/moose/metrics.mdx +++ b/apps/framework-docs/src/pages/moose/metrics.mdx @@ -165,7 +165,7 @@ SENTRY_DSN=https://your-sentry-dsn RUST_BACKTRACE=1 ``` - + Want this managed in production for you? Check out Boreal Cloud (from the makers of MooseStack). From 7086616dad0d9d09ed5af48779c884aa7adaa86e Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Thu, 21 Aug 2025 19:24:21 +0000 Subject: [PATCH 4/4] Rebrand documentation from "Moose" to "MooseStack" Co-authored-by: mitchell --- .../src/pages/moose/deploying.mdx | 16 ++++++------ apps/framework-docs/src/pages/moose/index.mdx | 6 ++--- .../src/pages/moose/metrics.mdx | 18 ++++++------- .../src/pages/moose/moose-cli.mdx | 26 +++++++++---------- .../src/pages/moose/olap/apply-migrations.mdx | 14 +++++----- 5 files changed, 40 insertions(+), 40 deletions(-) diff --git a/apps/framework-docs/src/pages/moose/deploying.mdx b/apps/framework-docs/src/pages/moose/deploying.mdx index bd144a03eb..8e64b2ef7d 100644 --- a/apps/framework-docs/src/pages/moose/deploying.mdx +++ b/apps/framework-docs/src/pages/moose/deploying.mdx @@ -6,15 +6,15 @@ description: Summary of deploying Moose into production import { TypeScript, Python, LanguageSwitcher, Callout } from "@/components"; import { Cloud } from "lucide-react"; -# Moose Deploy +# MooseStack Deploy ## Overview -Once you've finished developing your Moose application locally, the next step is to deploy your Moose app into production. You have two options: +Once you've finished developing your MooseStack application locally, the next step is to deploy your MooseStack app into production. You have two options: -- Self-host your Moose application on your own servers +- Self-host your MooseStack application on your own servers - Use the [Boreal Cloud hosting platform](https://www.fiveonefour.com/boreal) (from the makers of MooseStack) @@ -24,7 +24,7 @@ Want this managed in production for you? Check out Boreal Cloud (from the makers ## Getting Started With Self-Hosting -Moose makes it easy to package and deploy your applications, whether you're deploying to a server with or without internet access. The deployment process is designed to be flexible and can accommodate both containerized and non-containerized environments. +MooseStack makes it easy to package and deploy your applications, whether you're deploying to a server with or without internet access. The deployment process is designed to be flexible and can accommodate both containerized and non-containerized environments. ### Deployment Options @@ -35,16 +35,16 @@ Moose makes it easy to package and deploy your applications, whether you're depl ### Key Deployment Steps -There are three main aspects to deploying a Moose application: +There are three main aspects to deploying a MooseStack application: -1. Setting up your build environment with Node.js and the Moose CLI +1. Setting up your build environment with Node.js and the MooseStack CLI 2. Building your application using `moose build` 3. Setting up your deployment environment with the necessary runtime dependencies (Node.js, Docker) and configuration -1. Setting up your build environment with Python and the Moose CLI +1. Setting up your build environment with Python and the MooseStack CLI 2. Building your application using `moose build` 3. Setting up your deployment environment with the necessary runtime dependencies (Python, Docker) and configuration @@ -52,7 +52,7 @@ There are three main aspects to deploying a Moose application: ## Configuring Your Deployment -Based on our production experience, we recommend the following best practices for deploying Moose applications: +Based on our production experience, we recommend the following best practices for deploying MooseStack applications: ### Health Monitoring diff --git a/apps/framework-docs/src/pages/moose/index.mdx b/apps/framework-docs/src/pages/moose/index.mdx index 247049f20e..a7a190c338 100644 --- a/apps/framework-docs/src/pages/moose/index.mdx +++ b/apps/framework-docs/src/pages/moose/index.mdx @@ -18,14 +18,14 @@ import { Tabs } from "nextra/components"; Type-safe, code-first tooling for building real-time analytical backends--OLAP Databases, Data Streaming, ETL Workflows, Query APIs, and more. ## Get Started -```bash filename="Install Moose" copy +```bash filename="Install MooseStack" copy bash -i <(curl -fsSL https://fiveonefour.com/install.sh) moose ``` -Join our Slack community to share feedback and get help with Moose. +Join our Slack community to share feedback and get help with MooseStack. diff --git a/apps/framework-docs/src/pages/moose/moose-cli.mdx b/apps/framework-docs/src/pages/moose/moose-cli.mdx index dcfc3f6ca4..423812c3d0 100644 --- a/apps/framework-docs/src/pages/moose/moose-cli.mdx +++ b/apps/framework-docs/src/pages/moose/moose-cli.mdx @@ -1,9 +1,9 @@ --- -title: Moose CLI Reference -description: Moose CLI Reference +title: MooseStack CLI Reference +description: MooseStack CLI Reference --- -# Moose CLI Reference +# MooseStack CLI Reference ## Installation @@ -14,7 +14,7 @@ bash -i <(curl -fsSL https://fiveonefour.com/install.sh) moose ## Core Commands ### Init -Initializes a new Moose project. +Initializes a new MooseStack project. ```bash moose init --template