Home ci 42. monorepos: monorepo faq

42. monorepos: monorepo faq

Last updated on Aug 05, 2025

Monorepos FAQ URL: https://epycbyte.com/docs/monorepos/monorepo-faq

  1. How can I speed up builds?

    • The number of concurrent builds you have depends on your plan. Hobby plans allow 1 build, while Pro and Enterprise plans let you customize the number in billing settings. Learn more about concurrent builds.
  2. How can I make my projects available on different paths under the same domain?

    • Each directory becomes a separate Epycbyte project. To host multiple projects under one domain, create a new project, assign the domain, and use a epycbyte.json file for path rewrites.
  3. How are projects built after I push?

    • Pushing to connected Git repositories triggers parallel builds for each project.
  4. Can I share source files between projects?

    • Yes, enable "Include source files outside the Root Directory" in project settings. For Yarn workspaces, see deploying with Yarn.
  5. How can I use Epycbyte CLI without Project Linking?

    • Use Environment Variables instead of Project Linking. For example:
    epycbyte_ORG_ID=team_123 epycbyte_PROJECT_ID=prj_456 epycbyte
    

    Learn more about custom workflows with Epycbyte CLI.

  6. Can I use Turborepo on the Hobby plan?

    • Yes, Turborepo is supported on all plans.
  7. Can I use Nx with environment variables on Epycbyte?

    • Define environment variables in each deployment to avoid cache issues. Use Runtime Hash Inputs in nx.json to prevent cached values. For example:
    "runtimeCacheInputs": ["echo $MY_epycbyte_ENV"]
    

Table of Contents:

  1. How can I speed up builds?
  2. How can I make my projects available on different paths under the same domain?
  3. How are projects built after I push?
  4. Can I share source files between projects?
  5. How can I use Epycbyte CLI without Project Linking?
  6. Can I use Turborepo on the Hobby plan?