Every Esadax project comes with a set of configurable settings that determine how your application is built, deployed, and served. Understanding these settings is essential to optimize performance, ensure consistency across environments, and customize your workflows.
This article provides an overview of the available project settings and links to more detailed articles that cover each area.
Table of Contents
Overview
The Project Settings panel in your Esadax dashboard is where you define how your application should behave during both the build and runtime phases. These settings influence:
- The root directory where your app source code lives
- Which framework (e.g., Next.js, Astro, SvelteKit) to optimize for
- Build command and output directory
- Runtime environment variables for staging or production
- The Node.js version used during build and function execution
- HTTP headers such as caching or security headers
Root Directory
Projects that use monorepos or have nested folders may need to customize the root directory. Learn how to set it correctly in Root Directory Settings.
Framework Presets
Esadax auto-detects many popular frameworks but allows you to override detection and manually configure framework-specific behavior. See Framework Presets for more.
Build Settings
Customize your build command, output folder, and install behavior for more granular control of the build process. Learn more in Build Settings.
Environment Variables
Securely define variables for staging and production environments directly in the dashboard or via CLI. See Environment Variables.
Node.js Version
Ensure compatibility by specifying the Node.js version for build and runtime environments. Read How to Configure Node Version to get started.
Configure Headers
Define custom HTTP headers for caching, security, and routing. This is especially useful for static files and performance optimizations. See Configure Headers.
Conclusion
Project settings are foundational to how your application runs on Esadax. By tailoring these options to your app’s structure and framework, you can reduce configuration issues, improve deploy performance, and stay consistent across teams.
Continue reading the individual configuration guides linked above to explore each setting in more depth.
