Um 10:04 Uhr am 30.09.20 schrieb Sven Hartge:
> On 30.09.20 09:57, Kern Sibbald wrote:
>
> > Oh, there seem to be plenty of articles about self-hosting gitea,
> > so you can ignore my request -- however, if you have some special
> > tips, I would appreciate hearing them.
>
> It really is quite s
On 30.09.20 09:53, Kern Sibbald wrote:
> Even if I resolve that problem, I am not 100% sure that I want to keep
> it on github, because
> the repo is already on bacula.org, so having one more place to push it
> is just extra work.
You can configure the Github repository to be a read-only mirror o
On 30.09.20 09:57, Kern Sibbald wrote:
> Oh, there seem to be plenty of articles about self-hosting gitea,
> so you can ignore my request -- however, if you have some special
> tips, I would appreciate hearing them.
It really is quite straight-forward. Configuring the ini-file, starting
the servi
Hello again,
Oh, there seem to be plenty of articles about self-hosting gitea,
so you can ignore my request -- however, if you have some special
tips, I would appreciate hearing them.
Best regards,
Kern
On 9/30/20 9:55 AM, Kern Sibbald wrote:
Hello Sven,
Can you tell me where I can find info
Hello Sven,
Can you tell me where I can find info on creating a self-hosted
Gitea instance?
Thanks,
Kern
On 9/29/20 5:02 PM, Sven Hartge wrote:
On 29.09.20 16:54, Wanderlei Huttel wrote:
Have you think about migrate bacula community source code to github
instead using an git page exlusive f
Hello Wanderlei,
I took a look at it, but I no longer seem to have the password for
the bacula account.
Even if I resolve that problem, I am not 100% sure that I want to
keep it on github, because
the repo is already on bacula.org, so having one more place
On 29.09.20 16:54, Wanderlei Huttel wrote:
> Have you think about migrate bacula community source code to github
> instead using an git page exlusive from Bacula?
Or GitLab, if Github is too much Microsoft.
Or switch to an self-hosted Gitea instance, like I do for my private
projects (and inter
Hello Kern
Have you think about migrate bacula community source code to github
instead using an git page exlusive from Bacula?
Best regards
*Wanderlei Hüttel*
Em ter., 29 de set. de 2020 às 11:29, Kern Sibbald
escreveu:
> Hello Sven,
>
> Thanks for the lesson in debugging git transport. I
Hello Sven,
Thanks for the lesson in debugging git transport. I didn't know how to
do that. This
helped me find the problem, which was not particularly easy to fix, but
I think I
have not corrected the bacula.org git web page as well as the clone of
both the
docs and libs3.
There still is
Um 19:49 Uhr am 28.09.20 schrieb Kern Sibbald:
> Can you tell me why the version at xdocs.git works and
> the one at docs.git does not work. Note: the one at xdocs.git
> was deleted a few days ago by me since it was out of date.
>
> I believe that I have now fixed the web interface to the three
Hello Carsten,
Can you tell me why the version at xdocs.git works and
the one at docs.git does not work. Note: the one at xdocs.git
was deleted a few days ago by me since it was out of date.
I believe that I have now fixed the web interface to the three
repos (bacula.git, docs.git, and libs3.gi
Hi
Sven Hartge writes:
> I have both the source and the docs GIT cloned to my workstation and the
> docs remoted stopped working some time ago:
I can confirm that the docs repository worked, my clone's last commit is
2020-06-09 17:15 +0200 Kern Sibbald o [Branch-9.6]
{origin/Branch-
On 25.09.20 23:35, Kern Sibbald wrote:
> Since quite some time, there has been a problem with cgit on
> bacula.org. The only repo that it properly handles is bacula.git.
> The two other repos libs3.git and docs.git do not work. I have spent
> a lot of time on this problem, but have not yet solve
Hello Carsten,
Since quite some time, there has been a problem with cgit on
bacula.org. The only repo
that it properly handles is bacula.git. The two other repos libs3.git
and docs.git do not work.
I have spent a lot of time on this problem, but have not yet solved it.
Note: docs has been
o
14 matches
Mail list logo