Features: Deployment Pipe & Redirects #1271
Replies: 2 comments 2 replies
-
Heroku is only addressing the simple case of very simple apps, no persistent volumes, no dependency on the host etc. If that's what you like, all you need to do is this:
Does this address your usecase?
It's already a requested feature: #314 |
Beta Was this translation helpful? Give feedback.
-
I have not thought about this possibility and thought that deployment method No. 6 only works with images from dockerhub. I just tried it on my DEV server and got the error message: That the feature for the redirection in planning is pleased me very much. :) |
Beta Was this translation helpful? Give feedback.
-
I want to avoid being a pain, but I have a few ideas and wanted to hear what you think.
We like to use Heroku in the company and also on your homepage Heroku is compared with Caprover.
A very popular feature is the possibility to set up deployment pipes in Heroku.
App1 = Staging -> App2 = Production with one click, you can copy App1 to App2 after testing.
Would you consider such a feature for Caprover as well?
Another feature might be a possibility to set up a redirect to the "www.*" domain without editing the default nginx configuration. This would probably be possible with it too, but with an option, it would be nice and easy.
Beta Was this translation helpful? Give feedback.
All reactions