gitea | Git with a cup of tea! Painless self-hosted all-in-one software development service, includes Git ho | Continuous Deployment library
kandi X-RAY | gitea Summary
kandi X-RAY | gitea Summary
Git with a cup of tea! Painless self-hosted all-in-one software development service, includes Git hosting, code review, team collaboration, package registry and CI/CD
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of gitea
gitea Key Features
gitea Examples and Code Snippets
Community Discussions
Trending Discussions on gitea
QUESTION
I tried importing via default gitlab "import from gitea" and all I got - repositories with only FIRST commit, broken list of repositories from gitea (gitlab for some reason misplaces names of gitea repositories resulting in "name already taken").
Can I somehow export gitea repos into archive and import with 1 file or something? I'm afraid default gitlab import is not working for me, and our gitea server due to be disabled soon (migrating to server with better infrastructure).
...ANSWER
Answered 2022-Mar-16 at 08:19One possible workaround is, for each Gitea repository:
- clone it
- change the remote (
git remote set-url origin https://gitlab.com/...) to a new empty GitLab project/repository, which can be done from command line, using API orgitlab-cli git push --mirror
So you can script those steps, and loop over each of your Gitea repository that way.
QUESTION
We migrated a repository from a Gitea server to BitBucket. When we try to clone via HTTPS we get the following error:
Error downloading object: : Smudge error: Error downloading : Object does not exist on the server: [404] Object does not exist on the server.
I followed this SO answer and I can clone, but when I do the git lfs pull I get a bunch of
[404] Object does not exist
I then tried setting the lfs.url value as in this answer and then a git lfs pull results in
Repository or object not found: /objects/batch, Check that it exists and that you have proper access to it.
After that, I saw some posts about issues with LFS and HTTPS so I tried cloning with SSH. (created new SSH key, added it to BitBucket, etc) This resulted in
error: external filter 'git-lfs filter-process' failed, fatal: : smudge filter lfs failed, warning: Clone succeeded , but checkout failed.
I then tried running git lfs install --skip-smudge and cloning again via SSH. This worked, again, but the files are not accessible and when I run git lfs pull now I get the following message multiple times:
batch request: git@bitbucket.org: Permission denied (publickey).: exit status 255
How do I fix this?
...ANSWER
Answered 2022-Mar-07 at 19:48It appears Bitbucket's import tool does not import LFS objects. I ended up following the steps here to fix the problem (note that I updated step 9 to include origin to fix an error).
First, create new a repo on Bitbucket and take note of the URL (or SSH endpoint) of the new repo. (I did not do this as I was fixing a repo I had already created)
In a terminal window, clone the existing project from GitHub:
QUESTION
I'm using rsync to sync data from a VPS to a local storage NAS connected via a Wireguard tunnel.
This has been working perfectly for months but I noticed a few weeks ago that syncs wouldn't complete anymore.
I investigated a bit and found out that rsync just starts to hang in certain operations and eventually times out because of this. Here's the log from an rsync operation using -vvvrP flags:
...ANSWER
Answered 2022-Jan-31 at 11:25I've figured it out, Tshark gave me a hint with the TCP Retransmission errors, reverse searching that on google reveals that MTU settings might be at fault and indeed that was the issue, setting the MTU correctly in Wireguard has resolved this issue
QUESTION
So, I got a basic Gitea Instance here: https://git.cowdev.online, but I would like to rename my site. NOTE: It's actually a Nginx server which uses a Gitea Server on port 3000 as a reverse proxy. If the website goes down, It's most likely I'm just playing with it or my Server trial or Domain ended. UPDATE: I upgraded to GitLab, So you can't use the link anymore.
...ANSWER
Answered 2022-Jan-01 at 05:46Found the solution, there's a property in gitea's config file (for me located in /var/snap/gitea/gitea-common/gitea.ini)
QUESTION
I am trying to use mui TextField, I can change the color when focused (using theme). But however, I can't seem to find a way to changed its color (label, and border) when it's NOT focused (initial). Seems like it's always black, which means if I am using a black background it cannot be properly shown.
I would like a way to change its initial color to white, or any other color. Thanks.
Also, with the Select list, I have a same problem.
Below is my code (unrelated things are removed):
...ANSWER
Answered 2022-Jan-10 at 16:14See code below and codesandbox for a working example.
QUESTION
I have a problem with my gitea version 1.15.5 running on my raspberry pi. I appears that the built in ssh server is not starting:
...ANSWER
Answered 2021-Oct-23 at 13:00After some more googling, I found the solution myself:
If there is an sshd server running, gitea does not automatically start its built-in ssh server. Instead, you have to force it by adding this line under [server] in the app.ini configuration:
QUESTION
I've googled and googled and not sure what I'm doing wrong. it seems how ever way i try to set the root password for mysql, it doesn't seem to work. I'm currently testing out the below(which i've seen plastered over the internet) and this too doesn't work. I'm not getting any errors, logs do not show any errors, and honestly at this point, I'm kind of lost and would appreciate some help.
secrets.yaml file:
...ANSWER
Answered 2021-Oct-15 at 19:02I remember having a similar problem with Docker. I ended deleting (CAREFUL HERE) any folder created during the creation of the previous mysql docker container. One of those folders has the password for the root user and unless this is deleted or changed it will continue with any other mysql container used to replace the old one.
QUESTION
typedef struct ResponseBody {
size_t memorySize = BUFSIZ;
size_t dataSize{};
char *bodyMemory = new char[BUFSIZ];
public:
~ResponseBody();
} ResponseBody;
ResponseBody::~ResponseBody() {
delete[] this->bodyMemory;
}
size_t get_containers_callback(const char *buff, size_t size, size_t buff_size, void *data) {
auto *body = (ResponseBody *) data;
size_t needMemory = body->dataSize + buff_size;
if (needMemory > body->memorySize) {
auto *newMemory = new char[needMemory];
strcpy(newMemory, body->bodyMemory);
delete[] body->bodyMemory;
body->bodyMemory = newMemory;
body->memorySize = needMemory;
}
memcpy(body->bodyMemory + body->dataSize, buff, buff_size);
body->dataSize += buff_size;
return size * buff_size;
}
int main() {
auto *responseBody = new ResponseBody;
curl_easy_setopt(curl, CURLOPT_URL, "http://localhost:8080/containers/json?all=true");
curl_easy_setopt(curl, CURLOPT_WRITEFUNCTION, get_containers_callback);
curl_easy_setopt(curl, CURLOPT_WRITEDATA, responseBody);
res = curl_easy_perform(curl);
if (res == CURLE_OK) {
fprintf(stdout, "%s\n", responseBody->bodyMemory);
}
return 0;
}
ANSWER
Answered 2021-Oct-14 at 14:52Using "proper" C++ your code could be rewritten something like this:
QUESTION
Backstory: I am working on a Windows PC that is connected to a Ubuntu laptop via SSH. This laptop is connected to the company network via VPN. Company uses gitea (if that's relevant).
The problem: While attempting to use git from PC (Windows Terminal, VS Code terminal, VS Code git features) I am getting a Permission denied (publickey) message. Everything works fine if I'm trying to do the same from a terminal on the laptop.
Similarly, pipenv install fails on installing dependencies from the repository.
Visualization :)
[Laptop]: git pull results in a successful pull
[PC --ssh-> Laptop]: git pull results in a permission denied
No such things happen when I try to access my private github repos with PC ssh'd to my other computer. I have even tried adding a key generated on PC to the authorized git keys with no improvement whatsoever.
EDIT: @VonC's answer made me run a verbose ssh connection and revealed that ssh-agent wasn't running for my remote connection and only offered keys from ~/.ssh/ that started with id_ while my git key had a git_ prefix.
ANSWER
Answered 2021-Aug-19 at 11:57Test first, from a simple CMD:
QUESTION
I have a cluster with 4 nodes (3 raspi, 1 NUC) and have setup several different workloads. The cluster itself worked perfectly fine, so I doubt that it is a general problem with the configuration. After a reboot of all nodes the cluster came back up well and all pods are running without issues. Unfortunately, pods that are running on one of my nodes (NUC) are not reachable via ingress anymore. If I access them through kube-proxy, I can see that the pods itself run fine and the http services behave as exptected. I upgraded the NUC node from Ubuntu 20.10 from 21.04, which may be related to the issues, but is not confirmed.
When the same pods are scheduled to the other nodes everything works as expected. For pods on the NUC node, I see the following in the ingress-controller logs:
...ANSWER
Answered 2021-Aug-11 at 21:42Updating flannel from 13.1-rc2 to 14.0 seems to have done the trick. Maybe some of the iptables rules were screwed and got revreated, maybe 14.0 is necessary to work with 21.04? Who knows... I'm back up running fine and happy :)
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install gitea
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
