You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[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:
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.
The text was updated successfully, but these errors were encountered:
## Pull Request
Added new workflow of the project
## Related Issues
[Feature] : Separate Hosting of Server and Client Files for Vercel
(CI/CD) #10
## Checklist
<<<<<<< HEAD
<!--- Go over all the following points, and put an `x` in all the boxes
that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
=======
Go over all the following points, and put an `x` in all the boxes that
apply.
- [ ] My code follows the code style of this project.
- [ ] I have reviewed my code and ensured it's functioning as expected.
- [ ] I have added appropriate comments to my code, particularly in
hard-to-understand areas.
- [x] I have updated the documentation accordingly.
- [ ] My changes generate no new warnings or errors.
- [ ] I have tested my changes locally.
## Additional Notes
<!--- Any additional information or notes you want to add -->
[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:
Benefits:
By enabling separate hosting, this feature would offer several advantages:
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.
The text was updated successfully, but these errors were encountered: