Feature Description There is a problem occurs while setting up the gitea repo locally after forking it Screenshots No response
It took us quite a bit of troubleshooting to narrow it down to the fact that it happens when the users password is longer than 64 characters. If this is a limitation that's unable to be overcome, it would be nice to have a warning on the registration page that states that passwords ca...
Gitea is a painless self-hosted Git service written in GO, and very lightweight. It is somewhat similar to GitHub, Bitbucket and Gitlab. As well as support for Git revision control, it also provides issue tracking and wiki pages development. If you are looking for an alternative to Gitea,...
2024/10/13 19:18:58 ...eb/routing/logger.go:102:func1() [I] router: completed GET /organisation/repository/wiki/TopLevel1/TopLevel2/L2Page.md for 192.168.178.59:0, 500 Internal Server Error in 57.4ms @ repo/wiki.go:532(repo.Wiki) While troubleshooting I did a git ls-files | grep...
For integration with gitea: Install jenkins gitea plugin Configure access to gitea (manage -> configure, scroll to gitea server section) which will show up in the Server dropdowns Configure gitea repo webhook to jenkins (sometimes Jenkins automatically configures this) ...
Gitea + MySQL setup via Docker Compose. Contribute to bossjones/docker-compose-gitea-server development by creating an account on GitHub.
For troubleshooting, the things that I would have a look are The owners and file permissions of the repository files and directories. The user/group of the Gitea process in the container. The log in gitea.log at the moment when creating the repository. Author holmesb commented Aug 31, 2019...
I use gitea on windows with "START_SSH_SERVER" set to true. But when I pull my repository. I got the following error: fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. The Troubleshooting section in gitea document ...
This is a longer, albeit more complete guide on troubleshooting your connection. Note: if Gitea is running on a different server, I can't see how it could connect through named pipes; it must use TCP/IP, therefore it must use port 1433 or some TCP port (1433 is the standard, however...
Add LFS timeout issue to troubleshooting doc (go-gitea#5129) Oct 21, 2018 integrations CN translation of README (go-gitea#5050) Oct 15, 2018 models Increase the retry limit to 20 times and the interval to 200ms (go-gi… Oct 21, 2018 ...