Cloud Foundry开发工作流程 [英] Cloud Foundry Development Workflow

问题描述

当我从 Cloud Foundry博客：

而不是安装Web服务器（Tomcat等），运行时（Java，Ruby等）和服务（Postgres，MongoDB等），您可以一次下载Micro Cloud Foundry，将其启动，然后使用 vmc push部署应用程序。

"Rather than installing a web server (Tomcat, etc.), runtimes (Java, Ruby, etc.), and services (Postgres, MongoDB, etc.), you can do a single download of Micro Cloud Foundry, boot it up, and deploy your applications using ‘vmc push’."

在开发（Node，Grails或Java Web应用程序）时，我习惯于刷新并查看更改（嗯，总是针对客户端-辅助代码，有时用于服务器端）；它可以实现非常快速有效的发展。

When I'm developing (Node, Grails or Java web apps), I'm used to just refreshing and seeing my changes (well, always for client-side code, sometimes for server-side); it makes for very rapid and efficient development.

在开发过程中不断调用 vmc push对我来说几乎是一个入门。反馈周期太慢，无法实用。有没有更好的办法？有人真的这样做吗？

Constantly invoking 'vmc push' during development is pretty much a non-starter for me. It's far too slow of a feedback cycle to be practical. Is there a better way? Does anyone actually do this?

您的Cloud Foundry开发工作流程是什么样子？Micro Cloud Foundry适合什么位置？

What does your Cloud Foundry development workflow look like and where does Micro Cloud Foundry fit in?

推荐答案

所有将应用程序推送到Cloud Foundry所涉及的延迟问题，我经常使用Micro Cloud Foundry来提供服务（MySQL，MongoDB，Redis等），然后使用本地隧道连接到它们通过vmc tunnel命令。

All issues with the delays involved in pushing an application to Cloud Foundry aside, I often use Micro Cloud Foundry for provisioning services (MySQL, MongoDB, Redis etc) and then use a local tunnel to connect to them via the vmc tunnel command.

这篇关于Cloud Foundry开发工作流程的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！