Commit 05160ea1 authored by Poul-Henning Kamp's avatar Poul-Henning Kamp

Add a Interrim homepage based on sphinx

parent 0a3ba9e3
# Makefile for Sphinx documentation
#
# You can set these variables from the command line.
SPHINXOPTS =
SPHINXBUILD = sphinx-build
PAPER =
BUILDDIR = build
# User-friendly check for sphinx-build
ifeq ($(shell which $(SPHINXBUILD) >/dev/null 2>&1; echo $$?), 1)
$(error The '$(SPHINXBUILD)' command was not found. Make sure you have Sphinx installed, then set the SPHINXBUILD environment variable to point to the full path of the '$(SPHINXBUILD)' executable. Alternatively you can add the directory with the executable to your PATH. If you don't have Sphinx installed, grab it from http://sphinx-doc.org/)
endif
# Internal variables.
PAPEROPT_a4 = -D latex_paper_size=a4
PAPEROPT_letter = -D latex_paper_size=letter
ALLSPHINXOPTS = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) source
# the i18n builder cannot share the environment and doctrees with the others
I18NSPHINXOPTS = $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) source
.PHONY: help clean html dirhtml singlehtml pickle json htmlhelp qthelp devhelp epub latex latexpdf text man changes linkcheck doctest coverage gettext
all: html
pub: html
cd build/html && scp -C -P200 -r . \
root@r.varnish-cache.org:/usr/local/www/apache24/data/
help:
@echo "Please use \`make <target>' where <target> is one of"
@echo " html to make standalone HTML files"
@echo " dirhtml to make HTML files named index.html in directories"
@echo " singlehtml to make a single large HTML file"
@echo " pickle to make pickle files"
@echo " json to make JSON files"
@echo " htmlhelp to make HTML files and a HTML help project"
@echo " qthelp to make HTML files and a qthelp project"
@echo " applehelp to make an Apple Help Book"
@echo " devhelp to make HTML files and a Devhelp project"
@echo " epub to make an epub"
@echo " latex to make LaTeX files, you can set PAPER=a4 or PAPER=letter"
@echo " latexpdf to make LaTeX files and run them through pdflatex"
@echo " latexpdfja to make LaTeX files and run them through platex/dvipdfmx"
@echo " text to make text files"
@echo " man to make manual pages"
@echo " texinfo to make Texinfo files"
@echo " info to make Texinfo files and run them through makeinfo"
@echo " gettext to make PO message catalogs"
@echo " changes to make an overview of all changed/added/deprecated items"
@echo " xml to make Docutils-native XML files"
@echo " pseudoxml to make pseudoxml-XML files for display purposes"
@echo " linkcheck to check all external links for integrity"
@echo " doctest to run all doctests embedded in the documentation (if enabled)"
@echo " coverage to run coverage check of the documentation (if enabled)"
clean:
rm -rf $(BUILDDIR)/*
html:
$(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
@echo
@echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
dirhtml:
$(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml
@echo
@echo "Build finished. The HTML pages are in $(BUILDDIR)/dirhtml."
singlehtml:
$(SPHINXBUILD) -b singlehtml $(ALLSPHINXOPTS) $(BUILDDIR)/singlehtml
@echo
@echo "Build finished. The HTML page is in $(BUILDDIR)/singlehtml."
pickle:
$(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) $(BUILDDIR)/pickle
@echo
@echo "Build finished; now you can process the pickle files."
json:
$(SPHINXBUILD) -b json $(ALLSPHINXOPTS) $(BUILDDIR)/json
@echo
@echo "Build finished; now you can process the JSON files."
htmlhelp:
$(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) $(BUILDDIR)/htmlhelp
@echo
@echo "Build finished; now you can run HTML Help Workshop with the" \
".hhp project file in $(BUILDDIR)/htmlhelp."
qthelp:
$(SPHINXBUILD) -b qthelp $(ALLSPHINXOPTS) $(BUILDDIR)/qthelp
@echo
@echo "Build finished; now you can run "qcollectiongenerator" with the" \
".qhcp project file in $(BUILDDIR)/qthelp, like this:"
@echo "# qcollectiongenerator $(BUILDDIR)/qthelp/VarnishCache.qhcp"
@echo "To view the help file:"
@echo "# assistant -collectionFile $(BUILDDIR)/qthelp/VarnishCache.qhc"
applehelp:
$(SPHINXBUILD) -b applehelp $(ALLSPHINXOPTS) $(BUILDDIR)/applehelp
@echo
@echo "Build finished. The help book is in $(BUILDDIR)/applehelp."
@echo "N.B. You won't be able to view it unless you put it in" \
"~/Library/Documentation/Help or install it in your application" \
"bundle."
devhelp:
$(SPHINXBUILD) -b devhelp $(ALLSPHINXOPTS) $(BUILDDIR)/devhelp
@echo
@echo "Build finished."
@echo "To view the help file:"
@echo "# mkdir -p $$HOME/.local/share/devhelp/VarnishCache"
@echo "# ln -s $(BUILDDIR)/devhelp $$HOME/.local/share/devhelp/VarnishCache"
@echo "# devhelp"
epub:
$(SPHINXBUILD) -b epub $(ALLSPHINXOPTS) $(BUILDDIR)/epub
@echo
@echo "Build finished. The epub file is in $(BUILDDIR)/epub."
latex:
$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
@echo
@echo "Build finished; the LaTeX files are in $(BUILDDIR)/latex."
@echo "Run \`make' in that directory to run these through (pdf)latex" \
"(use \`make latexpdf' here to do that automatically)."
latexpdf:
$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
@echo "Running LaTeX files through pdflatex..."
$(MAKE) -C $(BUILDDIR)/latex all-pdf
@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
latexpdfja:
$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
@echo "Running LaTeX files through platex and dvipdfmx..."
$(MAKE) -C $(BUILDDIR)/latex all-pdf-ja
@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
text:
$(SPHINXBUILD) -b text $(ALLSPHINXOPTS) $(BUILDDIR)/text
@echo
@echo "Build finished. The text files are in $(BUILDDIR)/text."
man:
$(SPHINXBUILD) -b man $(ALLSPHINXOPTS) $(BUILDDIR)/man
@echo
@echo "Build finished. The manual pages are in $(BUILDDIR)/man."
texinfo:
$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
@echo
@echo "Build finished. The Texinfo files are in $(BUILDDIR)/texinfo."
@echo "Run \`make' in that directory to run these through makeinfo" \
"(use \`make info' here to do that automatically)."
info:
$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
@echo "Running Texinfo files through makeinfo..."
make -C $(BUILDDIR)/texinfo info
@echo "makeinfo finished; the Info files are in $(BUILDDIR)/texinfo."
gettext:
$(SPHINXBUILD) -b gettext $(I18NSPHINXOPTS) $(BUILDDIR)/locale
@echo
@echo "Build finished. The message catalogs are in $(BUILDDIR)/locale."
changes:
$(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) $(BUILDDIR)/changes
@echo
@echo "The overview file is in $(BUILDDIR)/changes."
linkcheck:
$(SPHINXBUILD) -b linkcheck $(ALLSPHINXOPTS) $(BUILDDIR)/linkcheck
@echo
@echo "Link check complete; look for any errors in the above output " \
"or in $(BUILDDIR)/linkcheck/output.txt."
doctest:
$(SPHINXBUILD) -b doctest $(ALLSPHINXOPTS) $(BUILDDIR)/doctest
@echo "Testing of doctests in the sources finished, look at the " \
"results in $(BUILDDIR)/doctest/output.txt."
coverage:
$(SPHINXBUILD) -b coverage $(ALLSPHINXOPTS) $(BUILDDIR)/coverage
@echo "Testing of coverage in the sources finished, look at the " \
"results in $(BUILDDIR)/coverage/python.txt."
xml:
$(SPHINXBUILD) -b xml $(ALLSPHINXOPTS) $(BUILDDIR)/xml
@echo
@echo "Build finished. The XML files are in $(BUILDDIR)/xml."
pseudoxml:
$(SPHINXBUILD) -b pseudoxml $(ALLSPHINXOPTS) $(BUILDDIR)/pseudoxml
@echo
@echo "Build finished. The pseudo-XML files are in $(BUILDDIR)/pseudoxml."
<h3>Index</h3>
<hr />
<ul>
<li class="toctree-l1"><a href="/news/index.html">News & dates</a></li>
<li class="toctree-l1"><a href="/releases/index.html">Releases & Downloads</a></li>
<li class="toctree-l1"><a href="https://www.varnish-cache.org/lists/mailman/listinfo">Mailing Lists</a></li>
<li class="toctree-l1"><a href="/security/index.html">Security & Advisories</a></li>
<li class="toctree-l1"><a href="/docs/index.html">Documentation</a></li>
<li class="toctree-l2"><a href="/docs/trunk">- trunk(5.0) </a></li>
<li class="toctree-l2"><a href="/docs/4.1">- 4.1.x</a></li>
<li class="toctree-l2"><a href="/docs/4.0">- 4.0.x</a></li>
<li class="toctree-l1"><a href="https://github.com/varnishcache/varnish-cache">Source/Bugs/Patches</a></li>
<li class="toctree-l1"><a href="/business/index.html">Varnish Business</a></li>
<hr />
<li class="toctree-l1"><a href="/trac/wiki">Old Trac Wiki</a></li>
</ul>
<h3>Brought to you by:</h3>
<hr />
<a href="https://www.rootbsd.net"><img src="/_static/RootBSD.png"></a>
<a href="https://www.freebsd.org"><img src="/_static/FreeBSD.gif"></a>
Varnish HTTP Cache Business
===========================
Companies which can help you with Varnish.
* `Varnish Software <https://www.varnish-software.com/>`_
Global Training, Support, Varnish extensions and rather good beer.
* `Fastly <https://www.fastly.com/>`_
Global Varnish based CDN.
* `UPLEX <http://uplex.de/>`_
Germany, Consulting.
(Send email to phk@ if you want your company listed here)
.. toctree::
:hidden:
# -*- coding: utf-8 -*-
#
# Varnish Cache documentation build configuration file, created by
# sphinx-quickstart on Mon Apr 11 08:19:53 2016.
#
# This file is execfile()d with the current directory set to its
# containing dir.
#
# Note that not all possible configuration values are present in this
# autogenerated file.
#
# All configuration values have a default; values that are commented out
# serve to show the default.
import sys
import os
import shlex
# If extensions (or modules to document with autodoc) are in another directory,
# add these directories to sys.path here. If the directory is relative to the
# documentation root, use os.path.abspath to make it absolute, like shown here.
#sys.path.insert(0, os.path.abspath('.'))
# -- General configuration ------------------------------------------------
# If your documentation needs a minimal Sphinx version, state it here.
#needs_sphinx = '1.0'
# Add any Sphinx extension module names here, as strings. They can be
# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
# ones.
extensions = []
# Add any paths that contain templates here, relative to this directory.
templates_path = ['_templates']
# The suffix(es) of source filenames.
# You can specify multiple suffix as a list of string:
# source_suffix = ['.rst', '.md']
source_suffix = '.rst'
# The encoding of source files.
#source_encoding = 'utf-8-sig'
# The master toctree document.
master_doc = 'index'
# General information about the project.
project = u'Varnish Cache Project'
copyright = u'2016, Poul-Henning Kamp'
author = u'Poul-Henning Kamp'
# The version info for the project you're documenting, acts as replacement for
# |version| and |release|, also used in various other places throughout the
# built documents.
#
# The short X.Y version.
version = '5.0'
# The full version, including alpha/beta/rc tags.
release = '5.0'
# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.
#
# This is also used if you do content translation via gettext catalogs.
# Usually you set "language" from the command line for these cases.
language = None
# There are two options for replacing |today|: either, you set today to some
# non-false value, then it is used:
#today = ''
# Else, today_fmt is used as the format for a strftime call.
#today_fmt = '%B %d, %Y'
# List of patterns, relative to source directory, that match files and
# directories to ignore when looking for source files.
exclude_patterns = []
# The reST default role (used for this markup: `text`) to use for all
# documents.
#default_role = None
# If true, '()' will be appended to :func: etc. cross-reference text.
#add_function_parentheses = True
# If true, the current module name will be prepended to all description
# unit titles (such as .. function::).
#add_module_names = True
# If true, sectionauthor and moduleauthor directives will be shown in the
# output. They are ignored by default.
#show_authors = False
# The name of the Pygments (syntax highlighting) style to use.
pygments_style = 'sphinx'
# A list of ignored prefixes for module index sorting.
#modindex_common_prefix = []
# If true, keep warnings as "system message" paragraphs in the built documents.
#keep_warnings = False
# If true, `todo` and `todoList` produce output, else they produce nothing.
todo_include_todos = False
# -- Options for HTML output ----------------------------------------------
import alabaster
# The theme to use for HTML and HTML Help pages. See the documentation for
# a list of builtin themes.
html_theme = 'alabaster'
# Theme options are theme-specific and customize the look and feel of a theme
# further. For a list of options available for each theme, see the
# documentation.
html_theme_options = { }
# Add any paths that contain custom themes here, relative to this directory.
html_theme_path = []
# The name for this set of Sphinx documents. If None, it defaults to
# "<project> v<release> documentation".
html_title = u'Varnish HTTP Cache'
# A shorter title for the navigation bar. Default is the same as html_title.
#html_short_title = None
# The name of an image file (relative to this directory) to place at the top
# of the sidebar.
html_logo = "_static/varnish-bunny.png"
# The name of an image file (within the static path) to use as favicon of the
# docs. This file should be a Windows icon file (.ico) being 16x16 or 32x32
# pixels large.
#html_favicon = None
# Add any paths that contain custom static files (such as style sheets) here,
# relative to this directory. They are copied after the builtin static files,
# so a file named "default.css" will overwrite the builtin "default.css".
html_static_path = ['_static']
# Add any extra paths that contain custom files (such as robots.txt or
# .htaccess) here, relative to this directory. These files are copied
# directly to the root of the documentation.
#html_extra_path = []
# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
# using the given strftime format.
#html_last_updated_fmt = '%b %d, %Y'
# If true, SmartyPants will be used to convert quotes and dashes to
# typographically correct entities.
#html_use_smartypants = True
# Custom sidebar templates, maps document names to template names.
html_sidebars = {
'**': [
'phkbar.html',
],
}
# Additional templates that should be rendered to pages, maps page names to
# template names.
#html_additional_pages = {}
# If false, no module index is generated.
#html_domain_indices = True
# If false, no index is generated.
#html_use_index = True
# If true, the index is split into individual pages for each letter.
#html_split_index = False
# If true, links to the reST sources are added to the pages.
html_show_sourcelink = False
# If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
#html_show_sphinx = True
# If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
#html_show_copyright = True
# If true, an OpenSearch description file will be output, and all pages will
# contain a <link> tag referring to it. The value of this option must be the
# base URL from which the finished HTML is served.
#html_use_opensearch = ''
# This is the file name suffix for HTML files (e.g. ".xhtml").
#html_file_suffix = None
# Language to be used for generating the HTML full-text search index.
# Sphinx supports the following languages:
# 'da', 'de', 'en', 'es', 'fi', 'fr', 'hu', 'it', 'ja'
# 'nl', 'no', 'pt', 'ro', 'ru', 'sv', 'tr'
#html_search_language = 'en'
# A dictionary with options for the search language support, empty by default.
# Now only 'ja' uses this config value
#html_search_options = {'type': 'default'}
# The name of a javascript file (relative to the configuration directory) that
# implements a search results scorer. If empty, the default will be used.
#html_search_scorer = 'scorer.js'
# Output file base name for HTML help builder.
htmlhelp_basename = 'VarnishCachedoc'
# -- Options for LaTeX output ---------------------------------------------
latex_elements = {
# The paper size ('letterpaper' or 'a4paper').
#'papersize': 'letterpaper',
# The font size ('10pt', '11pt' or '12pt').
#'pointsize': '10pt',
# Additional stuff for the LaTeX preamble.
#'preamble': '',
# Latex figure (float) alignment
#'figure_align': 'htbp',
}
# Grouping the document tree into LaTeX files. List of tuples
# (source start file, target name, title,
# author, documentclass [howto, manual, or own class]).
latex_documents = [
(master_doc, 'VarnishCache.tex', u'Varnish Cache Documentation',
u'Poul-Henning Kamp', 'manual'),
]
# The name of an image file (relative to this directory) to place at the top of
# the title page.
#latex_logo = None
# For "manual" documents, if this is true, then toplevel headings are parts,
# not chapters.
#latex_use_parts = False
# If true, show page references after internal links.
#latex_show_pagerefs = False
# If true, show URL addresses after external links.
#latex_show_urls = False
# Documents to append as an appendix to all manuals.
#latex_appendices = []
# If false, no module index is generated.
#latex_domain_indices = True
# -- Options for manual page output ---------------------------------------
# One entry per manual page. List of tuples
# (source start file, name, description, authors, manual section).
man_pages = [
(master_doc, 'varnishcache', u'Varnish Cache Documentation',
[author], 1)
]
# If true, show URL addresses after external links.
#man_show_urls = False
# -- Options for Texinfo output -------------------------------------------
# Grouping the document tree into Texinfo files. List of tuples
# (source start file, target name, title, author,
# dir menu entry, description, category)
texinfo_documents = [
(master_doc, 'VarnishCache', u'Varnish Cache Documentation',
author, 'VarnishCache', 'One line description of project.',
'Miscellaneous'),
]
# Documents to append as an appendix to all manuals.
#texinfo_appendices = []
# If false, no module index is generated.
#texinfo_domain_indices = True
# How to display URL addresses: 'footnote', 'no', or 'inline'.
#texinfo_show_urls = 'footnote'
# If true, do not generate a @detailmenu in the "Top" node's menu.
#texinfo_no_detailmenu = False
.. _faq_comm:
Communication with the project
==============================
Report a bug
~~~~~~~~~~~~
Open an issue on github.
Send a patch/fix
~~~~~~~~~~~~~~~~
Do a github pull-request
.. _faq_find:
Finding things
--------------
Install on FreeBSD
~~~~~~~~~~~~~~~~~~
This should work::
pkg install varnish
or::
cd /usr/ports/www/varnish
make all install clean
Where is the bug I opened in 2012?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
We saved a snapshot of the old tickets from 'Trac',
if you remember the number,
`click here <http://r.varnish-cache.org/trac/ticket/1234>`_
and fix up the URL with the ticket number.
We have also created place-holder tickets on Github, so
you can find it by browsing
`closed issues. <https://github.com/varnishcache/varnish-cache/issues?q=is%3Aissue+is%3Aclosed>`_
.. _faq:
Questions and Answers
=====================
.. toctree::
comm
find
what
who
.. _faq_what:
What does ... mean / What is a ... ?
------------------------------------
V(E)TLA
~~~~~~~
Varnish (Extended) Three Letter Acronym.
Because we ended up naming so many things 'Vsomething', VCL, VMOD and so
one, somebody eventually started talking about all our 'VTLA' and somebody
else pointed out that would have to be VETLA because it is four letters.
VCL
~~~
A VCL (program) is how you tell Varnish what it should do with your
traffic. The VCL program is compiled into C source code, which
again is compiled into a shared library for maximum performance.
.. _faq_who:
Who is ... ?
------------
Anders Berg
~~~~~~~~~~~
Blame Anders! He is the one who got the crazy idea that the world
needed another HTTP proxy server software, and convinced his employer,
the norvegian newspaper `Verdens Gang <http://www.vg.no>`_ to pay for the
first version to be developed.
Here is an interview with Anders about `how it all began
<http://info.varnish-software.com/blog/celebrating-10-years-of-varnish-cache-qa-with-the-man-behind-the-idea>`_
Poul-Henning Kamp
~~~~~~~~~~~~~~~~~
PHK, as he's usually known, has written most of the code and come up with
most of the crazy ideas in Varnish, and yet he still has trouble
remembering what 'REST', 'CORS' and 'ALPN' means, and he flunked
'CSS for dummies' because he was never a webmaster or webdeveloper.
He does have 30+ years of experience in systems programming, and
that seems useful too.
PHK's `random outbursts </docs/trunk/phk/index.html>`_ has their own
section in the varnish documentation.
Varnish HTTP Cache
==================
:ref:`I'm new here, please explain this Varnish thing <intro>`
:ref:`Questions and Answers<faq>`
Whats happening
---------------
2016-04-11 Sorry if it looks a bit sparse around here, we're in the process
of moving the Varnish Cache project to its own infrastructure. /phk
2016-04-21 (Copenhagen) `Varnish-Software Summit
<http://info.varnish-software.com/copenhagen-summit-2016>`_
2016-04-21 (Paris)
`User meeting Varnish + eZ Publish <http://www.eventbrite.co.uk/e/inscription-user-meeting-varnish-ez-22169494555>`_
2016-05-05 (San Francisco)
`Cinco de Mayo / High Scale Varnish Meetup <http://www.meetup.com/San-Francisco-Varnish-Meetup/events/230233385/>`_
2016-05-11 (Sydney) `Varnish-Software Summit
<http://info.varnish-software.com/sydney-summit-2016>`_
2016-05-13 (Auckland) `Varnish-Software Summit
<http://info.varnish-software.com/nz-summit-2016>`_
.. toctree::
:hidden:
intro/index
security/index
news/index
business/index
faq/index
releases/index
.. _intro:
Introduction to Varnish
=======================
.. toctree::
:hidden:
.. _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
News & Dates
============
* :ref:`2016-04-11 New Website <20160411_website>`
Next major release
-------------------
* 2016-09-xx Varnish 5.0
.. toctree::
:hidden:
20160411_website.rst
Releases & Downloads
====================
Currently supported releases
----------------------------
* :ref:`rel4.1.2`
* :ref:`rel4.0.3`
`Changelog for all releases <https://github.com/varnishcache/varnish-cache/blob/master/doc/changes.rst>`_
By Operating System
-------------------
* :ref:`install_freebsd`
* :ref:`install_ubuntu`
* :ref:`install_debian`
* :ref:`install_redhat`
Current and older releases
--------------------------
=================== ============ =========== ===========
Release Release Date Status Download
=================== ============ =========== ===========
:ref:`rel4.1.2` 2016-03-07 Supported `varnish-4.1.2.tar.gz`_
:ref:`rel4.0.3` 2015-02-19 Supported `varnish-4.0.3.tar.gz`_
Varnish Cache 4.0.2 2014-10-08 End Of Life `varnish-4.0.2.tar.gz`_
Varnish Cache 4.0.1 2014-06-24 End Of Life `varnish-4.0.1.tar.gz`_
Varnish Cache 4.0.0 2014-04-10 End Of Life `varnish-4.0.0.tar.gz`_
Varnish Cache 3.0.7 2015-03-23 End Of Life `varnish-3.0.7.tar.gz`_
Varnish Cache 3.0.6 2014-10-17 End Of Life `varnish-3.0.6.tar.gz`_
Varnish Cache 3.0.5 2013-12-02 End Of Life `varnish-3.0.5.tar.gz`_
Varnish Cache 3.0.4 2013-06-17 End Of Life `varnish-3.0.4.tar.gz`_
=================== ============ =========== ===========
.. _varnish-4.1.2.tar.gz: https://repo.varnish-cache.org/source/varnish-4.1.2.tar.gz
.. _varnish-4.0.3.tar.gz: https://repo.varnish-cache.org/source/varnish-4.0.3.tar.gz
.. _varnish-4.0.2.tar.gz: https://repo.varnish-cache.org/source/varnish-4.0.2.tar.gz
.. _varnish-4.0.1.tar.gz: https://repo.varnish-cache.org/source/varnish-4.0.1.tar.gz
.. _varnish-4.0.0.tar.gz: https://repo.varnish-cache.org/source/varnish-4.0.0.tar.gz
.. _varnish-3.0.7.tar.gz: https://repo.varnish-cache.org/source/varnish-3.0.7.tar.gz
.. _varnish-3.0.6.tar.gz: https://repo.varnish-cache.org/source/varnish-3.0.6.tar.gz
.. _varnish-3.0.5.tar.gz: https://repo.varnish-cache.org/source/varnish-3.0.5.tar.gz
.. _varnish-3.0.4.tar.gz: https://repo.varnish-cache.org/source/varnish-3.0.4.tar.gz
.. toctree::
:hidden:
rel4.1.2
rel4.0.3
install_freebsd
install_ubuntu
install_debian
install_redhat
.. _install_debian:
Installation on Debian
======================
Varnish is distributed in the Debian package repositories but the
version there might be out of date and we generally recommend using
the packages provided by varnish-cache.org or packages from
backports.debian.org.
To use the varnish-cache.org repository and install Varnish under
Debian 8 ("jessie") do the following as root::
apt-get install apt-transport-https
curl https://repo.varnish-cache.org/GPG-key.txt | apt-key add -
echo "deb https://repo.varnish-cache.org/debian/ jessie varnish-4.1"\
>> /etc/apt/sources.list.d/varnish-cache.list
apt-get update
apt-get install varnish
Packages are built for wheezy and jessie on amd64. Varnish 4.0
packages are available in the "varnish-4.0" component.
Ubuntu LTS users please follow :ref:`these instructions <install_ubuntu>`.
.. _install_freebsd:
Installation on FreeBSD
=======================
Varnish is distributed in the FreeBSD ports collection as 'www/varnish'.
You can either install it as binary package::
pkg install varnish
Or build it from source::
cd /usr/ports/www/varnish
make all install clean
.. _install_redhat:
Installation on RedHat
======================
Installing Varnish Cache is as simple as enabling our package
repository and installing the packages. Varnish Cache 4.0 and 4.1
are supported on EL6 and EL7.
Varnish 4.1
-----------
If you are on a compatible Linux distribution, use::
yum install epel-release
rpm --nosignature -i https://repo.varnish-cache.org/redhat/varnish-4.1.el7.rpm
(or: rpm --nosignature -i https://repo.varnish-cache.org/redhat/varnish-4.1.el6.rpm for RHEL6)
yum install varnish
Varnish 4.0
-----------
If you are on RHEL 6 or a compatible distribution, use::
yum install epel-release
rpm --nosignature -i https://repo.varnish-cache.org/redhat/varnish-4.0.el6.rpm
yum install varnish
For RHEL 7 and compatible distributions, use::
yum install epel-release
rpm --nosignature -i https://repo.varnish-cache.org/redhat/varnish-4.0.el7.rpm
yum install varnish
The --no-signature is only needed on initial installation, since
the Varnish GPG key is not yet in the yum keyring.
Varnish Cache is also distributed in the EPEL (Extra Packages for
Enterprise Linux) package repositories. However, while EPEL allows
new versions to be distributed, it does not allow for
backwards-incompatible changes. Therefore, new major versions will
not hit EPEL and it is not necessarily up to date.
.. _install_ubuntu:
Installation on Ubuntu
======================
Varnish is distributed in the Ubuntu package repositories, but the
version there might be out of date, and we generally recommend using
the packages provided by varnish-cache.org.
Please be advised that we only provide packages for Ubuntu's LTS
releases, not all the intermediate releases. These packages might
still work fine on newer releases. The supported architecture is
amd64.
To use the varnish-cache.org repository and install Varnish under
Ubuntu 14.04 (Trusty Tahr) do the following as root::
apt-get install apt-transport-https
curl https://repo.varnish-cache.org/GPG-key.txt | apt-key add -
echo "deb https://repo.varnish-cache.org/ubuntu/ trusty varnish-4.1" \
>> /etc/apt/sources.list.d/varnish-cache.list
apt-get update
apt-get install varnish
Packages for Varnish 4.0 is available in the "varnish-4.0" component.
Currently packages are being built for precise and trusty on amd64.
Debian users please follow :ref:`these instructions <install_debian>`.
.. _rel4.0.3:
Varnish Cache 4.0.3
===================
* 2015-02-19 /scn
`Source download <varnish-4.0.3.tar.gz>`_
`Change log <https://github.com/varnishcache/varnish-cache/blob/4.0/doc/changes.rst>`_
Summary of changes
------------------
* 26 reported bugs fixed.
* Replaced objects are now expired immediately,
instead of kept around until expiry.
* Memory usage on chunked backend responses is lower.
.. _rel4.1.2:
Varnish Cache 4.1.2
===================
* 2016-03-07 /scn
`Source download <varnish-4.1.2.tar.gz>`_
`Change log <https://github.com/varnishcache/varnish-cache/blob/4.1/doc/changes.rst>`_
This release adresses a performance regression as well as fixing multiple
bugs seen since 4.1.1.
It is recommended for all users to upgrade.
Debian/Ubuntu and Enterprise Linux packages will be available on
repo.varnish-cache.org shortly.
This diff is collapsed.
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