Warning bar on the side and backwards compatibility promise.
This commit is contained in:
Mitchell Hashimoto
parent
db789d8ff7
commit
b3b138d86a
|
|
@ -0,0 +1,9 @@
|
|||
<div class="block warning">
|
||||
<h1>Warning!</h1>
|
||||
|
||||
<p>
|
||||
Vagrant is <strong>beta software</strong>. Anything
|
||||
can change. Read more about our promise to backwards
|
||||
compatibility <a href="/docs/backwards-compatibility.html">here</a>.
|
||||
</p>
|
||||
</div>
|
||||
|
|
@ -1,17 +1,21 @@
|
|||
{% include header.html %}
|
||||
<div class="grid_3 alpha sidebar">
|
||||
<ol>
|
||||
<li><a href="/docs/getting-started/index.html">Overview</a></li>
|
||||
<li><a href="/docs/getting-started/why.html">Why Vagrant?</a></li>
|
||||
<li><a href="/docs/getting-started/introduction.html">Introduction</a></li>
|
||||
<li><a href="/docs/getting-started/setup.html">Project Setup</a></li>
|
||||
<li><a href="/docs/getting-started/boxes.html">Boxes</a></li>
|
||||
<li><a href="/docs/getting-started/provisioning.html">Provisioning</a></li>
|
||||
<li><a href="/docs/getting-started/ports.html">Port Forwarding</a></li>
|
||||
<li><a href="/docs/getting-started/packaging.html">Packaging</a></li>
|
||||
<li><a href="/docs/getting-started/teardown.html">Teardown</a></li>
|
||||
<li><a href="/docs/getting-started/rebuild.html">Rebuild Instantly</a></li>
|
||||
</ol>
|
||||
<div class="block">
|
||||
<ol>
|
||||
<li><a href="/docs/getting-started/index.html">Overview</a></li>
|
||||
<li><a href="/docs/getting-started/why.html">Why Vagrant?</a></li>
|
||||
<li><a href="/docs/getting-started/introduction.html">Introduction</a></li>
|
||||
<li><a href="/docs/getting-started/setup.html">Project Setup</a></li>
|
||||
<li><a href="/docs/getting-started/boxes.html">Boxes</a></li>
|
||||
<li><a href="/docs/getting-started/provisioning.html">Provisioning</a></li>
|
||||
<li><a href="/docs/getting-started/ports.html">Port Forwarding</a></li>
|
||||
<li><a href="/docs/getting-started/packaging.html">Packaging</a></li>
|
||||
<li><a href="/docs/getting-started/teardown.html">Teardown</a></li>
|
||||
<li><a href="/docs/getting-started/rebuild.html">Rebuild Instantly</a></li>
|
||||
</ol>
|
||||
</div>
|
||||
|
||||
{% include block_beta_warning.html %}
|
||||
</div>
|
||||
<div class="grid_9 omega guide">
|
||||
{{ content }}
|
||||
|
|
|
|||
|
|
@ -1,13 +1,17 @@
|
|||
{% include header.html %}
|
||||
<div class="grid_3 alpha sidebar">
|
||||
<ol>
|
||||
<li><a href="/docs/user-guide/index.html">Overview</a></li>
|
||||
<li><a href="/docs/user-guide/commands.html">Commands</a></li>
|
||||
<li><a href="/docs/user-guide/vagrantfile.html">Vagrantfile</a></li>
|
||||
<li><a href="/docs/user-guide/provisioning.html">Provisioning</a></li>
|
||||
<li><a href="/docs/user-guide/boxes.html">Boxes</a></li>
|
||||
<li><a href="/docs/user-guide/rake.html">Rake Integration</a></li>
|
||||
</ol>
|
||||
<div class="block">
|
||||
<ol>
|
||||
<li><a href="/docs/user-guide/index.html">Overview</a></li>
|
||||
<li><a href="/docs/user-guide/commands.html">Commands</a></li>
|
||||
<li><a href="/docs/user-guide/vagrantfile.html">Vagrantfile</a></li>
|
||||
<li><a href="/docs/user-guide/provisioning.html">Provisioning</a></li>
|
||||
<li><a href="/docs/user-guide/boxes.html">Boxes</a></li>
|
||||
<li><a href="/docs/user-guide/rake.html">Rake Integration</a></li>
|
||||
</ol>
|
||||
</div>
|
||||
|
||||
{% include block_beta_warning.html %}
|
||||
</div>
|
||||
<div class="grid_9 omega guide">
|
||||
{{ content }}
|
||||
|
|
|
|||
|
|
@ -232,6 +232,11 @@ blockquote {
|
|||
height: 275px;
|
||||
}
|
||||
|
||||
#content h1.top {
|
||||
margin-top: 0px;
|
||||
margin-left: 0px;
|
||||
}
|
||||
|
||||
.guide h1 {
|
||||
margin-left: 0;
|
||||
margin-top: 5px;
|
||||
|
|
@ -245,13 +250,33 @@ blockquote {
|
|||
------------------------------ */
|
||||
|
||||
.sidebar {
|
||||
border: 1px dotted #DDD;
|
||||
background-color: #EEEEEE;
|
||||
padding: 10px;
|
||||
margin-top: 10px;
|
||||
margin-right: 8px;
|
||||
}
|
||||
|
||||
.sidebar .block h1 {
|
||||
font-size: 20px;
|
||||
margin: 0;
|
||||
margin-top: 5px;
|
||||
color: inherit;
|
||||
font-weight: bold;
|
||||
}
|
||||
|
||||
.sidebar .block {
|
||||
border: 1px dotted #DDD;
|
||||
background-color: #EEEEEE;
|
||||
padding: 10px;
|
||||
margin-top: 10px;
|
||||
}
|
||||
|
||||
.sidebar .block.warning {
|
||||
border: 1px dotted #9F6000;
|
||||
background-color: #FEEFB3;
|
||||
color: #333;
|
||||
padding-top: 0px;
|
||||
padding-bottom: 0px;
|
||||
}
|
||||
|
||||
|
||||
.sidebar ol, .sidebar ul {
|
||||
margin-bottom: 0px;
|
||||
}
|
||||
|
|
|
|||
|
|
@ -0,0 +1,30 @@
|
|||
---
|
||||
layout: default
|
||||
title: Backwards Compatibility
|
||||
---
|
||||
|
||||
<h1 class="top">Backwards Compatibility Promise</h1>
|
||||
|
||||
Vagrant has set high goals for itself to **change the way web
|
||||
developers work,** but we know that to achieve that, Vagrant needs
|
||||
to be a _stable and reliable_ tool. One of the main benefits of Vagrant
|
||||
is that you should be able to go back to a Vagrant powered project
|
||||
a year later and still be able to build its environment as if it were
|
||||
made the same day. We plan to uphold the promise to this feature, but to
|
||||
do so we first need to settle on a _standard API and configuration specification_.
|
||||
|
||||
That being said, **our promise** is to provide backwards compatibility
|
||||
for every _major version_ of Vagrant. For example, once Vagrant 1.0 is released, we
|
||||
promise to support that version forever (one way or another).
|
||||
|
||||
To reiterate our point, you should be able to go back to a Vagrant 1.0 project
|
||||
when Vagrant 4.2 is released and still be able to get it up and running with a
|
||||
single command:
|
||||
|
||||
{% highlight bash %}
|
||||
$ vagrant up
|
||||
{% endhighlight %}
|
||||
|
||||
It is a bold statement and a promise which we're sure will introduce significant
|
||||
development challenges in the future, but we've discussed it and we're sure
|
||||
we can take this head on and we're committed to keeping our promise.
|
||||
|
|
@ -22,7 +22,7 @@ to create its virtual machines and then uses [Chef](http://www.opscode.org/chef)
|
|||
|
||||
### For Companies
|
||||
|
||||
If you've ever maintained a large web application one of the hardest parts is onboarding new resources.
|
||||
If you've ever maintained a large web application, one of the hardest parts is onboarding new resources.
|
||||
Message queues, caching, database servers and other infrastructure pieces mean a lot of installation
|
||||
and a lot more configuration (see [Insanity](http://www.robbyonrails.com/articles/2010/02/08/installing-ruby-on-rails-passenger-postgresql-mysql-oh-my-zsh-on-snow-leopard-fourth-edition)). Vagrant gives you the tools to build a development environment once and then easily distribute it to
|
||||
and a lot more configuration (see [case-in-point: insanity](http://www.robbyonrails.com/articles/2010/02/08/installing-ruby-on-rails-passenger-postgresql-mysql-oh-my-zsh-on-snow-leopard-fourth-edition)). Vagrant gives you the tools to build a development environment once and then easily distribute it to
|
||||
new members of your development team so you can get them to work and saving time, money and frustration.
|
||||
|
|
|
|||
Loading…
Reference in New Issue