blocks|key|3943941|text|如果您使用标准配置的机器，您可以使用全新的完美配置来镜像磁盘--这是许多公司中非常流行的方法(不仅仅是开发人员)。如果你需要单独配置操作系统，一旦配置好的操作系统变成你想要的设置，你可以用tar-bz2命令把所有添加和更改的文件都压缩到你想要的设置中，然后以root用户的身份解压它，从头开始创建你想要的环境。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3943942|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you use machines in a standard configuration, you can image the disk with a fresh perfectly configured install -- that's a very popular approach in many corporations (and not just for developers, either). If you need separately configured OS's, you can tar-bz2 all the added and changed files once a configured OS is turned into your desired setup, and just untar it as root to make your desired environment from scratch.

blocks|key|3943970|text|总是有使用虚拟机的选项(例如，参见VMWare+Player)。创建一个环境，并将其复制到每个新员工，只需最少的配置。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3943971|entityMap|0|LINK|mutability|MUTABLE|url|http://www.vmware.com/download/player/^0|H|D|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

There's always the option of using virtual machines (see e.g. <a href="http://www.vmware.com/download/player/" rel="nofollow noreferrer">VMWare Player</a>). Create one environment and copy it over for each new employee with minimal configuration needed.

blocks|key|724132|text|我喜欢使用Virtual+PC或VMware来虚拟化开发环境。这提供了一个标准的“开发环境”，可以在开发人员之间共享。您不必担心用户可能添加到其系统中的软件可能与您的开发环境冲突。它还为我提供了一种处理两个项目的方法，在这两个项目中，开发环境不能同时在一个系统上(使用核心技术的两个不同版本)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|724133|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I like to use Virtual PC or VMware to virtualize the development environment. This provides a standard "dev environment" that could be shared among developers. You don't have to worry about software that the user could add to their system that may conflict with your development environment. It also provides me a way to work to two projects where the development environments can't both be on one system (using two different versions of a core technology).

blocks|key|4787211|text|重要的一点是在源代码管理中设置您的项目，以便您可以在签出后立即构建、部署和运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4787212|这意味着您还应该检查帮助程序基础设施，如Makefiles、ant+buildfile等，以及工具的设置，如IDE项目文件。|4787213|这应该会解决单个项目的安装麻烦。|4787214|对于基本的机器设置，您可以使用标准映像。另一种选择是使用平台的工具自动安装。在Linux下，您可以创建一个meta-package，它依赖于您需要的所有包。在Windows下，使用MSI或类似的东西应该可以实现类似的事情。|4787215|编辑：|4787216|理想情况下，不是签入帮助器基础设施，而是签入允许构建生成帮助器基础设施的信息。这是GNU构建系统(autotools等)或Maven所采用的方法。这甚至更优雅，因为您(理论上)可以为任何(支持的)构建环境生成基础架构，因此您不会被绑定到某个特定的IDE，以及帮助基础架构(路径等)中的设置。不需要复制主项目设置。|4787217|然而，这也是一种更复杂的方法，所以如果你不能让它工作，我相信直接签入IDE文件之类的东西是可以接受的。|4787218|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

One important point is to set up your projects in source control such that you can immediately build, deploy and run after checkout. 

That means you should also checkin helper infrastructure, such as Makefiles, ant buildfiles etc., and settings for the tools, such as IDE project files.

That should take care of the setup hassle for individual projects.

For the basic machine setup, you could use a standard image. Another option is to use your platform's tools to automate installation. Under Linux, you could create a meta-package that depends on all the packages you need. Under Windows, a similar thing should be possible using MSI or the like.

Edit:

Ideally, instead of checking in helper infrastructure, you check in the information that allows the build to generate the helper infrastructure. This is the approach taken by e.g. the GNU build system (autotools etc.), or by Maven. This is even more elegant, because you can (theoretically) generate infrastructure for any (supported) build environment, thus you are not bound to e.g. one specific IDE, and settings in the helper infrastructure (paths etc.) don't need to duplicate the main project settings.

However, this also a more complex approach, so if you can't get it to work, I believe checking in stuff like IDE files directly is acceptable.

