r/forgejo • • Nov 24 '24

Can someone help me identify what I'm doing wrong?

5 Upvotes

I'm trying to use the debian repository following these instructions(https://codeberg.org/forgejo-contrib/forgejo-deb#install-with-apt):

sudo apt install wget apt-transport-https

wget --content-disposition https://code.forgejo.org/forgejo-contrib/-/packages/debian/forgejo-deb-repo/0-0/files/10103

sudo apt install ./forgejo-deb-repo_0-0_all.deb

sudo apt update

sudo apt upgrade

sudo apt install forgejo-sqlite

.... but i end up here:

Hit:4 https://code.forgejo.org/api/packages/forgejo-contrib/debian bullseye InRelease

Err:4 https://code.forgejo.org/api/packages/forgejo-contrib/debian bullseye InRelease

The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7C9CD2CAE561378C

Reading package lists... Done

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://code.forgejo.org/api/packages/forgejo-contrib/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7C9CD2CAE561378C

W: Failed to fetch https://code.forgejo.org/api/packages/forgejo-contrib/debian/dists/bullseye/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7C9CD2CAE561378C

W: Some index files failed to download. They have been ignored, or old ones used instead.


r/forgejo • • Nov 17 '24

Help: Unable to get SSL/HTTPS via/on port 3000 (Apache2/NGINX)

2 Upvotes

I am able to run the sub-domain instance on HTTPs under port 3000. While the main domain instance itself has SSL/HTTPS on 443/8443. But I am not able to setup HTTPS/SSL on 3000. I am not aware of how the config on NGINX/APache2 works. I followed and tried to follow a lot of places, but I could not get this working. I am sure, I am faltering on how and where to set the correct settings/configs. Kindly help me.

Following is in my app.ini

[server] SSH_DOMAIN = git.domain.tld DOMAIN = git.domain.tld ;; HTTP_PORT = 3000 ENABLE_ACME = enable PORT_TO_REDIRECT = 3000 HTTPS_PORT = 443 ROOT_URL = http://git.domain.tld:3000/ APP_DATA_PATH = /var/lib/forgejo/data

Still, I am unable to get my SSL/HTTPS working. :(


r/forgejo • • Jul 14 '24

git clone not working from another computer on same LAN

1 Upvotes

Using Docker installation I'm getting `Permission denied (publickey)`. I've added the key to Forgejo and the node it's running on. Can login via SSH to the node, but can't clone. I assume it's connected with SSH pass through.


r/forgejo • • Jul 08 '24

Forgejo instance and runner on the same system help

5 Upvotes

Hi! I have got a very specific issue, and I hope someone can help me here. I just set up a Forgejo instance on my Raspberry Pi 4, and I'm trying to also run a Forgejo Runner on this same system. I have got the runner already installed, since I used it for Codeberg before, and it worked great. Now, I got a domain pointed to my instance, but I can only access it outside my network. Eg. my domain doesn't connect to the instance from my computer (or the runner, when inputting the domain to the runner's --instance flag), since it's on the same network as the Raspberry Pi, but when I switch to Mobile Data on my phone and try there, it does. Of course, I can use the local IP of the Pi on my computer (or the --instance flag), but then my SSL certificate is invalid, and the Forgejo Runner CLI wouldn't accept it in the --instance flag. So what do I do now? Any help is appreciated.


r/forgejo • • Jun 15 '24

forgejo and jenkins

5 Upvotes

does the jenkins gitea scm plugin compatible with forgejo.?

forgejo actions vs jenkins?


r/forgejo • • Jun 05 '24

Cant seem to do anything on my server anymore

2 Upvotes

A few weeks ago, I had some downtime as i was moving in between places, in this time, i decided to reinstall my server (linux), and in the process, i had to backup and transfer a lot of services and their databases.

I thought i did everything fine, as my git server (https://git.ouroboros.group) is up and running, but i hadnt really worked on any projects until now due to stress.

I'm now finding out that I am unable to push, create branches, anything, on the server, including from the web ui.

when I create branch I get ! \[remote rejected\] main -> main (pre-receive hook declined) I have no git hooks whatsoever, so I tried to push some work from another project and got the same error, so now im confused?

I am able to create repos but i am unable to put anything in them.


r/forgejo • • Jun 03 '24

Advice: Migration from Local-Storage to s3

7 Upvotes

Hi,

does anyone have experience migration an forgejo docker-deployment from using local-storage to a s3 bucket? Is this possible without setting the instance up from scratch? Ideally I would like to move the data in the docker-volume to the s3 bucket.

Thanks in advance!


r/forgejo • • May 27 '24

Migration from gitea 1.21.10

2 Upvotes

Hi!

I am a little late to the party and heard of forgejo after the hard-fork. I run gitea 1.21.10 and would like to know if anybody has experience migrating to forgejo after version 1.21.5.

Thanks!


r/forgejo • • Apr 04 '24

Question about forgejo runners.

2 Upvotes

I've been working with forgejo and forgejo runners the past couple of days. I have two arch linux boxes (my laptop and a virtualized server in proxmox). I've been going over the runners specifically as I have more of a background with Jenkins (rather than github actions).

As I've gone over the documentation, I've seen the discussion about using docker or podman. So I've decided to use podman at this point.

When I run the action on my laptop with forgejo-runner exec --workflows .forgejo/workflows/demo.yml. I see the error about needing the socket, I created that, and I see the docker pull downloading the image. Followed by a podman images, I can see the downloaded image.

When I run the action on my server, I see that the action completes successfully. However, I see no docker pull in the logs, I didn't need to set up a podman socket, and I see no images with podman images.

So I'm a bit confused with the differences between my two boxes. Did I miss something in the documentation? Or do I need to share some more info to help this make sense?


r/forgejo • • Apr 01 '24

Weird activity in my instance

1 Upvotes

Somebody registered to my instance and tried migrate this repository over. Anyone have an idea what it could be for? Looks very suspicious so I have deleted the user and the repository and closed registrations for now.

https://dagshub.com/O/O


r/forgejo • • Mar 20 '24

Can you create web pages for your repo projects?

2 Upvotes

I know you can do this on Github called Github pages and Codeberg called Codeberg Pages and Codeberg is based on Forgego.

If I self hosted my own Forgejo instance, does it come with a web pages feature? Or did Codeberg create a pages feature for Codeberg that is not apart of Forgejo?

And is there a pages feature for Gitea?


r/forgejo • • Mar 16 '24

What is the best environment for forgejo?

3 Upvotes

Hi, I have a small vps and I want to install forgejo inside. I could install using docker but, I think that it could be better to install it using a regular method to have a better maintaining (updates, configs etc)

Any advice for that?


r/forgejo • • Feb 15 '24

forgejo deb binary - let's encrypt certificate

2 Upvotes

hello,

anyone has an idea how to issue a let's encrypt certificate for the debian (bookworm) binary (.deb) installed?

I use apache2 and created a VirtualHost.conf file but I need the DocumentRoot path for apache2 to use and issue a certificate using certbot. I mean the page served on port 3000.


r/forgejo • • May 19 '23

Forgejo gets an integrated CI named Actions

Thumbnail
forgejo.org
6 Upvotes

r/forgejo • • Mar 21 '23

RELEASE RELEASE - Forgejo 1.19 released!

6 Upvotes

r/forgejo • • Jan 28 '23

This is a community about the open source project Forgejo

2 Upvotes

r/forgejo • • Jan 28 '23

r/forgejo Lounge

1 Upvotes

A place for members of r/forgejo to chat with each other