Open itsmeadarsh2008 opened 2 months ago
Is this to deploy it to reflex hosted service, or to your own hosting provider? If the former, I feel like it's already quite easy to deploy. It the latter, afaik all the hosting provider work a bit different. So I guess reflex would need to prefer certain providers over others with their inbuilt github actions.
If you're looking for a github action yourself btw, you can check out mine: https://github.com/dentro-innovation/reflex_template/blob/main/.github/workflows/deploy.yaml
Is this to deploy it to reflex hosted service, or to your own hosting provider? If the former, I feel like it's already quite easy to deploy. It the latter, afaik all the hosting provider work a bit different. So I guess reflex would need to prefer certain providers over others with their inbuilt github actions.
If you're looking for a github action yourself btw, you can check out mine: https://github.com/dentro-innovation/reflex_template/blob/main/.github/workflows/deploy.yaml
I mean specifically for reflex.run sites. We need to manually push things.
true, but it's just one extra command isn't it?
Yeah. It is the same reason why we wouldn't publish PyPI packages from the host computer instead we do it from the CI/CD
I would like to suggest setting up GitHub Actions for easy deployment to Reflex Own Deployment Service. We can create a workflow that triggers push events to deploy the latest changes automatically. This will streamline our deployment process and ensure that every push to the main branch results in a new deployment. The action files will be generated via
reflex init
(enable to generate GitHub workflows by default)Not only the projects generated will be automatically updated but also the 3rd party components be benefitted from this.