blocks|key|3944075|text|使用puppet配置您的开发和生产环境。使用一流的自动化系统是扩展运营规模的唯一途径。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3944076|entityMap|0|LINK|mutability|MUTABLE|url|http://reductivelabs.com/trac/puppet/wiki/AboutPuppet^0|2|6|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Use <a href="http://reductivelabs.com/trac/puppet/wiki/AboutPuppet" rel="nofollow noreferrer">puppet</a> to configure both your development and production environment. Using a top-notch automation system is the only way to scale your ops.

blocks|key|4787287|text|如果您使用的是linux版本，那么您可能已经有了一个包管理系统:为fedora/redhat考虑.rpm，或者为ubuntu/debian考虑.deb。您所描述的许多东西已经有了可用的包:+svn、eclipse等您可以为公司特定的软件推出自己的包，创建一个存储库(可能仅在本地网络上可用)，然后您的设置可以简化为一个bash脚本，该脚本会将公司存储库添加到/+etc+/apt/Soures.list+(debian/ubuntu)，然后调用如下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4787288|/home/newhire$+apt-get+update+&&+apt-get+install+some+complete+package+list|code-block|syntax|javascript|4787289|您可以使用buildbot为经常更改的公司包自动执行常规构建。|offset|length|4787290|entityMap|0|LINK|mutability|MUTABLE|url|http://buildbot.net/trac^0|0|0|5|8|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

if you're using a linux flavor, you've probably got a package management system: thinks .rpm for fedora/redhat, or .deb for ubuntu/debian. many of the things you describe already have packages available: svn, eclipse, etc. you could roll your own packages for company specific software, create a repository (perhaps only available on the local network) and then your setup could be reduced to a single bash script which would add the company repo to /etc/apt/sources.list (debian/ubuntu) and then call a command like,

<pre><code>
/home/newhire$ apt-get update && apt-get install some complete package list
</code></pre>

you could use <a href="http://buildbot.net/trac" rel="nofollow noreferrer">buildbot</a> to then automate regular builds for company packages that change often.

