Skip to content
Open
Show file tree
Hide file tree
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions apps/framework-docs/src/pages/moose/deploying.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missed a couple on this row, for example

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cursoragent fix this

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Working on it! I'll start making changes in this branch.

Open in Cursor Open in Web


- Self-host your Moose application on your own servers
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

another one

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cursoragent fix this

Copy link

@cursor cursor bot Aug 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I performed a comprehensive branding update across the documentation, replacing all instances of "Moose" with "MooseStack". This ensures consistency with the new product name in deployment guides, CLI references, observability details, and OLAP migration processes.

  • I updated the product name from "Moose" to "MooseStack" throughout the documentation content.
  • I modified the titles and descriptions of several pages, including apps/framework-docs/src/pages/moose/moose-cli.mdx (to MooseStack CLI Reference) and apps/framework-docs/src/pages/moose/metrics.mdx (to Unified observability for MooseStack).
  • I replaced all instances of "Moose" with "MooseStack" in the body content across apps/framework-docs/src/pages/moose/deploying.mdx, index.mdx, metrics.mdx, moose-cli.mdx, and olap/apply-migrations.mdx.
  • I updated the filename attribute for the installation command from Install Moose to Install MooseStack in apps/framework-docs/src/pages/moose/index.mdx for improved clarity.

3 tasks completed

  • Find all remaining 'Moose' references in documentation files
  • Fix 'Moose' references in deploying.mdx file
  • Fix 'Moose' references in other documentation files
  • Verify all 'Moose' references have been updated to 'MooseStack'
Open in Cursor Open in Web

Learn more about Cursor Agents

- 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)



<Callout type="success" title="Deploy on Boreal Cloud" href="https://www.fiveonefour.com/boreal" ctaLabel="Learn More" icon={Cloud}>
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).
</Callout>

## Getting Started With Self-Hosting
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -772,7 +772,7 @@ sudo vim /etc/systemd/system/moose-stack.service

```
[Unit]
Description=Moose Stack
Description=MooseStack
Requires=docker.service
After=docker.service

Expand Down
4 changes: 2 additions & 2 deletions apps/framework-docs/src/pages/moose/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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)

<Callout type="info" title="Managed Moose in Production" href="https://www.fiveonefour.com/boreal" ctaLabel="Boreal Cloud" compact>
Want this managed in production for you? Check out Boreal Cloud (from the makers of the Moose Stack).
<Callout type="info" title="Managed MooseStack Applications in Production" href="https://www.fiveonefour.com/boreal" ctaLabel="Boreal Cloud" compact>
Want this managed in production for you? Check out Boreal Cloud (from the makers of MooseStack).
</Callout>

4 changes: 2 additions & 2 deletions apps/framework-docs/src/pages/moose/metrics.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -165,8 +165,8 @@ SENTRY_DSN=https://your-sentry-dsn
RUST_BACKTRACE=1
```

<Callout type="success" title="Managed Moose in Production" href="https://www.fiveonefour.com/boreal" ctaLabel="Boreal Cloud" icon={Cloud}>
Want this managed in production for you? Check out Boreal Cloud (from the makers of the Moose Stack).
<Callout type="success" title="Managed MooseStack Applications in Production" href="https://www.fiveonefour.com/boreal" ctaLabel="Boreal Cloud" icon={Cloud}>
Want this managed in production for you? Check out Boreal Cloud (from the makers of MooseStack).
</Callout>


Expand Down
Loading