*`gitea_dl_url`: The URL, the compiled gitea-binary will be downloaded from
*`gitea_systemd_cap_net_bind_service`: Adds `AmbientCapabilities=CAP_NET_BIND_SERVICE` to systemd service file
*`gitea_extra_config`: Additional configuration
### Look and feel
*`gitea_app_name`: Displayed application name
*`gitea_show_user_email`: Do you want to display email addresses ? (true/false)
*`gitea_disable_gravatar`: Do you want to disable Gravatar ? (privacy and so on) (true/false)
*`gitea_offline_mode`: Same but for disabling CDNs for frontend assets (true/false)
*`gitea_disable_registration`: Do you want to disable user registration ? (true/false)
*`gitea_only_allow_external_registration`: Do you want to force registration only using third-party services ? (true/false)
*`gitea_show_registration_button`: Do you want to show the registration button? (true/false)
*`gitea_require_signin`: Do you require a signin to see repo's (even public ones) ? (true/false)
*`gitea_enable_captcha`: Do you want to enable captcha's ? (true/false)
*`gitea_themes`: List of enabled themes
*`gitea_theme_default`: Default theme
### Security
*`gitea_secret_key`: Cookie secret key
*`gitea_internal_token`: Internal API token
*`gitea_disable_git_hooks`: Do you want to disable the interface to add git hooks? If enabled it could be a security bug as it can be used for RCE. Defaults to true (true/false)
### Limits
*`gitea_user_repo_limit`: Limit how many repos a user can have (-1 for unlimited)
### HTTP configuration
*`gitea_http_domain`: HTTP domain (displayed in your clone URLs, just the domain like git.foo.fr)
*`gitea_root_url`: Root URL used to access your web app (full URL)
If enabled, this will deploy a fail2ban filter and jail config for Gitea as described in the [Gitea Documentation](https://docs.gitea.io/en-us/fail2ban-setup/).
As this will only deploy config files, fail2ban already has to be installed or otherwise the role will fail.
*`gitea_fail2ban_enabled`: Whether to deploy the fail2ban config or not
I'm happy to fix any issue that's been opened, or even better, review your pull requests :)
## Testing
Testing uses [molecule](https://molecule.readthedocs.io/en/stable-1.22/usage.html). To start the
tests, install the dependencies first. I would recommend you use [a virtual env](https://virtualenv.pypa.io/en/latest/) for that but who am I to tell you what to do.
```
pip install pew # install pew to manage the venvs
pew new ansible # create the venv
pip install -r requirements-travis.txt # install the requirements
molecule test # Run the actual tests
```
Note: you need Docker installed
### Known testing limitations
Currently it's mainly validating that the playbook runs, the lint is ok, and that kind of things.
Since it runs in Docker, we currently have no way to check if the service is actually launched by systemd
and so on. This has to be worked on.
## License
```
Copyright 2019-present Thomas Maurice
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
