..  include:: /Includes.rst.txt

..  _installation:

============
Installation
============

Target group: **Administrators**

..  _requirements:

Requirements
============

*   TYPO3 13.4 LTS or 14
*   PHP 8.2, 8.3 or 8.4
*   An administrator account — the module is not available to editors

Two extensions are suggested, not required:

..  rst-class:: dl-parameters

:composer:`typo3/cms-seo`
    Provides the XML sitemap the indexing checks look for. Without it, the
    sitemap checks report as not verifiable.

:composer:`typo3/cms-scheduler`
    Without it, the scheduler check is skipped instead of reporting a missing
    setup.

..  _installation-composer:

Installation with Composer
==========================

..  code-block:: bash

    composer require webagentur-yahya/golive-check

..  _installation-classic:

Installation without Composer
=============================

Install the extension from the
`TYPO3 Extension Repository <https://extensions.typo3.org/extension/golive_check>`__
in the :guilabel:`Admin Tools > Extensions` module, or download it there and
upload the archive.

..  _installation-verify:

After installing
================

Open :guilabel:`Site Management > Go-Live Check`. The report is built when the
page loads; on a site with a reachable live URL this takes a few seconds
because a dozen checks send real HTTP requests.

Nothing else has to be configured. The extension writes nothing to the database
schema — the ticks of the manual checklist live in :sql:`sys_registry` under the
namespace ``golive_check``.

..  _installation-loopback:

If every live check reports "not verifiable"
============================================

The live checks are sent from the web server to the site's own base URL. That
request has to work *from the server*, which is not the same as working from
your browser:

*   In a local development environment (DDEV, Docker) the container often
    cannot resolve the production domain, and there is nothing to reach anyway.
    This is expected — the report is meant for the live installation.
*   A firewall or a load balancer may block a request that leaves and
    immediately comes back (hairpin NAT).
*   If the site's ``base`` has no host at all, the report falls back to the host
    of the current backend request and marks every comparison against a domain
    as not verifiable, because the answer would be a statement about the
    backend URL rather than about the site.

Each skipped check names its reason, so the report says which of these applies.