ansible-gitea

Synopsis

- hosts: all
  vars:
    gitea_database_name: gitea
    gitea_database_user: gitea
    gitea_database_password: "{{ vault_crypted_gitea_database_pass }}"
    gitea_salt: "{{ vault_crypted_gitea_salt }}"
    gitea_domain: git.example.com
    gitea_database_uri: mysql.example.com:3306
  roles:
    - ketudb.gitea

Description

Simple role to install the Gogs git server.

Requirements

• silpion.lib

Role Variables

• gitea_domain: The baseurl for linkgeneration mandatory
• gitea_database_password: Database password for gitea mandatory
• gitea_salt: The salt to use for password storage mandatory
• gitea_database_uri: Uri to use for database connection (default: localhost:3306)
• gitea_database_name: Name of the database gitea shall use (default: gitea)
• gitea_database_user: Name of the database usre gitea shall use (default: gitea)
• gitea_database_type: Type of gitea database (default: mysql)
• gitea_http_port: Http port gitea shall bind to (default: 3000)
• gitea_ssh_port: SSH port gitea shall bind to (default: 2222)
• gitea_http_proto: Whether to prepend http or https to generated links (default: http)
• gitea_logdir: The directory to write logs into (default: /var/run/gitea)
• gitea_appini_template: Template to use for gitea app.ini config file (default: builtin_app.ini.j2)
• gitea_home: Folder in which to put gitea data (default: /srv/gitea)
• gitea_username: Username under which to run gitea. Must be root if you want gitea to bind to ports < 1024 (default: gitea)
• gitea_install_dir: Folder to install gitea into (default: /opt/gitea)
• gitea_config_dir: Folder in which to put gitea config (default: /etc/gitea)
• gitea_version: The version of gitea to install (default: 1.12.3)
• gitea_http_listen_addr: The address to listen on for http request (default: ‘')

Contributing

Please fork this repository and create a local branch split off of the master branch and create pull requests back to the origin master branch.

License

AGPLv3

Integration testing

This role provides integration tests using the Ruby RSpec/serverspec framework with a few drawbacks at the time of writing this documentation.

Running integration tests requires a number of dependencies being installed. As this role uses Ruby RSpec there is the need to have Ruby with rake and bundler available.

# install role specific dependencies with bundler
bundle install

# run the complete test suite with Docker
rake suite

# run the complete test suite with Vagrant
source  envvars-vagrant.sample
rake suite

# run the complete test suite with Vagrant without destroying the box afterwards
source  envvars-vagrant.sample
RAKE_ANSIBLE_VAGRANT_DONT_CLEANUP=1 rake suite

Author information

• Alvaro Aleman