But I clicked one (1) link to the online book and found a thousand?

Edit: changing your downvote to something else won't change that fact you know

Man, if only someone around here had even if just an inch of self-awareness...

Comments URL: https://news.ycombinator.com/item?id=46374510

Points: 1

# Comments: 0

https://github.com/bctnry/gentle-introduction-to-mercury

I'll write more and finish this book in the future, and I'm definitely writing my response to some of you's replies in the book.

Comments URL: https://news.ycombinator.com/item?id=45386836

Points: 27

# Comments: 8

For the HTTP server and frontend part, this project only relies on `net/http` and `html/template`, both of which are in Golang's standard library. This might not be the best performance-wise but I wish to cut dependencies as much as possible.

If the way the whole project is structured and developed seems weird: this is the first Golang project and first serious backend project I've ever done. Before making Aegis I've only made a few small things with Node.js and have never touched Golang, and during the development a lot of things have been ignored and/or delayed for the sake of "having enough functionalities as quick as possible". At the beginning it was only meant to be a proof that I have what it takes to "learn on the job" (and to learn about Git internals of course) but it gradually snowballed from there.

Currently the major things that have been implemented are as follows:

    + Basic things: tree/file views, commit info, history, diff;
    + Read-only clone by HTTP and read/write access through SSH;
    + Basic issue tracking and pull requests;
    + Namespaces; 
    + Per-namespace and per-repository user access control;
    + Webhooks for external CI/CD (experimental feature; subject to change)
    + Snippets (à la GitHub snippets)
    + And many tiny things:
      + Labels for repositories;
      + UI for Git Blame;
      + UI for directly editing files;
      + 2-factor authentication w/ Email
      + Support for displaying `Co-Authored-By` messages
    + No JavaScript - works all major browsers and a lot of minor ones, including Ladybird and NetSurf.
    + Proper web installer for easy(-er) installation (like the one in WordPress)
    

    + 2FA w/ HOTP/TOTP and passkeys;
    + GitHub Pages-like thingy;
      + This is currently planned to be added as a part of CI...
    + Proper CI;
    + Migration from/to other hosting services;
    + Support for other version control software, e.g. Fossil, Mercurial and SVN
      + And conversion between them (to the degree that's possible).
    + Refactor;
    + Better SSH and HTTP clone/pull/push handling;
    + Maybe properly implement Git functionalities instead of relying on exec.Command?

Feedback & bug/security reports are greatly appreciated.

Comments URL: https://news.ycombinator.com/item?id=45384801

Points: 3

# Comments: 0

In the last 6 months I've been working on a self-hosted Git server and now I'd say it has reached a stage where I felt comfortable showing it properly.

For the HTTP server and frontend part, this project only relies on `net/http` and `html/template`, both of which are in Golang's standard library. This might not be the best performance-wise but I wish to cut dependencies as much as possible.

If the way the whole project is structured and developed seems weird: this is the first Golang project and first serious backend project I've ever done. Before making Aegis I've only made a few small things with Node.js and have never touched Golang, and during the development a lot of things have been ignored and/or delayed for the sake of "having enough functionalities as quick as possible". At the beginning it was only meant to be a proof that I have what it takes to "learn on the job" (and to learn about Git internals of course) but it gradually snowballed from there.

Currently the major things that have been implemented are as follows:

    + Basic things: tree/file views, commit info, history, diff;
    + Read-only clone by HTTP and read/write access through SSH;
    + Basic issue tracking and pull requests;
    + Namespaces; 
    + Per-namespace and per-repository user access control;
    + Webhooks for external CI/CD (experimental feature; subject to change)
    + Snippets (à la GitHub snippets)
    + And many tiny things:
      + Labels for repositories;
      + UI for Git Blame;
      + UI for directly editing files;
      + 2-factor authentication w/ Email
      + Support for displaying `Co-Authored-By` messages
    + No JavaScript - works all major browsers and a lot of minor ones, including Ladybird and NetSurf.
    + Proper web installer for easy(-er) installation (like the one in WordPress)
    

    + 2FA w/ HOTP/TOTP and passkeys;
    + GitHub Pages-like thingy;
      + This is currently planned to be added as a part of CI...
    + Proper CI;
    + Migration from/to other hosting services;
    + Support for other version control software, e.g. Fossil, Mercurial and SVN
      + And conversion between them (to the degree that's possible).
    + Refactor;
    + Better SSH and HTTP clone/pull/push handling;
    + Maybe properly implement Git functionalities instead of relying on exec.Command?

I have set up a demo server at https://aegis-demo.sebastian.graphics if you wish to see it in action. This server is hosted on a small VPS I've rented from DigitalOcean (not sponsored), which I'll be taking down in about two weeks. It will be configured with the most basic settings possible (i.e. basically SQLite for everything). I'll leave no restrictions on user activities, but please be nice...

Feedback & bug/security reports are greatly appreciated.

Comments URL: https://news.ycombinator.com/item?id=45365940

Points: 3

# Comments: 0

i had an old laptop that runs just fine (albeit with a tiny bit of fiddling). you're free not to believe me though, it's your opinion after all.

> requires us to pretend that it's in the same class as those other OSes?

lmfao, did they ever?

shut up and get your shit together.