Phorge

Public

• Join Room

So, are we able to install Phorge from the stable branch, or should we just install Phabricator for now and migrate to Phorge after the first release?

I'd say you could if you want to. But there has not yet been an official release of phorge, and so there might be things like inconsistent branding.

Right, I guess I'm just gonna work on deploying Phab, and then migrate to Phorge when released.

Hello :)

Do you mean like a docker container for phorge? I had a docker container for phabricator on dockerhub and jist recently switched it to phorge. https://github.com/cooperspencer/phorge

@buddyspencer how's this one published? there are so many phabricator images on the Hub (including one by Bitnami)

https://hub.docker.com/repository/docker/buddyspencer/phorge

Oh, you have ARM builds?

Yeah, compiling them on my pi

That's awesome. Here I am, writing my own dockerfiles because my K8s cluster runs exclusively ARM. 😄

Could you merge it with the phorge repository with the associated file for development please :) ?

@G Docker support within Phabricator was pretty much nonexistent.

Yes, it looks good :)

I mean, even the images under phabricator state they're unofficial.

It feels weird to me, that the official repository, do not have the necessary files to start a docker based development environment.

And whether there will be a place for that in the future is up to the maintainers.

Ah, I understand. I was more thinking for developers, not for production, as in if it is long and challenging to start to contribute, little people will do. If anybody can start to fiddle with two command lines, it will ease the process :)

Speaking of clusters, I wrote up T15057 specifically to at least spark discussion about better cluster support for Almanac/Drydock/Harbormaster - anyone can create tasks in Maniphest, and it's probably the best place to start a serious discussion on the topic of general Docker/containers support.

@golyalpha glad that it might be of help to someone beside me 😁

@buddyspencer I mean, I'll have to have a look at your thing, see if it's worth it abandoning my work mid-way or if I'd just have to do so many things to make it work that I'm just better off finishing what I started.

Oh, yes, there are a lot of things to improve for sure. For now, I just want to get comfortable with the code base, and fix a few bugs that irritate me daily.

Sure, sure. Not sure if it fits your needs. It was enough for me, but that might not be enough for everyone

It is unfortunate that with the current state of linux containers (specifically that CPU architectures are a problem, and most images don't crossbuild), having a functional docker build that's versatile enough on the configuration side isn't always enough to prevent that.

@buddyspencer I am sure it will fits my needs 🙏

Yeah, as a development container it definitely looks nice.

I guess the only small change would be to mound directly the local folder in the docker-compose.yml instead of the `/var/repo.

I'm willing to host any main website for "Phorge" on my Linode account for free. Just trying to contribute in anyway that I can. I'm also a Security Engineer so if you have any need for a Security Engineer let me know.

Awesome :D

Yup trying to help in whatever way I can.

Something some folks might be interested in: https://data.releng.team/dev/-/ddd/dashboard/project-metrics

If you try the above link, try typing something like "platform" or "kanban" into the project search, then select a project and select a date range to see what it's all about.

Heya everyone - I didn't notice this chatroom also being used

It looks like secure.phabricator.com was updated/fixed - things related to https://secure.phabricator.com/T13630

Verification email receive i should've been but hadn't. Fix this issue you must.

daemons died, they've been restarted

hi there

we are using phab for quite some time for internal support ticket tracking and escaltion to to tech level sup. i have added some more stuff to phab making it more useable as CRM tool. waiting for the email confirmation to get involed

Which email confirmation are you awaiting?

I think they mean the Email verification... email.

Hi Phorge team, I'm having trouble verifying my email address. I get a message saying "Primary Email Unverified: Your primary email address is unverified. You will not be able to receive email until you verify it.", and when I click on the verify button on the email section of my profile settings I get a modal that asks "Send another copy of the verification email to $EMAIL?". Clicking "Send Email" on that modal doesn't seem to send me a verification email.

Sorry, looks like I had some mail config issues. Resolved now!

Do you happen to be using an Outlook email address? We’ve had issues with Outlook emails.

Not Outlook, but self-managed. PEBCAK error on my side.

There looks to be a 502 on the repository pages:

https://we.phorge.it/source/phorge/
https://we.phorge.it/source/arcanist/

Can still clone though

See T15090: CVE-2022-24765 - Multi-user Git Privilege Escalation

Ah thanks, got it ... So I have a branch locally called merging-upstream that I believe contains all the changes... What's a way to push it up?

I'm not sure actually... I believe the master branch is protected against direct pushes by H7 Guard Phorge Repo with Blessed Committers. @speck do you have any insight you can provide, as you did configure this rule?

Created this task to address: T15094: Catch up the master branch to upstream

I think the idea was to separate contributors allowing to land changes but not in the master/stable branches, allowing for further curation of the production branches

@dcog you also will need to update arcanist I think

@roguelazer Yep, I actually have that done as well... but will need a different strategy for presenting the changes for review and testing

Everytime I try to access a diffusion repo on this install I get 502 errors

Hey @MacFan4000, I raised a task (T15093: 502 Bad Gateway error when attempting to view repo info) which was closed in favour of T15090: CVE-2022-24765 - Multi-user Git Privilege Escalation. Seems related to underlying git config on Phorge's server.

FYI, after restarting the server on June 14, I forgot to restart the daemons, so there were no notifications and no feed updates until now.