Deploying Moose into Production
Viewing typescript
switch to python
Once you’ve finished developing your Moose application locally, the next step is to deploy your Moose app into production. Check out the Architecture page to see what the architecture of your Moose application in production will look like.
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.
Key Deployment Steps
There are three main aspects to deploying a Moose application:
- Setting up your build environment with Node.js and the Moose CLI
- Building your application using
moose build - Setting up your deployment environment with the necessary runtime dependencies (Node.js, Docker) and configuration
- Setting up your build environment with Python and the Moose CLI
- Building your application using
moose build - Setting up your deployment environment with the necessary runtime dependencies (Python, Docker) and configuration
Deployment Options
Moose supports several deployment scenarios:
- Standard Server Deployment: Deploy your application to a server with internet access
- Offline Server Deployment: Deploy to an environment without internet access
- Containerized Deployment: Package your application in Docker containers for cloud or on-premises deployment
Environment Configuration
For any deployment type, you’ll need to configure:
- Runtime environment variables
- Database and storage cluster access
- Network settings and security configurations
- Application-specific configurations
The following pages provide detailed guides for each deployment scenario, including step-by-step instructions for both Python and TypeScript applications.