blocks|key|3944179|text|有几个选项，有时这些选项的组合很有用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3944180|3944181|automated+installation|unordered-list-item|3944182|disk+imaging|3944183|virtualization|3944184|source+control+|3944185|3944186|各种选项的详细信息：|3944187|用于自动安装和配置工作站的各种服务、工具和配置文件的|3944188|Automated+Installation工具：|ordered-list-item|offset|length|style|BOLD|3944189|3944190|-+[Puppet](https://puppet.com/)+has+a+learning+curve+but+is+powerful.++You+define+classes+of+machines+(development+box,+web+server,+etc.)+and+it+then+does+what+is+necessary+to+install,+configure,+and+keep+the+box+in+the+proper+state.++You+asked+for+one-click,+but+Puppet+by+default+is+zero-click,+as+it+checks+your+machine+periodically+to+make+sure+it+is+still+configured+as+desired.++It+will+detect+when+a+file+or+mode+has+been+changed,+and+fix+the+problem.++I+currently+use+this+to+maintain+a+handful+of+RedHat+Linux+boxes,+though+it's+capable+of+handling+thousands.++(Does+not+support+Windows+as+of+2009-05-08).++
-+[Cfengine](http://www.cfengine.org/)+is+another+one.++I've+seen+this+used+successfully+at+a+shop+with+70+engineers+using+RedHat+Linux.++Its+limitations+were+part+of+the+reason+for+Puppet.
-+[SmartFrog](http://en.wikipedia.org/wiki/SmartFrog)+is+another+tool+for+configuring+hosts.++It+does+support+Windows.
-+Shell+scripts.++[RightScale](http://blog.rightscale.com/2007/08/07/configuring-servers-with-rightscripts/)+has+examples+of+how+to+configure+an+Amazon+EC2+image+using+shell+scripts.
-+Install+packages.++On+a+Unix+box+it's+possible+to+do+this+entirely+with+packages,+and+on+Windows+msi+may+be+an+option.++For+example,+[RubyWorks](http://studios.thoughtworks.com/rubyworks)+provides+you+with+a+full+Ruby+on+Rails+stack,+all+by+installing+one+package+that+in+turn+installs+other+packages+via+dependencies.|code-block|syntax|javascript|3944191|​|3944192|3944193|Disk映像当然还有disk+imaging+tools，用于存储已配置主机的映像，以便可以将其恢复到另一台主机。与虚拟化一样，这对于测试箱特别好，因为它很容易恢复到一个干净的石板上。保持更新仍然是一个问题--仅仅为了传播配置文件而制作新映像是否值得呢?+change?|3944194|是另一种选择，例如制作Xen、VirtualPC或VMWare映像的副本来创建新主机。这对于测试箱特别有用，因为无论测试造成什么混乱，您都可以很容易地恢复到干净的、已知的状态。与磁盘映像工具一样，与自动安装/配置工具为used.|3944195|Source+Code+Control相比，使主机保持最新需要更多的手动步骤和警觉。一旦安装/配置了必要的工具，那么进行构建就应该是检查源代码存储库中需要的内容并构建它。|3944196|3944197|目前，我使用上面的组合来自动化这个过程，如下所示：|3944198|3944199|从在VMWare来宾|3944200|上安装基本操作系统开始运行shell脚本以安装Puppet并从源代码中检索其配置以从源代码控制中安装tools/components/configs|3944201|Check+out文件以构建和部署我们的web应用程序control|3944202|Puppet+|3944203|3944204|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/List_of_disk_imaging_software^0|0|0|0|0|0|0|0|0|0|0|M|0|0|0|0|0|0|6|A|I|0|0|0|0|J|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1Z|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|20|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|21|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|22|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|23|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|24|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|25|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|26|8|@$T|27|U|28|V|W]]|9|@]|A|$]]|$1|X|3|-4|5|6|7|29|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|10|7|2A|8|@]|9|@]|A|$11|12]]|$1|13|3|14|5|6|7|2B|8|@]|9|@]|A|$]]|$1|15|3|-4|5|6|7|2C|8|@]|9|@]|A|$]]|$1|16|3|17|5|S|7|2D|8|@$T|2E|U|2F|V|W]]|9|@$T|2G|U|2H|1|2I]]|A|$]]|$1|18|3|19|5|S|7|2J|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|S|7|2K|8|@$T|2L|U|2M|V|W]]|9|@]|A|$]]|$1|1C|3|-4|5|6|7|2N|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|2O|8|@]|9|@]|A|$]]|$1|1F|3|-4|5|6|7|2P|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|E|7|2Q|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|E|7|2R|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|E|7|2S|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|E|7|2T|8|@]|9|@]|A|$]]|$1|1O|3|-4|5|6|7|2U|8|@]|9|@]|A|$]]|$1|1P|3|-4|5|6|7|2V|8|@]|9|@]|A|$]]]|1Q|$1R|$5|1S|1T|1U|A|$1V|1W]]]]

There are several options, and sometimes a combination of these is useful: 

<ul>
<li>automated installation</li>
<li>disk imaging</li>
<li>virtualization</li>
<li>source code control </li>
</ul>

Details on the various options:

<ol>
<li>Automated Installation Tools for automating installation and configuration of a workstation's various services, tools and config files:

<ul>
<li><a href="https://puppet.com/" rel="noreferrer">Puppet</a> has a learning curve but is powerful. You define classes of machines (development box, web server, etc.) and it then does what is necessary to install, configure, and keep the box in the proper state. You asked for one-click, but Puppet by default is zero-click, as it checks your machine periodically to make sure it is still configured as desired. It will detect when a file or mode has been changed, and fix the problem. I currently use this to maintain a handful of RedHat Linux boxes, though it's capable of handling thousands. (Does not support Windows as of 2009-05-08). </li>
<li><a href="http://www.cfengine.org/" rel="noreferrer">Cfengine</a> is another one. I've seen this used successfully at a shop with 70 engineers using RedHat Linux. Its limitations were part of the reason for Puppet.</li>
<li><a href="http://en.wikipedia.org/wiki/SmartFrog" rel="noreferrer">SmartFrog</a> is another tool for configuring hosts. It does support Windows.</li>
<li>Shell scripts. <a href="http://blog.rightscale.com/2007/08/07/configuring-servers-with-rightscripts/" rel="noreferrer">RightScale</a> has examples of how to configure an Amazon EC2 image using shell scripts.</li>
<li>Install packages. On a Unix box it's possible to do this entirely with packages, and on Windows msi may be an option. For example, <a href="http://studios.thoughtworks.com/rubyworks" rel="noreferrer">RubyWorks</a> provides you with a full Ruby on Rails stack, all by installing one package that in turn installs other packages via dependencies.</li>
</ul></li>
<li>Disk Images Then of course there are also <a href="http://en.wikipedia.org/wiki/List_of_disk_imaging_software" rel="noreferrer">disk imaging tools</a> for storing an image of a configured host such that it can be restored to another host. As with virtualization, this is especially nice for test boxes, since it's easy to restore things to a clean slate. Keeping things continuously up-to-date is still an issue--is it worth making new images just to propagate a configuration file change?</li>
<li><a href="http://en.wikipedia.org/wiki/Full_virtualization" rel="noreferrer">Virtualization</a> is another option, for example making copies of a Xen, VirtualPC, or VMWare image to create new hosts. This is especially useful with test boxes, as no matter what mess a test creates, you can easily restore to a clean, known state. As with disk imaging tools, keeping hosts up-to-date requires more manual steps and vigilance than if an automated install/config tool is used.</li>
<li>Source Code Control Once you've got the necessary tools installed/configured, then doing builds should be a matter of checking out what's needed from a source code repository and building it.</li>
</ol>

Currently I use a combination of the above to automate the process as follows:

<ul>
<li>Start with a barebones OS install on a VMWare guest</li>
<li>Run a shell script to install Puppet and retrieve its configs from source code control</li>
<li>Puppet to install tools/components/configs</li>
<li>Check out files from source code control to build and deploy our web application</li>
</ul>

blocks|key|4787390|text|在以前的地方，我们拥有SCM+(然后是clearcase和SVN)中的一切(我的意思是一切)。当一个新的开发人员可以加入时，他们安装了ClearCase%7CSVN并吸收了存储库。当您需要更新特定的库/工具时，这也会处理这种情况，因为您可以让开发团队更新他们的环境。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4787391|我们为此使用了两个代码库，因此代码和工具/配置位于不同的位置。|4787392|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

At a prior place we had everything (and I mean EVERYTHING) in SCM (clearcase then SVN). When a new developer can in they installed ClearCase|SVN and sucked down the repository. This also handles the case when you need to update a particular lib/tool as you can just have the dev teams update their environment.

We used two repo's for this so code and tools/config lived in separate places.

blocks|key|3944290|text|我强烈推荐DevStructure的蓝图。它是开源的，您的用例实际上正是我们最初编写该软件的原因。我们的目标有所改变，但它仍然是您所描述的完美工具。简而言之，您可以创建可重用的服务器配置-非常简单的配置管理。我希望这能帮到你!|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3944291|https://github.com/devstructure/blueprint+(Blueprint+@+Github)|offset|length|3944292|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/devstructure/blueprint^0|0|0|15|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

I highly recommend Blueprint from DevStructure. It's open-source and your use case is actually the exact reason we originally wrote the software. Our goals have somewhat changed, but it still is the perfect tool for what you are describing. In short, you can create reusable server configs - dead simple configuration management. I hope this helps!

<a href="https://github.com/devstructure/blueprint" rel="nofollow">https://github.com/devstructure/blueprint</a> (Blueprint @ Github)

blocks|key|4787501|text|我自己也在考虑这个问题。您还可以使用其他一些技术。下面是我目前正在设置的内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4787502|基于|4787503|PXE的预播安装镜像(Debian+Squeeze)。您可以启动裸机计算机(或新的虚拟设备)，并从PXE启动菜单中选择映像。这样做的主要优点是能够在物理机器上安装您的环境(除了已经提到的虚拟appliances).|unordered-list-item|4787504|Someone。我使用的是CFEngine，但这是一个类似的交易。如果你不想要一个严格的环境(即开发人员可以选择工具集的组合)，你可以使用你自己的deb包，这样新的开发人员就可以为example.|4787505|Slightly离题输入sudo+apt-get+install+acmecorp-eclipse-env或sudo+apt-get+install+acmecorp-intellij-env，但是如果你运行的是基于Debian的环境(例如Ubuntu)，可以考虑安装apt-cacher+(包代理)。除了节省带宽之外，它还将使您的安装速度更快(因为包被缓存在您的本地网络上)。|offset|length|style|CODE|4787506|4787507|entityMap^0|0|0|0|0|C|15|1I|16|3Q|A|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|T|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|V|8|@$K|W|L|X|M|N]|$K|Y|L|Z|M|N]|$K|10|L|11|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|Q|$]]

