2017-11-26 16:44:32 -05:00
|
|
|
|
---
|
|
|
|
|
date: "2016-12-01T16:00:00+02:00"
|
2023-05-25 00:32:39 -04:00
|
|
|
|
title: "使用源代码安装"
|
2017-11-26 16:44:32 -05:00
|
|
|
|
slug: "install-from-source"
|
2023-07-25 22:00:14 -04:00
|
|
|
|
sidebar_position: 30
|
2020-12-09 01:47:06 -05:00
|
|
|
|
toc: false
|
2017-11-26 16:44:32 -05:00
|
|
|
|
draft: false
|
Refactor docs (#23752)
This was intended to be a small followup for
https://github.com/go-gitea/gitea/pull/23712, but...here we are.
1. Our docs currently use `slug` as the entire URL, which makes
refactoring tricky (see https://github.com/go-gitea/gitea/pull/23712).
Instead, this PR attempts to make future refactoring easier by using
slugs as an extension of the section. (Hugo terminology)
- What the above boils down to is this PR attempts to use directory
organization as URL management. e.g. `usage/comparison.en-us.md` ->
`en-us/usage/comparison/`, `usage/packages/overview.en-us.md` ->
`en-us/usage/packages/overview/`
- Technically we could even remove `slug`, as Hugo defaults to using
filename, however at least with this PR it means `slug` only needs to be
the name for the **current file** rather than an entire URL
2. This PR adds appropriate aliases (redirects) for pages, so anything
on the internet that links to our docs should hopefully not break.
3. A minor nit I've had for a while, renaming `seek-help` to `support`.
It's a minor thing, but `seek-help` has a strange connotation to it.
4. The commits are split such that you can review the first which is the
"actual" change, and the second is added redirects so that the first
doesn't break links elsewhere.
---------
Signed-off-by: jolheiser <john.olheiser@gmail.com>
2023-04-27 23:33:41 -04:00
|
|
|
|
aliases:
|
|
|
|
|
- /zh-cn/install-from-source
|
2017-11-26 16:44:32 -05:00
|
|
|
|
menu:
|
|
|
|
|
sidebar:
|
|
|
|
|
parent: "installation"
|
2023-05-25 00:32:39 -04:00
|
|
|
|
name: "使用源代码安装"
|
2023-07-25 22:00:14 -04:00
|
|
|
|
sidebar_position: 30
|
2017-11-26 16:44:32 -05:00
|
|
|
|
identifier: "install-from-source"
|
|
|
|
|
---
|
|
|
|
|
|
2023-05-25 00:32:39 -04:00
|
|
|
|
# 使用源代码安装
|
2017-11-26 16:44:32 -05:00
|
|
|
|
|
2022-08-14 12:03:12 -04:00
|
|
|
|
首先你需要安装Golang,关于Golang的安装,参见[官方文档](https://golang.google.cn/doc/install)。
|
|
|
|
|
|
|
|
|
|
其次你需要[安装Node.js](https://nodejs.org/zh-cn/download/),Node.js 和 npm 将用于构建 Gitea 前端。
|
|
|
|
|
|
2017-11-26 16:44:32 -05:00
|
|
|
|
## 下载
|
|
|
|
|
|
2022-08-14 12:03:12 -04:00
|
|
|
|
你需要获取Gitea的源码,最方便的方式是使用 `git` 命令。执行以下命令:
|
2017-11-26 16:44:32 -05:00
|
|
|
|
|
|
|
|
|
```
|
2022-08-14 12:03:12 -04:00
|
|
|
|
git clone https://github.com/go-gitea/gitea
|
|
|
|
|
cd gitea
|
2017-11-26 16:44:32 -05:00
|
|
|
|
```
|
|
|
|
|
|
2022-08-14 12:03:12 -04:00
|
|
|
|
然后你可以选择编译和安装的版本,当前你有多个选择。如果你想编译 `main` 版本,你可以直接跳到 [编译](#编译) 部分,这是我们的开发分支,虽然也很稳定但不建议您在正式产品中使用。
|
2017-11-26 16:44:32 -05:00
|
|
|
|
|
|
|
|
|
如果你想编译最新稳定分支,你可以执行以下命令签出源码:
|
|
|
|
|
|
2022-08-14 12:03:12 -04:00
|
|
|
|
```bash
|
2017-11-26 16:44:32 -05:00
|
|
|
|
git branch -a
|
2023-07-25 22:00:14 -04:00
|
|
|
|
git checkout v@version@
|
2017-11-26 16:44:32 -05:00
|
|
|
|
```
|
|
|
|
|
|
2023-07-25 22:00:14 -04:00
|
|
|
|
最后,你也可以直接使用标签版本如 `v@version@`。你可以执行以下命令列出可用的版本并选择某个版本签出:
|
2017-11-26 16:44:32 -05:00
|
|
|
|
|
2022-08-14 12:03:12 -04:00
|
|
|
|
```bash
|
2017-11-26 16:44:32 -05:00
|
|
|
|
git tag -l
|
2023-07-25 22:00:14 -04:00
|
|
|
|
git checkout v@version@
|
2017-11-26 16:44:32 -05:00
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
## 编译
|
|
|
|
|
|
2019-12-05 12:18:28 -05:00
|
|
|
|
要从源代码进行编译,以下依赖程序必须事先安装好:
|
2017-11-26 16:44:32 -05:00
|
|
|
|
|
2023-07-25 22:00:14 -04:00
|
|
|
|
- `go` @minGoVersion@ 或以上版本, 详见[这里](https://golang.google.cn/doc/install)
|
|
|
|
|
- `node` @minNodeVersion@ 或以上版本,并且安装 `npm`, 详见[这里](https://nodejs.org/zh-cn/download/)
|
2022-11-06 20:48:46 -05:00
|
|
|
|
- `make`, 详见[这里](/zh-cn/hacking-on-gitea/)
|
2017-11-26 16:44:32 -05:00
|
|
|
|
|
2022-08-14 12:03:12 -04:00
|
|
|
|
各种可用的 [make 任务](https://github.com/go-gitea/gitea/blob/main/Makefile)
|
2019-12-05 12:18:28 -05:00
|
|
|
|
可以用来使编译过程更方便。
|
2017-11-26 16:44:32 -05:00
|
|
|
|
|
2019-12-05 12:18:28 -05:00
|
|
|
|
按照您的编译需求,以下 tags 可以使用:
|
2017-11-26 16:44:32 -05:00
|
|
|
|
|
2022-07-27 21:22:47 -04:00
|
|
|
|
- `bindata`: 这个编译选项将会把运行Gitea所需的所有外部资源都打包到可执行文件中,这样部署将非常简单因为除了可执行程序将不再需要任何其他文件。
|
|
|
|
|
- `sqlite sqlite_unlock_notify`: 这个编译选项将启用SQLite3数据库的支持,建议只在少数人使用时使用这个模式。
|
|
|
|
|
- `pam`: 这个编译选项将会启用 PAM (Linux Pluggable Authentication Modules) 认证,如果你使用这一认证模式的话需要开启这个选项。
|
2017-11-26 16:44:32 -05:00
|
|
|
|
|
2019-12-05 12:18:28 -05:00
|
|
|
|
使用 bindata 可以打包资源文件到二进制可以使开发和测试更容易,你可以根据自己的需求决定是否打包资源文件。
|
|
|
|
|
要包含资源文件,请使用 `bindata` tag:
|
2017-11-26 16:44:32 -05:00
|
|
|
|
|
2019-12-05 12:18:28 -05:00
|
|
|
|
```bash
|
|
|
|
|
TAGS="bindata" make build
|
2017-11-26 16:44:32 -05:00
|
|
|
|
```
|
|
|
|
|
|
2019-12-05 12:18:28 -05:00
|
|
|
|
默认的发布版本中的编译选项是: `TAGS="bindata sqlite sqlite_unlock_notify"`。以下为推荐的编译方式:
|
2017-11-26 16:44:32 -05:00
|
|
|
|
|
2019-12-05 12:18:28 -05:00
|
|
|
|
```bash
|
|
|
|
|
TAGS="bindata sqlite sqlite_unlock_notify" make build
|
2017-11-26 16:44:32 -05:00
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
## 测试
|
|
|
|
|
|
|
|
|
|
在执行了以上步骤之后,你将会获得 `gitea` 的二进制文件,在你复制到部署的机器之前可以先测试一下。在命令行执行完后,你可以 `Ctrl + C` 关掉程序。
|
|
|
|
|
|
2022-08-14 12:03:12 -04:00
|
|
|
|
```bash
|
2017-11-26 16:44:32 -05:00
|
|
|
|
./gitea web
|
|
|
|
|
```
|
|
|
|
|
|
2022-08-14 12:03:12 -04:00
|
|
|
|
## 交叉编译
|
|
|
|
|
|
|
|
|
|
Go 编译器支持交叉编译到不同的目标架构。有关 Go 支持的目标架构列表,请参见 [Optional environment variables](https://go.dev/doc/install/source#environment)。
|
|
|
|
|
|
|
|
|
|
交叉构建适用于 Linux ARM64 的 Gitea:
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
GOOS=linux GOARCH=arm64 make build
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
交叉构建适用于 Linux ARM64 的 Gitea,并且带上 Gitea 发行版采用的编译选项:
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
CC=aarch64-unknown-linux-gnu-gcc GOOS=linux GOARCH=arm64 TAGS="bindata sqlite sqlite_unlock_notify" make build
|
|
|
|
|
```
|