Is this project compatible with gitea?

[Caballerog]

trafficstars

I'm going to testing the project using gitea.

Any idea if this project are not compatible with gitea?

In the next days, I will bring my feedback!

[xet7]

@Caballerog

I don't think there is much difference between Gogs and Gitea. Please test.

[mayjs]

I just tested it, and for me it does not work. There are no error messages, but there is no synchronisation happening at all.

[xet7]

@mayjs

So, Gitea does not work?

Did it work with Gogs?

[mayjs]

I think it does not work, but I will do further research into this issue. I did not test it with Gogs, since I don't have a running Gogs instance at the moment.

[andresmanelli]

I did not check the Gitea API. For different remotes to work we should write or use different clients and provide a mechanism to select which JS module to load (and adapt other parts of the code if necessary). Something similar to Drone environment variables maybe?

[mayjs]

@andresmanelli I just noticed I misunderstood how this tool works. After looking at the code it seems like you use webhooks to get notified on changes in Wekan or Gitea. In my testing environment I did not run the tool on a server with a public URL but on a local machine, which would be an obvious reason for the synchronization not working. I'll try it with a public URL in a couple of days.

[tezukzai]

@mayjs did this work for you in the end?

[mayjs]

@tezukzai I've not investigated it further unfortunately, since we've settled with another project management system for our project.

[gerroon]

Does anyone know if this works with GItea at this point?

[xet7]

@gerroon

Please test does it work.

[andresmanelli]

@xet7 @gerroon I don't think this works out-of-the-box with Gitea.

The client should be a generic interface, and call the specific client based on configuration (Gogs, Gitea, ...).

w2g.gogsc.X() => w2g.remote.X()

A new client should be written if their APIs are different: gitea_client.js

[ScrumpyJack]

+1 for gitea integration