I've been thinking about this myself. There are some other technologies that you could throw into the mix. Here's what I'm currently setting up:

<ul>
<li>PXE based pre-seeded installation images (Debian Squeeze). You can start up a bare-metal machine (or new virtual appliance) and select the image from the PXE boot menu. This has the major advantage of being able to install your environment on physical machines (in addition to virtual appliances).</li>
<li>Someone already mentioned Puppet. I use CFEngine but it's a similar deal. Essentially your configuration is documented and centralized in policy files which are continually enforced by an agent on the client.</li>
<li>if you don't want a rigid environment (i.e. developers may choose a combination of tool-sets) you can roll your own deb packages so new devs can type <code>sudo apt-get install acmecorp-eclipse-env</code> or <code>sudo apt-get install acmecorp-intellij-env</code>, for example.</li>
<li>Slightly off-topic, but if you run a Debian based environment (i.e. Ubuntu), consider installing <code>apt-cacher</code> (package proxy). In addition to saving bandwidth, it will make your installations much faster (since packages are cached on your local network).</li>
</ul>

blocks|key|3944418|text|我偶然发现了这个问题，令我非常惊讶的是，还没有人提到Vagrant。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3944419|​|3944420|📷|atomic|3944421|3944422|正如Pete+TerMaat和其他人所提到的，虚拟化是管理和自动化开发环境的一种很好的方法。流浪基本上消除了设置这些虚拟盒子的痛苦。|3944423|几分钟之内，你就可以拥有一个你最喜欢的Linux发行版的全新副本并运行起来，并且provisioned的方式和你的生产服务器完全一样。|3944424|不用再为安装PHP、MySQL等而与OSX或Windows打架了。所有软件都在虚拟机中运行。您甚至可以使用vagrant+ssh通过SSH登录。如果你犯了一个错误或弄坏了什么东西，只需用vagrant+destroy命令，然后用vagrant+up命令重新开始。|style|CODE|3944425|Vagrant自动为你的本地文件系统创建一个synced+folder，这意味着你不需要在虚拟机中进行开发(即.使用Vim)。使用您选择的任何编辑器。|3944426|我现在几乎为我做的每个项目都创建了一个新的“流浪者盒子”。我的所有设置都保存在项目存储库中，因此很容易引入其他团队成员。他们只需要拉回回购，然后运行vagrant+up，他们就已经准备好了。|3944427|这也使得处理具有不同软件需求的项目变得更加容易。也许你有一些依赖于PHP5.3的项目，但是一些新的运行PHP5.4的项目。只需为该项目安装您想要的版本。|3944428|Check+it+out!|3944429|entityMap|0|LINK|mutability|MUTABLE|url|http://www.vagrantup.com/|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/18de6fe4eb9ff7e2a97f63bf764093e3.png|imageAlt|2|http://docs.vagrantup.com/v2/provisioning/index.html|3|http://docs.vagrantup.com/v2/synced-folders/index.html|4^0|Q|7|0|0|0|0|1|1|0|0|0|14|B|2|0|1H|B|2L|F|36|A|0|M|D|3|0|22|A|0|0|0|D|4|0^^$0|@$1|2|3|4|5|6|7|1I|8|@]|9|@$A|1J|B|1K|1|1L]]|C|$]]|$1|D|3|E|5|6|7|1M|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|1N|8|@]|9|@$A|1O|B|1P|1|1Q]]|C|$]]|$1|I|3|E|5|6|7|1R|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|1S|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|1T|8|@]|9|@$A|1U|B|1V|1|1W]]|C|$]]|$1|N|3|O|5|6|7|1X|8|@$A|1Y|B|1Z|P|Q]|$A|20|B|21|P|Q]|$A|22|B|23|P|Q]]|9|@]|C|$]]|$1|R|3|S|5|6|7|24|8|@]|9|@$A|25|B|26|1|27]]|C|$]]|$1|T|3|U|5|6|7|28|8|@$A|29|B|2A|P|Q]]|9|@]|C|$]]|$1|V|3|W|5|6|7|2B|8|@]|9|@]|C|$]]|$1|X|3|Y|5|6|7|2C|8|@]|9|@$A|2D|B|2E|1|2F]]|C|$]]|$1|Z|3|-4|5|6|7|2G|8|@]|9|@]|C|$]]]|10|$11|$5|12|13|14|C|$15|16]]|17|$5|18|13|19|C|$1A|1B|1C|-4]]|1D|$5|12|13|14|C|$15|1E]]|1F|$5|12|13|14|C|$15|1G]]|1H|$5|12|13|14|C|$15|16]]]]

