mosaic-media-template

What the template provides

The Mosaic Media Template is part of the Axinom Mosaic development platform, and this repository holds the customizable parts of an Axinom Mosaic solution. The readme explains that the code can be used as is or customized to specific requirements, while the Mosaic libraries and services the solution depends on are provided, updated, and maintained by Axinom. In practice it is a starter set of services for building video platforms and content management on top of Mosaic. Getting started is done with a single command, npx with the @axinom/mosaic-cli package and the mosaic create instruction, which walks the user through creating a new Mosaic project based on the media template. The readme points to the CLI documentation for details. The whole monorepo and every package inside it are licensed under the MIT license. The template is aimed at teams that want a working foundation of media services they can extend rather than assembling the plumbing from scratch. Because Axinom maintains the underlying libraries, the expectation is that upgrades flow from the platform vendor while the project specific code stays in the user's copy of this repository. The project reports 32 stars and 6 forks on GitHub. Teams keep their custom code in this repo while Axinom ships the maintained platform libraries.

Prerequisites and local setup

Running the template locally expects a defined toolchain. The readme calls for Node.js, specifically the latest LTS version, and notes that version 22.13.1 is confirmed to work while other versions may need testing. Yarn and Docker are also required. The solution ships a dockerized infrastructure for local development that consists of PostgreSQL and pgAdmin, started and stopped with the yarn infra:up and yarn infra:down commands. Windows users are told to configure Docker for Linux containers, Linux users get a note about running docker commands without sudo through the post install steps, and Mac users get a hint about DNS resolution errors during Quick Deploy that can be fixed by adding public DNS servers to the Docker daemon config. Preparing the solution means running yarn to install workspace dependencies, yarn apply-templates to create local copies of every .template file, yarn infra:up to start the database infrastructure, and yarn db:reset to create the databases for all services. The user then sets tenant and environment parameters in the root .env file, pulling values such as tenant id, environment id, RabbitMQ credentials, and a dev service account client id and secret from the Environment Administration Portal. Finally yarn setup initializes all the services. A current Node LTS install is the single most important prerequisite for the scaffold to run.

Running and structure

To run the solution, the readme instructs the user to start several commands in parallel in separate terminals. The first is yarn dev:libs to compile the media-messages package in watch mode, and the readme warns to wait until this finishes before proceeding to avoid concurrency issues. The next is yarn dev:services to start the media service and catalog service. The development instructions are explicitly scoped to local work, with a pointer to separate documentation for preparing the services for production use. The template's structure reflects a service oriented media platform: messaging packages, media and catalog services, and environment configuration managed through the Mosaic CLI and the portal. Because the underlying Mosaic libraries are maintained by Axinom, teams adopting the template take on the job of writing the customizable business logic while relying on the vendor for the core platform updates. The MIT license on the monorepo means the starting code can be modified and redistributed under the same terms. The combination of a CLI scaffold, dockerized Postgres, and a documented setup path lowers the effort of standing up a customizable video platform compared with building the integration layer by hand. The repository's documentation points readers to docs.axinom.com for the full platform reference.

Editorial conclusion

The repository is published under the MIT license and its most recent commit was on 2026-08-26.