external/iiab
1
0
Fork 0
mirror of https://github.com/iiab/iiab.git synced 2025-03-09 15:40:17 +00:00
Code Issues Releases Wiki Activity

Merge pull request #1573 from aidan-fitz/gitea-docs

Browse source 
Expand Gitea documentation
This commit is contained in:
A Holt 2019-04-01 21:50:00 -07:00 • committed by GitHub
commit 9e680781a3
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 32 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

39
roles/gitea/README.rst
View file

@ -1,6 +1,6 @@
============= ============
Gitea README Gitea README
============= ============
This Ansible role installs Gitea - a self-hosted Git service written in Go. This Ansible role installs Gitea - a self-hosted Git service written in Go.
@ -9,16 +9,41 @@ Using It
Gitea should be accessible at: http://box/gitea Gitea should be accessible at: http://box/gitea
Gitea repositories can be cloned using either HTTP or SSH. When cloning with
HTTP, the clone URL will start with ``http://box.lan/gitea/``. SSH clone URLs
start with ``gitea@box.lan``.
Installation and Setup
----------------------
Simply run ``cd /opt/iiab/iiab`` then ``sudo ./runrole gitea`` to install
Gitea. After installing, Gitea will be live at http://box/gitea
The first time you access the Gitea web interface, the home page will appear.
Clicking on "Register" or "Sign In" in the upper right corner will take you to
the setup page. The recommended settings have been configured for you, but you
can change them if you want. For example, you may want to change the site title
to match the name of your organization.
After finishing the setup process, you will be directed to a page where you can
create a user account. The first account created after setting up Gitea will be
an admin account. You can also create an admin account from the setup page
under "Administrator Account Settings."
Configuration Configuration
------------- -------------
Gitea has been configured to work with MySQL; it can also be used with SQLite or Gitea has been configured to work with SQLite; it can also be used with MySQL or
PostgreSQL. If you want to use it with a different database, change the PostgreSQL. If you want to use it with a different database, change the
``DB_TYPE`` property in ``/etc/gitea/app.ini`` [1] and change the line ``After=mysqld.service`` ``DB_TYPE`` property in ``/etc/gitea/app.ini`` [1] and add one of the following
in ``/etc/systemd/system/gitea.service`` [2] to one of the following: lines to the ``[Unit]`` section of ``/etc/systemd/system/gitea.service`` [2]:
* SQLite: comment it out. * MySQL: ``After=mysqld.service``
* Postgres: ``After=postgresql.service`` * PostgreSQL: ``After=postgresql.service``
For MySQL and PostgreSQL, you need to specify the server address, the database
name, and the user credentials that Gitea will use to access the database.
**Make sure the user exists on the database server first.**
[1] Prior to installing Gitea, instead edit: ``/opt/iiab/iiab/roles/gitea/templates/app.ini.j2`` [1] Prior to installing Gitea, instead edit: ``/opt/iiab/iiab/roles/gitea/templates/app.ini.j2``

1
roles/gitea/templates/gitea.service.j2
View file

@ -2,7 +2,6 @@
Description=Gitea (Git with a cup of tea) Description=Gitea (Git with a cup of tea)
After=syslog.target After=syslog.target
After=network.target After=network.target
After=mysqld.service
[Service] [Service]
# Modify these two values and uncomment them if you have # Modify these two values and uncomment them if you have