I stumbled across this question and was very suprised that no one has mentioned <a href="http://www.vagrantup.com/" rel="noreferrer">Vagrant</a> yet.

<img src="https://i.stack.imgur.com/Lf6Q6.png" alt="Vagrant">

As Pete TerMaat and others have mentioned, virtualization is a great way to manage and automate development environments. Vagrant basically takes the pain away from setting up these virtual boxes.

Within minutes you can have a completely fresh copy of your favourite Linux distro up and running, and <a href="http://docs.vagrantup.com/v2/provisioning/index.html" rel="noreferrer">provisioned</a> exactly the same way your production server is.

No more fighting with OSX or Windows to get PHP, MySQL, etc. installed. All software lives and runs inside the virtual machine. You can even SSH in with <code>vagrant ssh</code>. If you make a mistake or break something, just <code>vagrant destroy</code> it, and <code>vagrant up</code> to start over fresh.

Vagrant automatically creates a <a href="http://docs.vagrantup.com/v2/synced-folders/index.html" rel="noreferrer">synced folder</a> to your local file system, meaning you don't need to develop within the virtual machine (ie. using Vim). Use whatever your editor of choice is.

I now create a new "Vagrant box" for almost every project I do. All my settings are saved into the project repository, so it's easy to bring on another team member. They simply have to pull the repo, and run <code>vagrant up</code>, and they are literally ready to go.

