As a developer using YunoHost to self-host my software forge (currently ynh:gitlab, considering switching to ynh:forgejo), I want to configure Weblate to connect to my forge.
Context
Currently the Weblate installer appears to require me to select either github.com or gitlab.com, but I am using yunohost in order to get away from those. It makes me feel this is not for me.
Now I understand from a comment in #60 that it's possible to put in garbage values to get past this and then do a manual configuration.
I would like to enter the config details of my own forge in the weblate setup. The easier the better, but it does not have to be completely done in the GUI. The most important thing in my opinion is to make it clear that the two options currently offered are optional helpers and make it clear that that many other options are possible, even if they require manual config file editing.
Expected behavior
Some possible solutions:
a comprehensive GUI :-) (not really expecting this)
an additional option, "other forge" with sufficient parameters to cover a range of the possible supported forges
an additional option, "neither/none of those, please: I will configure it manually"
a plain text config file editor (having this functionality in the install/config GUI would be useful for many other apps too)
Notes: the Weblate documentation is pretty solid and understandable. Displaying a link directly to this section would also be helpful.
As a developer using YunoHost to self-host my software forge (currently ynh:gitlab, considering switching to ynh:forgejo), I want to configure Weblate to connect to my forge.
Context
Currently the Weblate installer appears to require me to select either github.com or gitlab.com, but I am using yunohost in order to get away from those. It makes me feel this is not for me.
Now I understand from a comment in #60 that it's possible to put in garbage values to get past this and then do a manual configuration.
I would like to enter the config details of my own forge in the weblate setup. The easier the better, but it does not have to be completely done in the GUI. The most important thing in my opinion is to make it clear that the two options currently offered are optional helpers and make it clear that that many other options are possible, even if they require manual config file editing.
Expected behavior
Some possible solutions:
Notes: the Weblate documentation is pretty solid and understandable. Displaying a link directly to this section would also be helpful.