techknowlogick
52808369d4
Update docusaurus.config.js
2023-11-27 04:43:08 +00:00
Giteabot and CodeShakingSheep
804129d9ff
Docs: Replace deprecated IS_TLS_ENABLED mailer setting in email setup ( #28205 ) ( #28208 )
...
Backport #28205 by @CodeShakingSheep
In the [docs for email
setup](https://docs.gitea.com/administration/email-setup )
`mailer.IS_TLS_ENABLED` is mentioned which was replaced by
`mailer.PROTOCOL` in release 1.18.0 according to
https://blog.gitea.com/release-of-1.18.0/ . This change wasn't reflected
in the docs for email setup. I just replaced the deprecated mailer
setting.
Co-authored-by: CodeShakingSheep <[email protected]
2023-11-25 15:41:01 +08:00
Renovate Bot
e13745aa3f
fix(deps): update dependency @easyops-cn/docusaurus-search-local to ^0.38.0 ( #91 )
...
Co-authored-by: Renovate Bot <[email protected] [email protected]
2023-11-25 04:17:25 +00:00
CodeShakingSheep
2233876d46
Docs: Replace deprecated IS_TLS_ENABLED mailer setting in email setup ( #28205 )
...
In the [docs for email
setup](https://docs.gitea.com/administration/email-setup )
`mailer.IS_TLS_ENABLED` is mentioned which was replaced by
`mailer.PROTOCOL` in release 1.18.0 according to
https://blog.gitea.com/release-of-1.18.0/ . This change wasn't reflected
in the docs for email setup. I just replaced the deprecated mailer
setting.
2023-11-25 10:16:29 +08:00
Giteabot and yp05327
b024987618
Fix some incorrect links in docs ( #28191 ) ( #28201 )
...
Backport #28191 by @yp05327
https://gitea.com/gitea/gitea-docusaurus/actions/runs/661/jobs/0#jobstep-9-39
I noticed that there are many warning logs in building docs.
It is causing 404 in docs.gitea.com now, so we need to fix it.
And there are also some other problems in v1.19 which can not be done in
this PR.
Co-authored-by: yp05327 <[email protected]
2023-11-24 19:55:08 +00:00
yp05327
aaa49886ff
Fix some incorrect links in docs ( #28191 )
...
https://gitea.com/gitea/gitea-docusaurus/actions/runs/661/jobs/0#jobstep-9-39
I noticed that there are many warning logs in building docs.
It is causing 404 in docs.gitea.com now, so we need to fix it.
And there are also some other problems in v1.19 which can not be done in
this PR.
ps: Are there any good methods to test this in local?
2023-11-24 13:57:09 +00:00
yp05327
be67d3f610
Remove misadded packages docs in 1.19 ( #28192 )
...
Follow #28191
There are some misadded docs in #24914 's backport PR #25016 .
The following package registries are all supported in 1.20, so we should
not have docs in v1.19
- Alpine (#23714 )
- CRAN (#22343 )
- Debain (#24426 )
- Go (#24687 )
- RPM (#23380 )
2023-11-24 01:09:17 -05:00
Giteabot and yp05327
1c3dadcb1c
Fix the description about the default setting for action in quick start document ( #28160 ) ( #28168 )
...
Backport #28160 by @yp05327
Since #27054 , Actions are enabled by default. so we should also edit the
document. 😃
ps: I think this should be backport to 1.21.0.
Co-authored-by: yp05327 <[email protected]
2023-11-22 16:46:11 +08:00
yp05327
5195cc7e92
Fix the description about the default setting for action in quick start document ( #28160 )
...
Since #27054 , Actions are enabled by default. so we should also edit the
document. 😃
ps: I think this should be backport to 1.21.0.
2023-11-22 02:11:22 +00:00
techknowlogick
6da93d0e87
rm announcement bar as docs have been live for half a year
2023-11-21 20:31:28 +00:00
techknowlogick
c4259b9a83
1.21
2023-11-20 05:35:14 +00:00
John Olheiser
6d8e32689d
Update docs for docusaurus v3 ( #28125 )
...
Updates the docs for usage with docusaurus v3
Signed-off-by: jolheiser <[email protected]
2023-11-20 00:25:47 -05:00
John Olheiser
79dfabcd5a
Update docs for docusaurus v3 ( #28128 )
...
Signed-off-by: jolheiser <[email protected]
2023-11-20 00:25:22 -05:00
John Olheiser
163765d335
Update docs for docusaurus v3 ( #28126 )
...
Signed-off-by: jolheiser <[email protected]
2023-11-20 00:24:50 -05:00
John Olheiser
82ce3ded0a
Update docs for docusaurus v3 ( #28127 )
...
Signed-off-by: jolheiser <[email protected]
2023-11-20 00:24:36 -05:00
jolheiser
52841fa1d9
Makefile enhancements ( #89 )
...
These are some things I changed to make local development easier, especially when having to update multiple versions of docs at once like the docusaurus v3 update.
i.e.
```makefile
GITEA_REMOTE := ~/code/code.gitea.io/gitea
GITEA_LATEST_BRANCH := docs-v3
GITEA_VERSION_BRANCH_PREFIX := docs-v3-
...
```
to run the Makefile against my local repo.
Reviewed-on: https://gitea.com/gitea/gitea-docusaurus/pulls/89
Co-authored-by: jolheiser <[email protected] [email protected]
2023-11-20 04:27:27 +00:00
Denys Konovalov
697a90b01c
add skip ci functionality ( #28075 )
...
Adds the possibility to skip workflow execution if the commit message
contains a string like [skip ci] or similar.
The default strings are the same as on GitHub, users can also set custom
ones in app.ini
Reference:
https://docs.github.com/en/actions/managing-workflow-runs/skipping-workflow-runs
Close #28020
2023-11-18 13:37:08 +02:00
Renovate Bot
213177e524
fix(deps): update dependency @easyops-cn/docusaurus-search-local to v0.37.4 ( #87 )
...
Co-authored-by: Renovate Bot <[email protected] [email protected]
2023-11-16 01:43:21 +00:00
Renovate Bot
dc68e99a1a
fix(deps): update dependency prism-react-renderer to v2.2.0 ( #86 )
...
Co-authored-by: Renovate Bot <[email protected] [email protected]
2023-11-16 01:42:58 +00:00
Lunny Xiao
1f528ecb35
Update 1.21.0 version
2023-11-15 13:16:15 +08:00
Giteabot and Nanguan Lin
7e1b2579a1
Change default size of issue/pr attachments and repo file ( #27946 ) ( #28017 )
...
Backport #27946 by @lng2020
As title. Some attachments and file sizes can easily be larger than
these limits
Co-authored-by: Nanguan Lin <[email protected]
2023-11-13 15:27:39 +01:00
Nanguan Lin
c333830929
Change default size of issue/pr attachments and repo file ( #27946 )
...
As title. Some attachments and file sizes can easily be larger than
these limits
2023-11-13 14:19:22 +00:00
techknowlogick
d669bc9720
fix theme import
2023-11-10 13:01:41 -05:00
techknowlogick
9c94c41125
bump to v3 of deps
2023-11-10 12:55:26 -05:00
Renovate Bot
8b09ee6be8
fix(deps): update docusaurus monorepo to v3 (major) ( #82 )
...
Co-authored-by: Renovate Bot <[email protected] [email protected]
2023-11-10 17:14:05 +00:00
Renovate Bot
4772c875cd
fix(deps): update react monorepo to v18 (major) ( #80 )
...
Co-authored-by: Renovate Bot <[email protected] [email protected]
2023-11-10 17:11:19 +00:00
f6948ba8ee
Add Profile Readme for Organisations ( #27955 )
...
https://blog.gitea.com/release-of-1.20.0/#-user-profile-readme-23260
(#23260 ) did introduce Profile Readme for Users.
This makes it usable for Organisations:
---
*Sponsored by Kithara Software GmbH*
---------
Co-authored-by: silverwind <[email protected] [email protected]
2023-11-09 14:05:52 +00:00
6543
8025369dd8
Allow to set explore page default sort ( #27951 )
...
as title
---
*Sponsored by Kithara Software GmbH*
2023-11-09 10:11:45 +00:00
Giteabot and 6543
2d11206e9c
Document REACTION_MAX_USER_NUM setting option ( #27954 ) ( #27959 )
...
Backport #27954 by @6543
as title
---
*Sponsored by Kithara Software GmbH*
Co-authored-by: 6543 <[email protected]
2023-11-08 08:54:48 +08:00
6543
7ac34b57d4
Document REACTION_MAX_USER_NUM setting option ( #27954 )
...
https://github.com/go-gitea/gitea/blob/4a0103fa293cc42075d4a9c10ca4dffa9c2d3a40/modules/setting/ui.go#L24
https://github.com/go-gitea/gitea/blob/4a0103fa293cc42075d4a9c10ca4dffa9c2d3a40/modules/setting/ui.go#L77
---
*Sponsored by Kithara Software GmbH*
2023-11-08 01:50:31 +01:00
Giteabot and Nanguan Lin
0c06065ab4
Remove known issue section in Gitea Actions Doc ( #27930 ) ( #27938 )
...
Backport #27930 by @lng2020
The bug has been fixed for several months in the
`docker/build-push-action`
The fix commit is
[d8823bfaed](https://github.com/docker/build-push-action/commit/d8823bfaed2a82c6f5d4799a2f8e86173c461aba )
as the Gitea Actions Doc mentioned too.
Co-authored-by: Nanguan Lin <[email protected]
2023-11-06 17:03:06 +01:00
Nanguan Lin
68a216fd3f
Remove known issue section in Gitea Actions Doc ( #27930 )
...
The bug has been fixed for several months in the
`docker/build-push-action`
The fix commit is
[d8823bfaed](https://github.com/docker/build-push-action/commit/d8823bfaed2a82c6f5d4799a2f8e86173c461aba )
as the Gitea Actions Doc mentioned too.
2023-11-06 22:45:37 +08:00
Giteabot and Moritz Poldrack
7daad25fe2
refactor postgres connection string building ( #27723 ) ( #27869 )
...
Backport #27723 by @mpldr
This patchset changes the connection string builder to use net.URL and
the host/port parser to use the stdlib function for splitting host from
port. It also adds a footnote about a potentially required portnumber
for postgres UNIX sockets.
Fixes : #24552
Co-authored-by: Moritz Poldrack <[email protected]
2023-11-01 23:19:02 +00:00
Moritz Poldrack
c9b2b9c245
refactor postgres connection string building ( #27723 )
...
This patchset changes the connection string builder to use net.URL and
the host/port parser to use the stdlib function for splitting host from
port. It also adds a footnote about a potentially required portnumber
for postgres UNIX sockets.
Fixes : #24552
2023-11-01 18:00:20 +00:00
Giteabot and nodiscc
e1186b6b76
doc: actions/act-runner: document running as a systemd service ( #27844 ) ( #27866 )
...
Backport #27844 by @nodiscc
This documents running `act-runner` as a systemd service under a
dedicated user account.
Co-authored-by: nodiscc <[email protected]
2023-11-01 18:18:01 +01:00
nodiscc
e5c0884503
doc: actions/act-runner: document running as a systemd service ( #27844 )
...
This documents running `act-runner` as a systemd service under a
dedicated user account.
2023-11-01 23:14:40 +08:00
Giteabot and Lunny Xiao
86c8fcdd5b
Fix wrong relative path on obtain token from command line ( #27850 ) ( #27851 )
...
Backport #27850 by @lunny
Caused by #27845
Co-authored-by: Lunny Xiao <[email protected]
2023-10-31 11:36:22 +08:00
Lunny Xiao
494d46b23f
Fix wrong relative path on obtain token from command line ( #27850 )
...
Caused by #27845
2023-10-30 23:31:09 -04:00
Giteabot
93d0b216be
doc: actions/act-runner: document obtaining a runner registration token from gitea CLI ( #27845 ) ( #27848 )
2023-10-30 20:16:05 -04:00
nodiscc
810777a961
doc: actions/act-runner: document obtaining a runner registration token from gitea CLI ( #27845 )
2023-10-30 19:28:02 -04:00
Renovate Bot
4ce58616e6
chore(deps): update actions/setup-node action to v4 ( #81 )
...
Co-authored-by: Renovate Bot <[email protected] [email protected]
2023-10-24 20:10:15 +00:00
HoshinoRei
0256f70d27
Fix an indentation in the Chinese documentation of Act Runner ( #27730 )
...
In the [English
document](https://docs.gitea.com/1.21/usage/actions/act-runner#configuring-cache-when-starting-a-runner-using-docker-image ),
there is indentation here, but there is no indentation in the Chinese
document.
2023-10-22 19:37:56 +08:00
MiloCubed
91ee9fedea
[docs] Add note that PROTOCOL config is case-sensitive ( #25685 )
...
See [issue on
gitea.com](https://gitea.com/gitea/gitea-docusaurus/issues/38 ), copied
below for convenience:
> Hello, may I first confirm that the app.ini PROTOCOL config is case
sensitive (must be lowercase)?
>
> If so, I'd like to suggest for it to be highlighted in the [HTTPS
Setup](https://docs.gitea.com/administration/https-setup#using-the-built-in-server )
page.
> Perhaps something like:
> For the PROTOCOL=https field, make sure https is lowercase. Writing
PROTOCOL=HTTPS may result in a SSL_ERROR_RX_RECORD_TOO_LONG error on
Firefox or ERR_SSL_PROTOCOL_ERROR on Chrome and Edge.
>
> Background
> At first I carelessly wrote PROTOCOL=HTTPS in my app.ini, and Firefox
didn't allow me to connect because:
> Secure Connection Failed
> An error occurred during a connection to gitea.local.lan. SSL received
a record that exceeded the maximum permissible length.
> Error code: SSL_ERROR_RX_RECORD_TOO_LONG
> I spent maybe half an hour troubleshooting my certs, ports, and other
configs before backtracking to the start and realizing the
capitalization difference there 😅 . When I changed that config to
lowercase, it worked.
For this PR I added the note in the Config Cheat Sheet page and fixed
the links to it from the HTTPS Setup page.
Was originally thinking to put the note in the HTTPS Setup page itself,
but since there are 2 sections referencing the PROTOCOL config, I was
thinking it'd be neater and more concise to put it in the Config Cheat
Sheet page instead. Especially since both sections already link to it,
and I actually tried to check that link quite early on in my
troubleshooting (but didn't pay much attention to it since the link was
broken).
## Before/After screenshots as per [this repo's
docs](https://github.com/go-gitea/gitea/tree/main/docs )
Before - links
Note: For this the links weren't broken, the links fix is because they
were broken on gitea.com's docs (see below).
After - links
Before - config cheat sheet
After - config cheat sheet
## Before/After screenshots as per [gitea.com's
docs](https://gitea.com/gitea/gitea-docusaurus )
Before - links
After - links
Before - config cheat sheet
After - config cheat sheet
2023-10-19 16:14:46 +08:00
SandeshPyakurel
11ab160e5a
Typos fixed in documentation files ( #27687 )
...
Typos fixed in multiple docs files.
2023-10-19 02:46:26 -04:00
Sandro Santilli
e7fa5d1014
Update agit-support.en-us.md ( #27652 )
...
Clarify Agit PR creation documentation
See https://github.com/go-gitea/gitea/issues/27579
2023-10-17 17:53:36 +08:00
Giteabot and Nanguan Lin
c599d2a203
Change the default branch in the agit docs ( #27621 ) ( #27623 )
...
Backport #27621 by @lng2020
It's main now.
relevant #27579
Co-authored-by: Nanguan Lin <[email protected]
2023-10-15 09:16:15 +08:00
Nanguan Lin
42e0703455
Change the default branch in the agit docs ( #27621 )
2023-10-14 09:50:23 -04:00
Renovate Bot
c382b955f5
fix(deps): update dependency clsx to v2 ( #78 )
...
Co-authored-by: Renovate Bot <[email protected] [email protected]
2023-10-14 01:32:27 +00:00
KN4CK3R
d1e0a6ead1
Enhanced auth token / remember me ( #27606 )
...
Closes #27455
> The mechanism responsible for long-term authentication (the 'remember
me' cookie) uses a weak construction technique. It will hash the user's
hashed password and the rands value; it will then call the secure cookie
code, which will encrypt the user's name with the computed hash. If one
were able to dump the database, they could extract those two values to
rebuild that cookie and impersonate a user. That vulnerability exists
from the date the dump was obtained until a user changed their password.
>
> To fix this security issue, the cookie could be created and verified
using a different technique such as the one explained at
https://paragonie.com/blog/2015/04/secure-authentication-php-with-long-term-persistence#secure-remember-me-cookies .
The PR removes the now obsolete setting `COOKIE_USERNAME`.
2023-10-14 00:56:41 +00:00
techknowlogick
247f76bebe
rm outdated docs from some languages ( #27530 )
...
related to #27499
2023-10-13 19:29:18 +00:00
techknowlogick
GiteabotandCodeShakingSheep
Renovate Bot
John Olheiser
Denys Konovalov
Lunny Xiao
techknowlogick
HoshinoRei
MiloCubed
SandeshPyakurel
Sandro Santilli