|
|
|
|
|
|
by yingw787
2669 days ago
|
|
|
Interesting proposal! I have a number of questions: - How much configuration is still required by the end user to leverage Dockup? How would it be different from a Vagrant/Docker setup where you would define a Vagrantfile and Dockerfile? - Why make pull request reviews with a development environment rather than a slimmed down production environment? Testing turnaround time? - Do you guys anticipate on-premise deployments of Dockup? Best of luck! |
|
|
- Regarding configuration - you need Dockerfiles for your apps and also configure environment variables and ports in Dockup. We call this configuration a "blueprint", which once created will be the template for your automated deployments. Unlike Vagrant, Dockup runs your apps on the cloud and you get URLs in your slack channel when someone opens a PR.
- Our pull request reviews (we use Dockup while developing Dockup :D) actually use production environment. We simply use a postgres container as the database and turn off analytics in our Dockup environments.
- Yes we do get requests for on-premise installations and we do support that. In fact, when we started, we only supported on-premise and later made the SaaS version. If you want to just self-host the infra and use Dockup UI, you can do it right now by signing up for the self-hosted plan.