1
1
Fork 0
mirror of https://github.com/roles-ansible/ansible_role_gitea.git synced 2024-08-16 11:39:50 +02:00
ansible_role_gitea/templates
L3D 9c536d77a9 Simplify configuration file
I kicked out some config values, that are not controlled via ansible variables.
Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)*

I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine.

I assume that the official gitea chenged and updated some options.
Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/).

@thomas-maurice: What did you think about it?
Better track every value and update it in our config.

Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-06-02 23:04:10 +02:00
..
fail2ban more fail2ban config options 2019-03-15 17:05:09 +00:00
gitea.ini.j2 Simplify configuration file 2019-06-02 23:04:10 +02:00
gitea.service.j2 First commit 2017-01-10 22:09:34 +01:00