Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
V
varnish-cache
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
varnishcache
varnish-cache
Commits
ff94a678
Commit
ff94a678
authored
Aug 25, 2015
by
Francisco Velázquez
Committed by
Martin Blix Grydeland
Nov 16, 2015
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Separating next steps after installation in its own section
parent
050c69f6
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
4 deletions
+8
-4
install.rst
doc/sphinx/installation/install.rst
+8
-4
No files found.
doc/sphinx/installation/install.rst
View file @
ff94a678
...
@@ -143,11 +143,15 @@ And finally, the true test of a brave heart: ``sudo make install``
...
@@ -143,11 +143,15 @@ And finally, the true test of a brave heart: ``sudo make install``
Varnish will now be installed in ``/usr/local``. The ``varnishd`` binary is in
Varnish will now be installed in ``/usr/local``. The ``varnishd`` binary is in
`/usr/local/sbin/varnishd`. To make sure that the necessary links and caches
`/usr/local/sbin/varnishd`. To make sure that the necessary links and caches
to the most recent shared libraries are found, run ``sudo ldconfig``.
of the most recent shared libraries are found, run ``sudo ldconfig``.
Next steps
==========
After successful installation you are ready to proceed to the :ref:`tutorial-index`.
After successful installation you are ready to proceed to the :ref:`tutorial-index`.
This tutorial, however, is written for installations from binary packages.
In practice, it means that you cannot call ``service varnish start`` out of the box.
This tutorial is written for installations from binary packages.
Instead, you start the varnish daemon manually, for example::
In practice, it means that some configurations are not in place for installations from source code.
For example, instead of calling ``service varnish start``, you start the varnish daemon manually by typing::
varnishd -a :6081 -T localhost:6082 -b localhost:8080 -f /path/my_file.vcl
varnishd -a :6081 -T localhost:6082 -b localhost:8080 -f /path/my_file.vcl
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment