-
Notifications
You must be signed in to change notification settings - Fork 15
Build Overview
This step assumes that you've already done the following in your local development environment:
- Installed Git, NodeJS, MeteorJS
- Cloned the SparkEd Repository
- Installed SparkEd Dependencies with
npm install
To build a release build of a MeteorJS application for custom deployments, run
meteor build <dist_dir> --architecture <architecture_name>
The architecture flag is optional, however it's recommended if you need to build for architectures other than your current machine's architecture. For example, running
meteor build <dist_dir> --architecture os.linux.x86_64
from an OS X device would build a Linux x64 bit variant of the application.
The end result of the build command will be an gziped archive under the <dist_dir> directory. This contains the built application that you'll use for custom MeteorJS deployments.
After extracting this production build end users will need to run (cd programs/server && npm install) from the extracted bundle directory.
Building for Windows has proven slightly tricky. We've opted to use Demeteorizer based on recommendations in this forum post.
We've tested this process on Windows, but have not yet tried building from another platform and seeing if the resulting bundle runs on windows without any issues.
See the Windows Setup Documentation for more details.
MeteorJS supports a variety of other deployments as well, including managed services like Galaxy, as well as Docker containers and direct deployment tooling. You can read more about other MeteorJS Deployment options in the MeteorJS Documentation.