Re: [DNG] Living Dangerously (was: Review of documentation needed)
On Thu, 23 Sep 2021 17:16:21 + g4sra via Dng wrote: > A rookie sysadmin mistake is to take backups but never ever do a test > restore to ensure they are OK. Can confirm. I had a backup persistency file which felt "old" when I tried using it. Backups seemed to be going impressively fast; suspiciously fast. I finally figured out that it wasn't because it was a huge file that was being skipped, but that it wasn't ever being backed up / overwritten in the first place. Of course its size wouldn't change, but apparently a persistency file doesn't get its modification time changed when it's written-within. I never would have guessed.. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] devuan gitea broken?
On Fri, 24 Sep 2021 09:57:59 +1000 Ralph Ronnquist via Dng wrote: > This one turned out to be that someone (aka me) had mistakenly raised a > blanket traffic blockage as a misdirected response to an apparent DoS > effect via gitea accesses. Things should be better now, at least until I > have another go at dealing with the same problem. > > Ralph. Hi, whatever you did it fixed the web interface. It is speedy now, just loading files in the editor is still a little slow but acceptable. Thanks for your time and effort. Ciao, Tito > On Thu, 23 Sep 2021 21:42:41 +0200 > tito via Dng wrote: > > > On Wed, 22 Sep 2021 14:54:54 +0200 > > tito via Dng wrote: > > > > > Hi, > > > is there any problem with devuan's gitea web interface? > > > It loads so slowly that it is impossible to work with it. > > > My connectivity seems ok as all other sites work as expected. > > > > > > Ciao, > > > Tito > > > > > > > Hi, > > just wanted to tell that the gitea problem has not improved yet. > > Opening files is slow but editing them is impossible. > > I'm still waiting after 6 min that the file loads in the web editing > > interface. > > It used to work flawlessly last time I used it so please whatever > > was changed revert it. > > Still after 8.21 mins no file loaded. > > > > Ciao, > > Tito > > > > ___ > > Dng mailing list > > Dng@lists.dyne.org > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] devuan gitea broken?
On Fri, 24 Sep 2021 21:39:01 +0200 tito wrote: > On Fri, 24 Sep 2021 09:57:59 +1000 > Ralph Ronnquist via Dng wrote: > > > This one turned out to be that someone (aka me) had mistakenly > > raised a blanket traffic blockage as a misdirected response to an > > apparent DoS effect via gitea accesses. Things should be better > > now, at least until I have another go at dealing with the same > > problem. > > > > Ralph. > > Hi, > whatever you did it fixed the web interface. > It is speedy now, just loading files in the > editor is still a little slow but acceptable. > > Thanks for your time and effort. Yeah; if I don't have things to do I create some :) Btw the favoured way to work with git, both generally and also for Devuan's git store, is to clone the project into a workspace on your own machine to edit and commit locally, and then push changes back. Apart from being slow, editing via the repository browser is error prone in many ways, especially because it causes a very refined commit history which reduces its usefulness. In fact, if you deep dive into the ontological structure that underpins the notion of version control for collaborative authoring you're likely to arrive at and take a position to the very question whether editing while browsing is or is not a contrary idea. I'd say "is". Ralph. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] devuan gitea broken?
On Sat, 25 Sep 2021 08:45:50 +1000 Ralph Ronnquist via Dng wrote: > On Fri, 24 Sep 2021 21:39:01 +0200 > tito wrote: > > > On Fri, 24 Sep 2021 09:57:59 +1000 > > Ralph Ronnquist via Dng wrote: > > > > > This one turned out to be that someone (aka me) had mistakenly > > > raised a blanket traffic blockage as a misdirected response to an > > > apparent DoS effect via gitea accesses. Things should be better > > > now, at least until I have another go at dealing with the same > > > problem. > > > > > > Ralph. > > > > Hi, > > whatever you did it fixed the web interface. > > It is speedy now, just loading files in the > > editor is still a little slow but acceptable. > > > > Thanks for your time and effort. > > Yeah; if I don't have things to do I create some :) > > Btw the favoured way to work with git, both generally and also > for Devuan's git store, is to clone the project into a workspace on your > own machine to edit and commit locally, and then push changes back. > Apart from being slow, editing via the repository browser is error prone > in many ways, especially because it causes a very refined commit history > which reduces its usefulness. > > In fact, if you deep dive into the ontological structure that underpins > the notion of version control for collaborative authoring you're likely > to arrive at and take a position to the very question whether editing > while browsing is or is not a contrary idea. I'd say "is". > > Ralph. Hi, Yes, but I don't have the time to learn the git-fu at the moment. I work on my local cloned tree and when I'm ready or to tired I just delete the current git version in the editing window and copy my new version. This way I get a diff in a simple and fast way add some commit notes, hit commit and I'm done and can drink a beer and go to sleep. I agree with you that this is not the most elegant way to use git but it works for me. Ciao and keep up the good work, Tito ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
