Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] : Separate Hosting of Server and Client Files for Vercel (CI/CD) #10

Open
SSameer20 opened this issue Apr 10, 2024 · 2 comments
Assignees
Labels
CI/CD enhancement New feature or request

Comments

@SSameer20
Copy link
Owner

SSameer20 commented Apr 10, 2024

[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.

@SSameer20 SSameer20 added enhancement New feature or request CI/CD labels Apr 10, 2024
@SSameer20
Copy link
Owner Author

https://docker-automation.vercel.app/

Try to share a visitable website link

SSameer20 added a commit that referenced this issue Apr 16, 2024
## 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 -->
@Sohail-9
Copy link
Collaborator

Sohail-9 commented Apr 17, 2024

https://docker-automation.vercel.app => link for docker automation app

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI/CD enhancement New feature or request
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants