Skip to content

Commit 75e32a0

Browse files
committed
docs: remove about Vagrant
1 parent d90c803 commit 75e32a0

File tree

1 file changed

+0
-34
lines changed

1 file changed

+0
-34
lines changed

user_guide_src/source/installation/running.rst

Lines changed: 0 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -260,40 +260,6 @@ Setting Environment
260260

261261
See :ref:`Handling Multiple Environments <environment-nginx>`.
262262

263-
Hosting with Vagrant
264-
====================
265-
266-
Virtualization is an effective way to test your webapp in the environment you
267-
plan to deploy on, even if you develop on a different one.
268-
Even if you are using the same platform for both, virtualization provides an
269-
isolated environment for testing.
270-
271-
The codebase comes with a ``VagrantFile.dist``, that can be copied to ``VagrantFile``
272-
and tailored for your system, for instance enabling access to specific database or caching engines.
273-
274-
Setting Up
275-
----------
276-
277-
It assumes that you have installed `VirtualBox <https://www.virtualbox.org/wiki/Downloads>`_ and
278-
`Vagrant <https://www.vagrantup.com/downloads.html>`_
279-
for your platform.
280-
281-
The Vagrant configuration file assumes you have set up a `ubuntu/bionic64 Vagrant box
282-
<https://app.vagrantup.com/ubuntu/boxes/bionic64>`_ on your system::
283-
284-
vagrant box add ubuntu/bionic64
285-
286-
Testing
287-
-------
288-
289-
Once set up, you can then launch your webapp inside a VM, with the command::
290-
291-
vagrant up
292-
293-
Your webapp will be accessible at ``http://localhost:8080``, with the code coverage
294-
report for your build at ``http://localhost:8081`` and the user guide for
295-
it at ``http://localhost:8082``.
296-
297263
Bootstrapping the App
298264
=====================
299265

0 commit comments

Comments
 (0)