[Feature] : Separate Hosting of Server and Client Files for Vercel (CI/CD) #10
Description
[Feature] : Separate Hosting of Server and Client Files for Vercel (CI/CD)
Description:
Currently, when deploying server-side and client-side code together on Vercel using CI/CD, it can be challenging to manage separate scaling needs and security concerns. For instance, exposing server-side code publicly might introduce security vulnerabilities. Additionally, serverless functions on Vercel may require different build processes compared to client-side assets.
Proposed Solution:
We propose a feature that allows developers to configure separate build pipelines for server and client code in their CI/CD workflows. This could involve:
- The ability to specify different build commands and environments for each codebase.
- Support for deploying server-side code to a private backend while serving client-side files from Vercel's CDN.
- Integration with Vercel's serverless functions framework for seamless execution of server-side logic.
Benefits:
By enabling separate hosting, this feature would offer several advantages:
- Enhanced security: Server-side code remains private, mitigating potential security risks.
- Improved scalability: Server and client deployments can be scaled independently based on their respective requirements.
- Greater flexibility: Developers can leverage Vercel's serverless functions seamlessly while maintaining a secure separation from public client-side assets.
Additional Context:
This feature would be particularly valuable for building serverless applications on Vercel where server-side logic is required but needs to be kept separate from publicly exposed client-side code.