Please squash the changes into the appropriate commits.

this is awesome

The status update that shows a [somewhat] viable sr.ht finally. Really only tested meta, git, and paste while todo, man, and hg works fine [so far] from my tinkering. Local nixpkgs consist of #66401, #65109, and #54425 on top of 2da00ae with a nixops configuration here [1].

In terms of other stuff, the mailing/mail server will probably be the last thing that'll work since I hardly have any experience setting that up. I'll probably just setup the web interfaces for dispatch, lists, and builds while focusing on builds so it'll be completed before I head for the dorms in college.

[1] https://gist.github.com/eadwu/e633df2660b316f3d09974594cb519e5

Then again, setting up a mailserver could be outside the scope of this,

I agree. I also suggest the nixos-mailserver, which I have good experience with (used it only for journalwatch so far).
I would also say that this is out of scope of this package and a user should setup their own webserver for using sourcehut, not the package/service should ship one!

Seems to me all review items have been addressed. Unless there is something fundamentally wrong with this, it'd be nice to finally integrate it.

Rebased onto latest master and built successfully.

Thank you

Bravo! @eadwu thanks for sticking with it.

Yippie!

Thanks @eadwu! This closes #65109, right?

#65109 is an incomplete implementation of an actual sourcehut network (internals, not webserver/mailserver). This PR just included the packages needed for it to function.

Is it possible to run sourcehut with these packages and systemd services until the module in #65109 is merged?
This is what I am trying, but the service doesn't find the dependencies:

  systemd.services.sourcehut-meta = {
      description = "meta.sr.ht website service";
      requires = ["postgresql.service"];
      after = [ "postgresql.service network.target" ];

      environment = let
        penv = pkgs.python.buildEnv.override {
          extraLibs = [ pkgs.sourcehut.metasrht ] ;
        };
      in
      {
              PYTHONPATH = "${penv}/${pkgs.python.sitePackages}";
      };

      serviceConfig = {
        Type = "simple";
        User = "sourcehut";
        Restart = "always";
        ExecStart = ''${pkgs.python38Packages.gunicorn}/bin/gunicorn app.py --chdir ${pkgs.sourcehut.metasrht}/lib/python3.8/site-packages/metasrht -b 127.0.0.1:5000'';
      };
   };

journalctl -u sourcehut-meta.service shows: ModuleNotFoundError: No module named 'metasrht'

meta.sr.ht was implemented to a fully functional state already when the PR was created.

meta.sr.ht was implemented to a fully functional state already when the PR was created.

Can you link me any kind of information or docs on how to actually run it?

I believe a nixops implementation was referred on IRC? And there is the nixops implementation I used locally within nixos-configuration, although it's now moved from sr.ht to github.

There's no difference between the nixops configuration and normal NixOS configuration (just combine it all), nixops is just a easier way to distribute sourcehut across multiple machines (VMs).

Wrong thread to post on though since you're pinging the 20 or so other people by commenting.