Deployment & Operations
Process guide, execution, and operational guidelines for the current KENTODAL repository.
Authorization Notice
The site is not publicly published at this time. Its publication to a final domain and deployment to production require explicit authorization from KENTODAL's corporate management.
Operational Flow (Current vs. Recommended)
Execution Status and Configuration
The current KENTODAL repository uses the next dev commands for local development and preview, and next build followed by next start for production execution. This implies the availability of a Node.js environment, rather than being an application exported purely as static files.
Configuration is managed via environment variables, with NEXT_PUBLIC_SITE_URL being the main publicly exposed variable that determines the site's base addresses.
Build Verification
Recommended checks are performed before starting the server:
- Type checking:
tsc --noEmitto validate the code structure in TypeScript. - Compilation:
next buildwhich prepares the site and incorporates the content of the institutional modules.
Recommended Practices for Release
Due to the institutional nature of the platform, we recommend that future publications to a final domain include:
- Environment Reviews: Validate the site in a pre-production (Staging) environment before public release.
- Immutable Deployments: Schemes that allow for atomic versions of the site.
- Controlled Rollback: Strategies that make it easy to revert to a stable version if required.
- CI/CD Automation: A continuous integration pipeline that validates code branches (e.g.
main) before going to production.