> For the complete documentation index, see [llms.txt](https://docs.svrunit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.svrunit.com/use-cases/verify-server-for-project.md).

# Verify Server for Project

SVRUnit can also be installed with Composer.\
This means you can **install it along with your project**, such as Symfony projects, Shopware projects and more.

Now imagine, that you create a SVRUnit test file that contains all **requirements of your project**. You can simply run the tests directly from your project and verify that your hosting environment can **run your project**!

Let's use the example of Shopware 6.

Shopware has a page with their requirements at: \
<https://docs.shopware.com/en/shopware-6-en/first-steps/system-requirements>

I've created a **template file for Shopware 6** that you can use as base for your project: \
<https://github.com/svrunit/svrunit/blob/main/templates/shopware/shopware6.yml>

Let's install SVRUnit as Dependency in your project (dev or prod, depends on you)

```bash
composer require svrunit/svrunit
```

Now create a **XML configuration** file that specifies a single YML test file.

```xml
<svrunit>  
  <testsuites>   
      
      <testsuite name="My Shopware 6 Project Tests">         
         <file>./shopware6.yml</file>      
      </testsuite>   
        
  </testsuites>
</svrunit>
```

Now let's place the content of our YML (or the template file from above) in the shopware6.yml file.

```yaml
php_ini:

  - name: "PHP Version is correct"
    setting: "PHP_VERSION"
    mode: "web"
    value_or:
      - "operator": ">="
        "value": "7.4"
        
    ......
    ......
```

That's it!

You can now **manually** run your tests, or even use your **CI/CD pipeline** for this.

<pre class="language-bash"><code class="lang-bash"><strong>php vendor/bin/svrunit --configuration=shopware6.xml  
</strong></code></pre>

&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.svrunit.com/use-cases/verify-server-for-project.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.