Foundry development workflow

I'm trying to understand how to use Micro CloudFoundry for development, as described when I read the following items from the Cloud Foundry blog

"Instead of installing a web server (Tomcat, etc.), runtime (Java, Ruby, etc.) and services (Postgres, MongoDB, etc.) you can perform a single Micro Cloud Foundry download by downloading and Deploy your applications using vmc push.

When I develop (Node, Grails or Java web applications), I'm used to just updating and seeing my changes (well, always for client code, sometimes for server code); It provides a very fast and efficient development.

Constantly calling "vmc push" during development is pretty much not a starter for me. This is too slow a feedback loop to be practical. Is there a better way? Does anyone really do this?

What does Cloud Foundry development workflow look like and where is Micro Cloud Foundry located?

+4
source share
1 answer

All problems with delays associated with clicking the application in Cloud Foundry, I often use Micro Cloud Foundry to provide services (MySQL, MongoDB, Redis, etc.), and then use the local tunnel to connect to them through the vmc tunnel command.

+2
source

Source: https://habr.com/ru/post/1447390/


All Articles