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
@@ -73,50 +73,6 @@ it's recommended to use `const _promise = asyncFoo()` to tell readers
73
73
that this is done by purpose, we want to call the async function and ignore the Promise.
74
74
Some lint rules and IDEs also have warnings if the returned Promise is not handled.
75
75
76
-
#### DOM Event Listener
77
-
78
-
```js
79
-
el.addEventListener('click', (e) => {
80
-
(async () => {
81
-
awaitasyncFoo(); // recommended
82
-
// then we shound't do e.preventDefault() after await, no effect
83
-
})();
84
-
85
-
const_promise=asyncFoo(); // recommended
86
-
87
-
e.preventDefault(); // correct
88
-
});
89
-
90
-
el.addEventListener('async', async (e) => { // not recommended but acceptable
91
-
e.preventDefault(); // acceptable
92
-
awaitasyncFoo(); // skip out event dispatch
93
-
e.preventDefault(); // WRONG
94
-
});
95
-
```
96
-
97
-
#### jQuery Event Listener
98
-
99
-
```js
100
-
$('#el').on('click', (e) => {
101
-
(async () => {
102
-
awaitasyncFoo(); // recommended
103
-
// then we shound't do e.preventDefault() after await, no effect
104
-
})();
105
-
106
-
const_promise=asyncFoo(); // recommended
107
-
108
-
e.preventDefault(); // correct
109
-
returnfalse; // correct
110
-
});
111
-
112
-
$('#el').on('click', async (e) => { // not recommended but acceptable
113
-
e.preventDefault(); // acceptable
114
-
returnfalse; // WRONG, jQuery expects the returned value is a boolean, not a Promise
115
-
awaitasyncFoo(); // skip out event dispatch
116
-
returnfalse; // WRONG
117
-
});
118
-
```
119
-
120
76
### HTML Attributes and `dataset`
121
77
122
78
We forbid `dataset` usage, its camel-casing behaviour makes it hard to grep for attributes. However there are still some special cases, so the current guideline is:
Copy file name to clipboardExpand all lines: docs/content/doc/usage/backup-and-restore.en-us.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,12 @@ file can be unpacked and used to restore an instance.
22
22
23
23
{{< toc >}}
24
24
25
+
## Backup Consistency
26
+
27
+
To ensure the consistency of the Gitea instance, it must be shutdown during backup.
28
+
29
+
Gitea consists of a database, files and git repositories, all of which change when it is used. For instance, when a migration is in progress, a transaction is created in the database while the git repository is being copied over. If the backup happens in the middle of the migration, the git repository may be incomplete although the database claims otherwise because it was dumped afterwards. The only way to avoid such race conditions is by stopping the Gitea instance during the backups.
30
+
25
31
## Backup Command (`dump`)
26
32
27
33
Switch to the user running Gitea: `su git`. Run `./gitea dump -c /path/to/app.ini` in the Gitea installation
@@ -48,6 +54,17 @@ Inside the `gitea-dump-1482906742.zip` file, will be the following:
48
54
Intermediate backup files are created in a temporary directory specified either with the
49
55
`--tempdir` command-line parameter or the `TMPDIR` environment variable.
50
56
57
+
## Backup the database
58
+
59
+
The SQL dump created by `gitea dump` uses XORM and Gitea admins may prefer to use the native the MySQL and PostgreSQL dump tools instead. There are still open issues when using XORM for dumping the database that may cause problems when attempting to restore it.
Copy file name to clipboardExpand all lines: docs/content/page/index.de-de.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ Gitea ist ein [Gogs](http://gogs.io)-Fork.
26
26
- 2 CPU Kerne und 1GB RAM sind für kleine Teams/Projekte ausreichend.
27
27
- Gitea sollte unter einem seperaten nicht-root Account auf UNIX-Systemen ausgeführt werden.
28
28
- Achtung: Gitea verwaltet die `~/.ssh/authorized_keys` Datei. Gitea unter einem normalen Benutzer auszuführen könnte dazu führen, dass dieser sich nicht mehr anmelden kann.
29
-
-[Git](https://git-scm.com/) Version 1.7.2 oder später wird benötigt. Version 1.9.0 oder später wird empfohlen. Außerdem zu beachten:
29
+
-[Git](https://git-scm.com/) Version 2.0 oder später wird benötigt.
30
30
- Wenn git >= 2.1.2. und [Git large file storage](https://git-lfs.github.com/) aktiviert ist, dann wird es auch in Gitea verwendbar sein.
31
31
- Wenn git >= 2.18, dann wird das Rendern von Commit-Graphen automatisch aktiviert.
Copy file name to clipboardExpand all lines: docs/content/page/index.fr-fr.md
+8-11Lines changed: 8 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -249,27 +249,24 @@ Le but de ce projet est de fournir de la manière la plus simple, la plus rapide
249
249
250
250
## Navigateurs supportés
251
251
252
-
- Consultez [Semantic UI](https://github.com/Semantic-Org/Semantic-UI#browser-support) pour la liste des navigateurs supportés.
253
-
- La taille minimale supportée officielement est de **1024*768**, l'interface utilisateur peut toujours fonctionner à une taille plus petite, mais ce n'est pas garanti et les problèmes remontés ne seront pas corrigés.
252
+
- Chrome, Firefox, Safari, Edge
254
253
255
254
## Composants
256
255
257
256
* Framework web : [Chi](http://github.com/go-chi/chi)
0 commit comments