Skip to content

H
homepage
Commit 831cb127 authored by Poul-Henning Kamp's avatar Poul-Henning Kamp
Browse files
Options

Remove the "news" page, we seem to forget to use it and rely instead 

on the frontpage. (dogfood and repo info migrated to elsewhere)

Prune the frontpage.
parent 6ea8b7a3
Hide whitespace changes
Inline Side-by-side
Showing with 16 additions and 406 deletions
R1/source/_templates/navigation.html
View file @ 831cb127
<h3>Index</h3>
<hr />
<ul>
<li class="toctree-l1">
<a href="{{ pathto("news/index") }}">News</a>
</li>
<li class="toctree-l1">
<a href="{{ pathto("releases/index") }}">Download</a>
</li>
......
R1/source/faq/index.rst
View file @ 831cb127
......@@ -7,5 +7,11 @@ Questions and Answers
comm
find
what
.. toctree::
:maxdepth: 1
dogfood
who
R1/source/index.rst
View file @ 831cb127
......@@ -26,177 +26,17 @@ attack, please see :ref:`vsv00001`
Varnish versions 4.0.5, 4.1.8 and 5.1.3 are now available. See
:ref:`vsv00001` for details.
2017-06-28 - Maintenance release 4.1.7
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Varnish Cache 4.1.7 has been released and is ready for
download. Packages will be made available for the usual platforms.
The release contains bug fixes and minor enhancements. Among the bug
fixes is `#1764 - Correctly honor nuke_limit parameter
<https://github.com/varnishcache/varnish-cache/issues/1764>`_. Before
this fix, Varnish would not limit the number of LRU nukes to fit a new
object into the cache. Now nuke_limit will be honored.
Pål Hermunn Johansen, Varnish Software
2017-04-27 - Maintenance release 4.1.6
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Varnish Cache 4.1.6 has been released and is ready for download. This
is a maintenance release with bug fixes and some minor
enhancements. Details can be found in the changelog.
Pål Hermunn Johansen, Varnish Software Group
2017-04-11 - Varnish 5.1 release post mortem
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
`Poul-Henning looks at the last couple of weeks </docs/trunk/phk/somethinghappened.html>`_
2017-04-07 - Varnish 5.1.2 is here too
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
We decided that 5.1.1 had too many bugs, none of the truly horrible,
but there were too many asserts for our taste.
We fixed that, and thanks to Simon and Xcir, the HTTP/2 code got a good
beating out and is now much more stable as a result.
EL7, Debian-Jessie, Ubuntu-Trusty and Ubuntu-Xenial packages can be found
on `PackageCloud.io <https://packagecloud.io/varnishcache/varnish5>`_
:download:`Source package can be found here <releases/varnish-5.1.2.tgz>`
2017-03-16 - Varnish 5.1.1 is here
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Come and get it...
Our `list of changes and other good reasons to update to 5.1 </docs/trunk/whats-new/changes-5.1.html>`_
EL7, Debian-Jessie, Ubuntu-Trusty and Ubuntu-Xenial packages can be found
on `PackageCloud.io <https://packagecloud.io/varnishcache/varnish5>`_
:download:`Source package can be found here <releases/varnish-5.1.1.tgz>`
And yes, it is called 5.1.1 and we're one day late and it's all my
fault. I'll tell you about it later, but first I have to do some
housekeeping.
/phk
2017-02-25 - 5.1 Release in 18 days
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Varnish release 5.1 is due on march 15, in only 18 days, and we
are trying polish and test the release as much as we can before
then.
If you can, please give the trunk release from github a workout
and report any trouble you find.
/phk
2017-02-09 - Maintenance release 4.1.5
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Varnish Cache 4.1.5 has been released and is ready for download. This
is a maintenance release with bug fixes.
Pål Hermunn Johansen, Varnish Software Group
2017-01-05 - Source Code Coverage
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I usually brag that we have 90%+ automatic test coverage in Varnish,
and that comes with a couple of footnotes.
The main one is that we don't automatically test the curses(3) based
tools (varnish{hist|top|stat|...}) - only because I havn't found a
way to do so.
For 2017 I've raised the bar: from now our goal is 90%+ on *all* our
source code.
At the same time, I have retooled our code coverage test scripts
so the `GCOV results can be seen online </gcov>`_ .
Presently at 81.8%, but we'll get there...
/phk
2016-12-21 - Project server upgraded
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Now running FreeBSD 11-RELEASE /phk
2016-12-02 - Maintenance release of 4.1.4, 4.0 is End Of Life
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Varnish Cache 4.1.4 has been released and is ready for download. This
is a maintenance release with bug fixes and performance enhancements.
In other news, Varnish Cache 4.0 has reached End Of Life, and with
this we have released Varnish Cache 4.0.4. This contains all the last
fixes from git, and there will be no 4.0.5. Please upgrade to 4.1 or 5.0
as soon as you can.
Pål Hermunn Johansen, Varnish Software Group
2016-11-21 - New Tool in Town
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I finally sat down and wrote a Varnish specific "Continuous
Integration" tool, and people are busy starting it on the various
machines we use for testing in the project.
You can `see the result(s) here. </vtest/index.html>`_
If you want to run a "sandbox" for us, you just need to run
`a small simple shell-script
<https://github.com/varnishcache/varnish-cache/blob/master/tools/vtest.sh>`_
- there is `no need for a Java Runtime or anything else.
</docs/trunk/phk/trialerror.html>`_
/phk
2016-09-27 - Send us (more) money!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If we want to keep up the same activity level as the last couple
of years, we need €2000/month to buy more of Poul-Hennings time.
So if Varnish improves your company's profit, please invest in a
one-time or recurring `Varnish Moral License <http://phk.freebsd.dk/VML>`_
to help fund the projects future.
Thanks in advance!
And a big thanks to the companies already sponsoring Varnish:
* Fastly
* Varnish-Software
* UPLEX
* [your companys name could have been here...]
2016-09-15 - Varnish 5.0
~~~~~~~~~~~~~~~~~~~~~~~~
Varnish Cache 5.0.0 has been released! /Lasse /phk
See:
Package repository status
-------------------------
* :ref:`Releases`
* `Release Note </docs/5.0/whats-new/relnote-5.0.html>`_
* `Upgrading </docs/5.0/whats-new/upgrading-5.0.html>`_
* `Changes </docs/5.0/whats-new/changes-5.0.html>`_
The official Linux (apt/yum) package repositories are now located
at Packagecloud.io.
A list of all available repositories can be found at:
https://packagecloud.io/varnishcache
(And yes, we're dog-food running it on the varnish-cache.org site)
The old http://repo.varnish-cache.org/ is going to be removed on the 31st of August.
For more details on packages, see :ref:`Releases & Downloads <releases>`
Privacy
-------
......@@ -217,7 +57,6 @@ they collect, it will be discontinued.
intro/index
security/index
news/index
business/index
faq/index
releases/index
......
R1/source/news/20160411_website.rst deleted 100644 → 0
View file @ 6ea8b7a3
.. _20160411_website:
We have a new website
=====================
Well, sorta...
As part of the server migration, we want to redo the project homepage,
but as is so often the case in volunterism, something happened, and
then something else came in the way and ...
So this temporary home-page happened, and since nothing is as permanent
as that which is erected as temporary, the Tower of Eiffel comes to mind,
you might have to get used to this page.
We'll see where it goes...
2016-04-11 /phk
R1/source/news/20160425_website.rst deleted 100644 → 0
View file @ 6ea8b7a3
.. _20160425_website:
How our website works
=====================
One of the major reasons for the website upgrade the Varnish Project
has been going through this month, was in an effort to eat more of
our own dogfood.
The principle of eating your own dogfood is important for software
quality, that is how you experience what your users are dealing with
and I am not the least ashamed to admit that several obvious improvements
have already appeared on my TODO list as a result of this transition.
But it is also important to externalize what you learn doing so, and
therefore I thought I would document here how the projects new "internal
IT" works.
Hardware
--------
Who cares?
Yes, we use some kind of hardware, but to be honest I don't know what
it is.
Our primary site runs on a `RootBSD 'Omega' <https://www.rootbsd.net/>`_
virtual server somewhere near CDG/Paris.
And as backup/integration/testing server we can use any server,
virtual or physical, as long as it has a internet connection and
contemporary performance, because the entire install is scripted
and under version control (more below)
Operating System
----------------
So, dogfood: Obviously FreeBSD.
Apart from the obvious reason that I wrote a lot of FreeBSD and
can get world-class support by bugging my buddies about it, there
are two equally serious reasons for the Varnish Project to run on
FreeBSD: Dogfood and jails.
Varnish Cache is not "software for Linux", it is software for any
competent UNIX-like operating system, and FreeBSD is our primary
"keep us honest about this" platform.
Jails
-----
You have probably heard about Docker and Containers, but FreeBSD
have had jails
`since I wrote them in 1998 <http://phk.freebsd.dk/sagas/jails.html>`_
and they're a wonderful way to keep your server installation
sane.
We currently have three jails:
* Hitch - runs the `Hitch SSL proxy <https://hitch-tls.org/>`_
* Varnish - <a href="rimshot.mp3">You guessed it</a>
* Tools - backend webserver, currently `ACME Labs' thttpd <http://acme.com/software/thttpd/>`_
Script & Version Control All The Things
---------------------------------------
We have a git repos with shell scripts which create these jails
from scratch and also a script to configure the host machine
properly.
That means that the procedure to install a clone of the server
is, unabridged::
# Install FreeBSD 10.3 (if not already done by hosting)
# Configure networking (if not already done by hosting)
# Set the clock
service ntpdate forcestart
# Get git
env ASSUME_ALWAYS_YES=yes pkg install git
# Clone the private git repo
git clone ssh://example.com/root/Admin
# Edit the machines IP numbers in /etc/pf.conf
# Configure the host
sh build_host.sh |& tee _.bh
# Build the jails
foreach i (Tools Hitch Varnish)
(cd $i ; sh build* |& tee _.bj)
end
From bare hardware to ready system in 15-30 minutes.
It goes without saying that this git repos contains stuff
like ssh host keys, so it should *not* go on github.
Backups
-------
Right now there is nothing we need to backup.
When I move the mailserver/mailman/mailing lists over, those will
need to be backed up, but here the trick is to *only* backup the
minimal set of files, and in a "exchange" format, so that future
migrations and upgrades can slurp them in right away.
The Homepage
------------
The new homepage is built with `Sphinx <http://www.sphinx-doc.org/>`_
and lives in its own
`github project <https://github.com/varnishcache/homepage>`_ (Pull requests
are very welcome!)
We have taken snapshots of some of the old webproperties, Trac, the
Forum etc as static HTML copies.
Why on Earth...
---------------
It is a little bit tedious to get a setup like this going, whenever
you tweak some config file, you need to remember to pull the change
back out and put it in your Admin repos.
But that extra effort pays of so many times later.
You never have to wonder "who made that change and why" or even try
to remember what changes were needed in the first place.
For us as a project, it means, that all our sysadmin people
can build a clone of our infrastructure, if they have a copy of
our "Admin" git repos and access to github.
And when `FreeBSD 11 <https://www.youtube.com/watch?v=KOO5S4vxi0o>`_
comes out, or a new version of sphinx or something else, mucking
about with things until they work can be done at leisure without
guess work.
For instance I just added the forum snapshot, by working out all
the kinks on one of my test-machines.
Once it was as I wanted it, I pushed the changes the live machine and then::
varnishadm vcl.use backup
# The 'backup' VCL does a "pass" of all traffic to my server
cd Admin
git pull
cd Tools
sh build_j_tools.sh |& tee _.bj
varnishadm vcl.load foobar varnish-live.vcl
varnishadm vcl.use foobar
For a few minutes our website was a bit slower (because of the
extra Paris-Denmark hop), but there was never any interruption.
And by doing it this way, I *know* it will work next time also.
2016-04-25 /phk
All that buzz about "reproducible builds" ? Yeah, not a new idea.
R1/source/news/index.rst deleted 100644 → 0
View file @ 6ea8b7a3
News, Dates & Events
====================
* :ref:`2016-04-25 How our website works <20160425_website>`
* :ref:`2016-04-11 New Website <20160411_website>`
Next major release
-------------------
* 2017-09-xx Varnish 5.2 or 6.0 (not yet decided)
.. toctree::
:hidden:
20160425_website.rst
20160411_website.rst
Package repository status
-------------------------
The official (apt/yum) package repositories are now located at Packagecloud.io.
A list of all available repositories can be found at:
https://packagecloud.io/varnishcache
The old http://repo.varnish-cache.org/ is going to be removed on the 31st of August.
For more details on packages, see :ref:`Releases & Downloads <releases>`
Past events
-----------
* 2016-06-17 VarnishCon 2016 - Amsterdam
* 2015-12-04 VUG10 - Rotterdam
* 2014-11-19 VUG9 - Barcelona
* 2013-11-28 VUG8 - Berlin
* 2013-05-30 VUG7 - New York
* 2012-10-05 VUG6 - London
* 2012-03-22 VUG5 - Paris
* 2012-09-28 VUG4 - Baltimore
* 2011-02-14 VUG3 - Amsterdam
* 2010-03-29 VUG2 - Amsterdam
* 2009-09-21 VUG1 - London
R1/source/releases/index.rst
View file @ 831cb127
......@@ -109,6 +109,7 @@ Older Releases
.. toctree::
:maxdepth: 1
rel5.2.0
rel5.1.3
rel5.1.2
rel5.1.1
......
R1/source/tips/contribdoc/index.rst
View file @ 831cb127
......@@ -4,7 +4,7 @@ How to contribute documentation to varnish-cache.org
====================================================
This is where we walk you through the mechanics of adding content to
varnish-cache.org (see phk's note :ref:`20160425_website` for an
varnish-cache.org (see phk's note :ref:`dogfood` for an
insight into the innards of site).
Git Repository
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment