Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

Commit

Permalink
Improved documentation index
Browse files Browse the repository at this point in the history
  • Loading branch information
ellmetha committed Feb 13, 2017
1 parent 8cdc5d2 commit 3d01c47
Showing 1 changed file with 9 additions and 9 deletions.
18 changes: 9 additions & 9 deletions docs/_templates/indexcontent.html
Original file line number Diff line number Diff line change
Expand Up @@ -13,22 +13,22 @@ <h1>LXD-Nomad</h1>
<p>LXD-Nomad is a wrapper around <a href="https://www.ubuntu.com/cloud/lxd" target="_blank">LXD</a> that allows developers to orchestrate their development environments using a worklow similar to Vagrant.</p>
</div>
<div class="figure align-center" id="id3">
<h2>Why use LXD-Nomad?</h2>
</div>
<div class="figure align-center" id="id4">
<p><strong>It's fast.</strong> LXD-Nomad is much <em>much</em> faster than a typical Vagrant + Virtualbox setup.</p>
<p><strong>Multi-arch.</strong> Vagrant has been designed with Virtualbox and x86 in mind. Even if you use alternative providers, you’re going to have to jump through inelegant hoops to have your Vagrantfile work on x86 and arm (for example) at the same time because the very concept of a Vagrant box is arch-specific.</p>
<p><strong>Simpler.</strong> When working with containers, much of the complexity of Vagrant becomes useless. Why the need for special "vagrant-prepared" boxes when <code class="docutils literal"><span class="pre">lxc exec</span></code> is available? It's much simpler to use whatever images are provided directly by LXD. By removing the need to manage boxes, nomad suddenly becomes much simpler (a simple wrapper around lxd, really).</p>
</div>
<div class="figure align-center" id="id5">
<h2>Features</h2>
</div>
<div id="features_wrapper">
<div id="features_wrapper" class="figure">
<div class="feature"><span class="fa fa-cubes">&nbsp;Multi-container</span></div>
<div class="feature"><span class="fa fa-gears">&nbsp;Multi-arch</span></div>
<div class="feature"><span class="fa fa-bolt">&nbsp;Fast &amp; Intuitive</span></div>
<div class="feature"><span class="fa fa-folder">&nbsp;Shared folders</span></div>
<div class="feature"><span class="fa fa-linux">&nbsp;Various distributions</span></div>
<div class="feature"><span class="fa fa-rocket">&nbsp;Automated provisioning</span></div>
</div>
<div class="figure align-center" id="id5">
<h2>Why use LXD-Nomad?</h2>
</div>
<div class="figure align-center" id="id6">
<p><strong>It's fast.</strong> LXD-Nomad is much <em>much</em> faster than a typical Vagrant + Virtualbox setup.</p>
<p><strong>Multi-arch.</strong> Vagrant has been designed with Virtualbox and x86 in mind. Even if you use alternative providers, you’re going to have to jump through inelegant hoops to have your Vagrantfile work on x86 and arm (for example) at the same time because the very concept of a Vagrant box is arch-specific.</p>
<p><strong>Simpler.</strong> When working with containers, much of the complexity of Vagrant becomes useless. Why the need for special "vagrant-prepared" boxes when <code class="docutils literal"><span class="pre">lxc exec</span></code> is available? It's much simpler to use whatever images are provided directly by LXD. By removing the need to manage boxes, nomad suddenly becomes much simpler (a simple wrapper around lxd, really).</p>
</div>
{% endblock body %}

0 comments on commit 3d01c47

Please sign in to comment.