I'm available to configure an inboud email receiver via a simple IMAP spooler, thanks to this:

Thank you for your work on this, Dan!

(should also include the rHP -> /home/ stuff)

Per discussion during {E9}

This is a direct result of T15090: CVE-2022-24765 - Multi-user Git Privilege Escalation - confirmed in the Nginx error logs:

STDERR
fatal: unsafe repository ('/var/repo/1' is owned by someone else)
To add an exception for this directory, call:

Hmm, possibly depending on how it's hosted? What I saw when that CVE was announced on a local instance and on secure. was like the below screenshot, where the repo page was still visible but file structure and recent commits were b0rked:

Related to T15090: CVE-2022-24765 - Multi-user Git Privilege Escalation perhaps? Revisions are stored in the database that's why they're viewable, but the main repository page requires a call to git.

Closing this task now, to prevent it from turning into a perpetual task.

The choice to not allow administrators to edit profiles is a strange one... at the very least, we should probably upstream Mukunda's patch.

Another one popped up: https://we.phorge.it/p/seo-auckland/

Yeah admittedly what I did was just a hack because I didn't want to implement storage and UI for a new "hidden" boolean flag.

Now that I look at this some more, this isn’t quite done - there are still some components of phorge that are missing projects.

I’ll note here that I’m going to work on creating projects for some of the prototypes that do get used.

In T15001#1011, @MacFan4000 wrote:

In T15001#980, @MacFan4000 wrote:

Just a note that Trusted Contributors can’t self grow beyond admins adding people currently as to add members you need to be able to edit the project. Currently only admins can edit the project.

IMO the edit policy should be set to Project Members. This way it’ll be able to self grow. :)

In T15001#980, @MacFan4000 wrote:

Just a note that Trusted Contributors can’t self grow beyond admins adding people currently as to add members you need to be able to edit the project. Currently only admins can edit the project.

Just a note that Trusted Contributors can’t self grow beyond admins adding people currently as to add members you need to be able to edit the project. Currently only admins can edit the project.

Yea I think it will be easiest to host this on the same server that's running we.phorge.it. If we're able to build it as an extension application for phabricator it can be setup in the same installation and then we can route the web server to host it properly.

I think that the best choice is to keep everything in one place, so create the presentation site on the same infrastructure of we.phorge.it

sorry for late reply. I can start working on it now. Where will be it hosted? Do you have some preference? We can use also my company infrastructure and change DNS record for a 3rd level to point to the IP.

In T15000#888, @MacFan4000 wrote:

And also we perhaps should have an IRC channel such as #phorge on Libera. It would be possible to bridge it to Zulip.

For this phorge instance, I think we should configure auth providers to allow logging in with Github/Google etc.

Per discussion on Zulip.

In T15008#651, @speck wrote:

@jupe yea I figure similar to the Phabricator landing page on https://phacility.com/phabricator/ I think we want a basic static page which showcases the project & features, along with some form of T15010, then points to the other content on this install.

In T15008#619, @deadalnix wrote:

In T15008#573, @jupe wrote:

should we also start working on the content?

Yes. If there is something that is obviously useful and that you know how to do, then please do it. You'll be adding a ton of value.

Definitely -- I believe the idea that @avivey is aiming for is something extending AphrontSite which would serve up this static page/content, then we can update nginx to point phorge.it to that site leaving we.phorge.it to point here. If you'd like to start putting together the content or learning about extending AphrontSite that would be a great help.

@jupe yea I figure similar to the Phabricator landing page on https://phacility.com/phabricator/ I think we want a basic static page which showcases the project & features, along with some form of T15010, then points to the other content on this install.

In T15008#573, @jupe wrote:

should we also start working on the content?