mike_wooskey, 1 month ago I don’t know if your problem is the same as mine was, but the symptom sounds the same. The docker-compose.yaml file shown in the Forgejo documentation for docker installation shows this mount: <span style="color:#323232;"> volumes: </span><span style="color:#323232;"> - ./forgejo:/data </span> For me, Forgejo installed and created new resource files in /data and ignored the resource files gitea alread made. I changed the volume to: <span style="color:#323232;"> volumes: </span><span style="color:#323232;"> - data:/var/lib/gitea </span> Forgejo then recognized the gitea resources.
I don’t know if your problem is the same as mine was, but the symptom sounds the same.
The docker-compose.yaml file shown in the Forgejo documentation for docker installation shows this mount:
<span style="color:#323232;"> volumes: </span><span style="color:#323232;"> - ./forgejo:/data </span>
For me, Forgejo installed and created new resource files in /data and ignored the resource files gitea alread made.
/data
I changed the volume to:
<span style="color:#323232;"> volumes: </span><span style="color:#323232;"> - data:/var/lib/gitea </span>
Forgejo then recognized the gitea resources.