Re: Broken GitWeb

If someone wants to patch it so it doesn't eat up 100% cpu on all cores 
we could potentially put it back online. I also worry how it shells out 
to the command line git a bit too much. When the web server starts 
hitting 100 load average for extended periods I tend to notice.

As I stands now, I don't feel it is a safe tool to put up on a public 
website. Way too easy to DDOS with it.

On 7/18/2024 12:14 PM, Elizabeth Figura wrote:
> On Thursday, 18 July 2024 12:01:59 CDT Gabriel Ivăncescu wrote:
>> Unfortunately, github has also been increasingly reliant on javascript
>> and became very sluggish on less mainstream browsers, but it's still
>> better than gitlab's UI.
>>
>> gitweb was just on another level of convenience for me. Sad moment.
> 
> Yeah, I'm also sad about this. gitweb was fast, it didn't have visual clutter, it was able to render several times as many commits as gitlab or github, it had a lot more intuitive UI and more links in convenient places...
> 
> Brendan suggested this off-list, but if gitweb is badly optimized on the server side, could we try cgit instead? It has a similarly nice experience to gitweb and might be more efficient.
> 
> --Zeb
> 
> 
>   
> 

-- 
CodeWeavers, Inc.
🐉 Jeremy Newman ⛭ Director of IT
──────────────────────────────────────────────────────
   📧  [email protected]
   🌐  https://www.codeweavers.com/about/people/jnewman