This also makes it much easier to handle projects that have different software requirements. Maybe you have some projects that rely on PHP 5.3, but some newer ones that run PHP 5.4. Just install the version you want for that project.

<a href="http://www.vagrantup.com/" rel="noreferrer">Check it out!</a>

blocks|key|3944455|text|在http://nsnihalsahu.github.io/devscript上试试DevScript吧。它只有一个命令，比如devscript+lamp、devscript+laravel或devscript+django。大约几分钟后，取决于你的网速|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3944456|entityMap|0|LINK|mutability|MUTABLE|url|http://nsnihalsahu.github.io/devscript^0|1R|E|26|H|2O|G|1|12|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]]|E|$]]|$1|F|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

Try out DevScript at <a href="http://nsnihalsahu.github.io/devscript" rel="nofollow">http://nsnihalsahu.github.io/devscript</a> .
Its one command like , 
<code>devscript lamp</code> or <code>devscript laravel</code> or <code>devscript django</code> . In around a few minutes ,depending on the speed of your internet co

blocks|key|1229057|text|如果您正在使用OSX并使用Rails。我的建议是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1229058|1229059|https://github.com/platform45/let-there-be-light|unordered-list-item|offset|length|1229060|https://github.com/thoughtbot/laptop|1229061|1229062|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|0|1C|0|0|0|10|1|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|U|8|@]|9|@$F|V|G|W|1|X]]|A|$]]|$1|H|3|I|5|E|7|Y|8|@]|9|@$F|Z|G|10|1|11]]|A|$]]|$1|J|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|D]]|R|$5|N|O|P|A|$Q|I]]]]

If you're using OSX and working with Rails. I'd suggest either: 

<ul>
<li><a href="https://github.com/platform45/let-there-be-light" rel="nofollow">https://github.com/platform45/let-there-be-light</a></li>
<li><a href="https://github.com/thoughtbot/laptop" rel="nofollow">https://github.com/thoughtbot/laptop</a></li>
</ul>

Every time a new developer joins the team or the computer a developer is using changes, the developer needs to do lots of work to setup the local development environment to make the current project work. As a SCRUM team we are trying to automate everything including deployment and tests so what I am asking is: is there a tool or a practice to make local development environment setup automated?

For example to setup my environment, first I had to install eclipse, then SVN, Apache, Tomcat, MySQL, PHP. After that I populated the DB and I had to do minor changes in the various configuration files etc... Is there a way to reduce this labor to one-click?

How to automate development environment setup?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

每当新的开发人员加入团队或开发人员正在使用的计算机发生变化时，开发人员都需要做大量的工作来设置本地开发环境，以使当前项目正常工作。作为一个SCRUM团队，我们正在尝试自动化所有的事情，包括部署和测试，所以我想问的是:有没有工具或实践可以让本地开发环境设置自动化？例如，要设置我的环境，首先我必须安装eclipse，然后是...

问如何自动设置开发环境？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何自动设置开发环境？EN