Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: NixOS/nixos-homepage
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 4c35487081a6
Choose a base ref
...
head repository: NixOS/nixos-homepage
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: cfe8aef4d446
Choose a head ref
  • 2 commits
  • 1 file changed
  • 1 contributor

Commits on Nov 10, 2020

  1. new item

    @garbas
    garbas committed Nov 10, 2020

    Unverified

    This user has not yet uploaded their public signing key.
    GPG key ID: A0E01EF44C27BF00
    Learn about vigilant mode
    Copy the full SHA
    e50326c View commit details

  2. cloud feature

    @garbas
    garbas committed Nov 10, 2020

    Unverified

    This user has not yet uploaded their public signing key.
    GPG key ID: A0E01EF44C27BF00
    Learn about vigilant mode
    Copy the full SHA
    cfe8aef View commit details
Showing with 67 additions and 47 deletions.
  1. +67 −47 overview.tt
114 changes: 67 additions & 47 deletions overview.tt
View file
Original file line number Diff line number Diff line change
@@ -128,87 +128,102 @@
</div>
</div>

<!--
<div>
[% PROCESS svg path="site-styles/assets/gfx-overview-gears.svg" %]
<div>
<h2>
Move fast and fix things: quickly discover bugs.
</h2>
<p>
Want to boost productivity? Choose a conflict-free development environment.
</p>
<div>
patching, reproducibility
</div>
</div>
</div>

<div>
[% PROCESS svg path="site-styles/assets/gfx-overview-gears.svg" %]
<div>
<h2>
Be carefree. Develop with no limits.
</h2>
<p>
Gives you the power to build and deploy software consistently on different machines. Save time, be carefree
and
rollback anytime to the previous version. Nix will make sure all dependencies are in place.
</p>
<div>
reproducibility
</div>
</div>
</div>

<div>
[% PROCESS svg path="site-styles/assets/gfx-overview-gears.svg" %]
<div>
<h2>
No conflicts with the operating system.
Is the previous version better? Rollback anytime.
</h2>
<p>
Securely install software with no risk of breaking anything down. Nix prevents conflicts not only between
multiple environments, but also with the operating system. All packages remain installed side-by-side even if
different users install packages with the conflicting dependencies.
Packages are never overwritten, and old versions are always stored.
Rollback to any previous version within milliseconds.
</p>
<ul>
<li>generations</li>
<li>garbage collection</li>
<li>atomic</li>
<li>nix store</li>
</ul>
<div>
explain /nix/store
<p>
profiles, generations, garbage collection
</p>
</div>
</div>
</div>

<div>
<!-- hacking, fun, party -->
[% PROCESS svg path="site-styles/assets/gfx-overview-gears.svg" %]
<div>
<h2>
Simple and consistent. Trust in your deployments.
<!-- TODO: "have fun" can be interpreted in the wrong way.
need to check with somebody english native
-->
It is important to have fun.
</h2>
<ul>
<li>generations</li>
<li>nix store</li>
</ul>
<p>
To eliminate the risk of leaving any parts behind, all operations are atomic. Nix sets everything in place and
once ready, there are only two possible outcomes. Upgrade was successful or upgrade did not happen.
We don't stop playing, because we grow old; we grow old because we stop
playing - George Bernard Shaw.
Use tools that allow you to play with different software as
you did when the job wasn't waiting for you the next day.
</p>
<div>
link farm
<p>
Install new software with no risk of breaking anything down. Nix
prevents conflicts not only between multiple development environments,
but also with the operating system. You work environment will stay
intact, but allow you to experiment.
</p>
<p>
We could write that because of Nix you will become a better
programmer. You probably will, just because you will be able to
expose yourself to more software. But none of this is relevant.
The most important thing is to have fun.
<strong>Without it, we get sick.</strong>
</p>
</div>
</div>
</div>

<div>
[% PROCESS svg path="site-styles/assets/gfx-overview-gears.svg" %]
[% PROCESS svg path="site-styles/assets/gfx-overview-cloud.svg" %]
<div>
<h2>
Is the previous version better? Rollback anytime.
From zero to cloud.
</h2>
<ul>
<li>cloud images</li>
<li>docker images</li>
<li>devops</li>
</ul>
<p>
Packages are never overwritten, and old versions are always stored. Roll back to any previous version within
milliseconds. Yes, again with the trustworthy atomic operation.
Use the same tool to build one project or even one hundred projects,
configure machines and deploy to the cloud. Thanks to the extensible
Nix language, it's easy to compose parts together with little overhead.
</p>
<div>
profiles, generations, garbage collection
<p>
Using one tool to build Amazon EC2, Google Cloud, Azure, Virtualbox,
KVM and other images in a declarative way.
You can then deploy them with the tools you already know and use.
</p>
<p>
Nix takes building docker images to the next level. Forget
<code>Dockerfile</code> and have a peace of mind with declarative
approach that Nix gives you. Automatically calculate the best
layer structure for your docker image and build minimal images
that include only software that is needed for you project. Nix and
Docker is a match made in heaven.
</p>
</div>
</div>
</div>
<!--

<div>
[% PROCESS svg path="site-styles/assets/gfx-overview-gears.svg" %]
@@ -223,7 +238,12 @@
All that in a truly all-inclusive build environment: NixOS.
</p>
<div>
link farm
declarative configuration / NixOS
<p>
To eliminate the risk of leaving any parts behind, all operations are atomic. Nix sets everything in place and
once ready, there are only two possible outcomes. Upgrade was successful or upgrade did not happen.
</p>
</div>
</div>
</div>