You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/content/doc/installation/from-binary.en-us.md
+13-13Lines changed: 13 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ location. When launched manually, Gitea can be killed using `Ctrl+C`.
44
44
45
45
## Recommended server configuration
46
46
47
-
**NOTE:** Many of the following directories can be configured using [Environment Variables]({{< relref "doc/advanced/specific-variables.en-us.md" >}}) as well!
47
+
**NOTE:** Many of the following directories can be configured using [Environment Variables]({{< relref "doc/advanced/specific-variables.en-us.md" >}}) as well!
48
48
Of note, configuring `GITEA_WORK_DIR` will tell Gitea where to base its working directory, as well as ease installation.
49
49
50
50
### Prepare environment
@@ -80,7 +80,7 @@ chmod 770 /etc/gitea
80
80
**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:
81
81
```
82
82
chmod 750 /etc/gitea
83
-
chmod 644 /etc/gitea/app.ini
83
+
chmod 640 /etc/gitea/app.ini
84
84
```
85
85
If you don't want the web installer to be able to write the config file at all, it is also possible to make the config file read-only for the gitea user (owner/group `root:root`, mode `0660`), and set `INSTALL_LOCK = true`. In that case all database configuration details must be set beforehand in the config file, as well as the `SECRET_KEY` and `INTERNAL_TOKEN` values. See the [command line documentation]({{< relref "doc/usage/command-line.en-us.md" >}}) for information on using `gitea generate secret INTERNAL_TOKEN`.
86
86
@@ -113,16 +113,16 @@ GITEA_WORK_DIR=/var/lib/gitea/ /usr/local/bin/gitea web -c /etc/gitea/app.ini
113
113
114
114
## Updating to a new version
115
115
116
-
You can update to a new version of Gitea by stopping Gitea, replacing the binary at `/usr/local/bin/gitea` and restarting the instance.
117
-
The binary file name should not be changed during the update to avoid problems
118
-
in existing repositories.
116
+
You can update to a new version of Gitea by stopping Gitea, replacing the binary at `/usr/local/bin/gitea` and restarting the instance.
117
+
The binary file name should not be changed during the update to avoid problems
118
+
in existing repositories.
119
119
120
120
It is recommended you do a [backup]({{< relref "doc/usage/backup-and-restore.en-us.md" >}}) before updating your installation.
121
121
122
-
If you have carried out the installation steps as described above, the binary should
123
-
have the generic name `gitea`. Do not change this, i.e. to include the version number.
122
+
If you have carried out the installation steps as described above, the binary should
123
+
have the generic name `gitea`. Do not change this, i.e. to include the version number.
124
124
125
-
See below for troubleshooting instructions to repair broken repositories after
125
+
See below for troubleshooting instructions to repair broken repositories after
126
126
an update of your Gitea version.
127
127
128
128
## Troubleshooting
@@ -145,7 +145,7 @@ is already running.
145
145
146
146
### Running Gitea on Raspbian
147
147
148
-
As of v1.8, there is a problem with the arm7 version of Gitea and it doesn't run on Raspberry Pi and similar devices.
148
+
As of v1.8, there is a problem with the arm7 version of Gitea and it doesn't run on Raspberry Pi and similar devices.
149
149
150
150
It is therefore recommended to switch to the arm6 version which has been tested and shown to work on Raspberry Pi and similar devices.
151
151
@@ -154,18 +154,18 @@ please remove after fixing the arm7 bug
154
154
--->
155
155
### Git error after updating to a new version of Gitea
156
156
157
-
If the binary file name has been changed during the update to a new version of Gitea,
158
-
git hooks in existing repositories will not work any more. In that case, a git
157
+
If the binary file name has been changed during the update to a new version of Gitea,
158
+
git hooks in existing repositories will not work any more. In that case, a git
159
159
error will be displayed when pushing to the repository.
160
160
161
161
```
162
162
remote: ./hooks/pre-receive.d/gitea: line 2: [...]: No such file or directory
163
163
```
164
164
165
-
The `[...]` part of the error message will contain the path to your previous Gitea
165
+
The `[...]` part of the error message will contain the path to your previous Gitea
166
166
binary.
167
167
168
-
To solve this, go to the admin options and run the task `Resynchronize pre-receive,
168
+
To solve this, go to the admin options and run the task `Resynchronize pre-receive,
169
169
update and post-receive hooks of all repositories` to update all hooks to contain
170
170
the new binary path. Please note that this overwrite all git hooks including ones
0 commit comments