title: "Build Features for Customizing Deployments"

Build Features for Customizing Deployments

Epycbyte provides several features to customize your deployments, ensuring security and performance while allowing flexibility in how your project is managed and accessed.

Private npm packages

When working with private npm modules that require authentication, follow these steps:

1. Define NPM_TOKEN as an environment variable in your project.
2. Alternatively, define NPM_RC in the .npmrc file located at the root of your project folder.

This allows Epycbyte to install and use your private dependencies securely.

Ignored files and folders

Epycbyte ignores specific files and folders by default to enhance security and performance:

• Common ignored files:
  • .hg, .git, .gitmodules, .svn, .cache, .next, .now, .epycbyte, .npmignore, .dockerignore, .gitignore, *.swp, .DS_Store, .wafpick-*, .lock-wscript, .env.local, .env.*.local, .venv
  • Directories:
    • node_modules, __pycache__, venv, CVS

These files are automatically excluded from deployment without needing to modify .epycbyteignore.

Special paths

Access your deployment's source code and build logs using special pathnames:

• /_src: Redirects to the Deployment inspector for viewing sources.
• /_logs: Provides real-time log streaming.

These paths are protected by default but can be made public under Security settings in Project Settings.

Git submodules

Deploy Git submodules publicly via HTTP. Private or SSH-accessed submodules will fail during build unless referenced as npm packages in your package.json.

For private repositories, use the provider-specific syntax in your dependencies.