forkjo/docs/content/doc/installation/from-binary.en-us.md

date	title	slug	weight	toc	draft	menu
2017-06-19T12:00:00+02:00	Installation from binary	install-from-binary	10	true	false	sidebar parent name weight identifier installation From binary 20 install-from-binary

Installation from binary

All downloads come with SQLite, MySQL and PostgreSQL support, and are built with embedded assets. This can be different for older releases. Choose the file matching the destination platform from the downloads page, copy the URL and replace the URL within the commands below:

wget -O gitea https://dl.gitea.io/gitea/1.5.0/gitea-1.5.0-linux-amd64
chmod +x gitea

Verify GPG signature

Gitea signs all binaries with a GPG key to prevent against unwanted modification of binaries. To validate the binary download the signature file which ends in .asc for the binary you downloaded and use the gpg command line tool.

gpg --keyserver pgp.mit.edu --recv 0x2D9AE806EC1592E2
gpg --verify gitea-1.5.0-linux-amd64.asc gitea-1.5.0-linux-amd64

Test

After getting a binary, it can be tested with ./gitea web or moved to a permanent location. When launched manually, Gitea can be killed using Ctrl+C.

./gitea web

Recommended server configuration

Prepare environment

Check that git is installed on the server, if it is not install it first.

git --version

Create user to run gitea (ex. git)

adduser \
   --system \
   --shell /bin/bash \
   --gecos 'Git Version Control' \
   --group \
   --disabled-password \
   --home /home/git \
   git

Create required directory structure

mkdir -p /var/lib/gitea/{custom,data,indexers,public,log}
chown git:git /var/lib/gitea/{data,indexers,log}
chmod 750 /var/lib/gitea/{data,indexers,log}
mkdir /etc/gitea
chown root:git /etc/gitea
chmod 770 /etc/gitea

NOTE: /etc/gitea is temporary set with write rights for user git so that Web installer could write configuration file. After installation is done it is recommended to set rights to read-only using:

chmod 750 /etc/gitea
chmod 644 /etc/gitea/app.ini

Copy gitea binary to global location

cp gitea /usr/local/bin/gitea

Create service file to start gitea automatically

See how to create [Linux service]({{< relref "run-as-service-in-ubuntu.en-us.md" >}})

Updating to a new version

You can update to a new version of gitea by stopping gitea, replacing the binary at /usr/local/bin/gitea and restarting the instance. The binary file name should not be changed during the update to avoid problems in existing repositories.

It is recommended you do a [backup]({{< relref "doc/usage/backup-and-restore.en-us.md" >}}) before updating your installation.

If you have carried out the installation steps as described above, the binary should have the generic name gitea. Do not change this, i.e. to include the version number.

See below for troubleshooting instructions to repair broken repositories after an update of your gitea version.

Troubleshooting

Old glibc versions

Older Linux distributions (such as Debian 7 and CentOS 6) may not be able to load the Gitea binary, usually producing an error such as ./gitea: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC\_2.14' not found (required by ./gitea). This is due to the integrated SQLite support in the binaries provided by dl.gitea.io. In this situation, it is usually possible to [install from source]({{< relref "from-source.en-us.md" >}}) without sqlite support.

Running gitea on another port

For errors like 702 runWeb()] [E] Failed to start server: listen tcp 0.0.0.0:3000: bind: address already in use gitea needs to be started on another free port. This is possible using ./gitea web -p $PORT. It's possible another instance of gitea is already running.

Git error after updating to a new version of gitea

If the binary file name has been changed during the update to a new version of gitea, git hooks in existing repositories will not work any more. In that case, a git error will be displayed when pushing to the repository.

remote: ./hooks/pre-receive.d/gitea: line 2: [...]: No such file or directory

The [...] part of the error message will contain the path to your previous gitea binary.

To solve this, go to the admin options and run the task Resynchronize pre-receive, update and post-receive hooks of all repositories to update all hooks to contain the new binary path. Please note that this overwrite all git hooks including ones with customizations made.

If you aren't using the built-in to Gitea ssh server you will also need to re-write the authorized key file by running the Update the '.ssh/authorized_keys' file with Gitea SSH keys. task in the admin options.