Skip to content

Commit

Permalink
Merge pull request #6314 from kenjis/remove-Vagrantfile
Browse files Browse the repository at this point in the history
chore: Remove Vagrant
  • Loading branch information
kenjis authored Jul 30, 2022
2 parents 6f4b407 + 75e32a0 commit 4b7306f
Show file tree
Hide file tree
Showing 4 changed files with 1 addition and 238 deletions.
1 change: 0 additions & 1 deletion .gitattributes
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,6 @@ contributing/ export-ignore
.nojekyll export-ignore export-ignore
CODE_OF_CONDUCT.md export-ignore
CONTRIBUTING.md export-ignore
Vagrantfile.dist export-ignore

# They don't want our test files
tests/AutoReview/ export-ignore
Expand Down
203 changes: 0 additions & 203 deletions Vagrantfile.dist

This file was deleted.

1 change: 1 addition & 0 deletions user_guide_src/source/changelogs/v4.2.2.rst
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@ Changes
- Fixed: Validation of fields with a leading asterisk (wildcard).
- Now ``CLIRequest::isCLI()`` always returns true.
- Now ``IncommingRequest::isCLI()`` always returns false.
- **Vagrantfile.dist** has been moved to `CodeIgniter DevKit <https://github.com/codeigniter4/devkit>`_.

Deprecations
************
Expand Down
34 changes: 0 additions & 34 deletions user_guide_src/source/installation/running.rst
Original file line number Diff line number Diff line change
Expand Up @@ -260,40 +260,6 @@ Setting Environment

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

Hosting with Vagrant
====================

Virtualization is an effective way to test your webapp in the environment you
plan to deploy on, even if you develop on a different one.
Even if you are using the same platform for both, virtualization provides an
isolated environment for testing.

The codebase comes with a ``VagrantFile.dist``, that can be copied to ``VagrantFile``
and tailored for your system, for instance enabling access to specific database or caching engines.

Setting Up
----------

It assumes that you have installed `VirtualBox <https://www.virtualbox.org/wiki/Downloads>`_ and
`Vagrant <https://www.vagrantup.com/downloads.html>`_
for your platform.

The Vagrant configuration file assumes you have set up a `ubuntu/bionic64 Vagrant box
<https://app.vagrantup.com/ubuntu/boxes/bionic64>`_ on your system::

vagrant box add ubuntu/bionic64

Testing
-------

Once set up, you can then launch your webapp inside a VM, with the command::

vagrant up

Your webapp will be accessible at ``http://localhost:8080``, with the code coverage
report for your build at ``http://localhost:8081`` and the user guide for
it at ``http://localhost:8082``.

Bootstrapping the App
=====================

Expand Down

0 comments on commit 4b7306f

Please sign in to comment.