I've re-applied this patch and uploaded with arc diff, just to normalize it.

Bear with me here, because Javeline (like all js frameworks) is confusing to me.

@kwisatz I'll try to review the diff this week, and that will probably get to master/stable soon...

As in E14, this is really important for protecting us and contributors.

In T15026#3074, @jeremy.norris wrote:

Wouldn't it just be easier for users if the current Phacility/stable was merged into Phorge/stable, thus avoiding the need to issue git reset --hard?

we've decided to add git reset --hard to the instructions to avoid the merges and simplify the stable issue, avoiding the merge from multiple branches.

I'll go over this to see if there's anything left to do.

What if you upgrade a heavily modified (forked) Phabricator to the vanilla Phorge?

ah, I see the error now.
yes, that's a typo - it was carried over from an earlier version of the document.
in phase 5, only node-modules should be removed, not the package files.
thank you for reporting, and sorry I was being harsh - I forgot I split this section and only looked at the primary blob of commands.

@kwisatz - did you actually try to follow the instructions and ran into a problem, or are you just speculating?

I just tried it here, and it didn't require any auth. maybe something was wrong with our setup at the time?

We've made it to y-combinator, so I think that counts.

Fixed and deployed.

I think we can close this now.

Why do we run npm install when we have previously deleted the package.json file from that directory?

thanks - not technically a dupe, because there's no ticket, but D25050 would fix those.

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

Done - deleted phabricator books.

I've updated the guide with @jeremy.norris's Aphlict instructions, and also a section about configurations we might change later.

the Aphlict change sounds simple enough to just add to the migration guide - it's going to happen at the same time for basically everyone anyway.

re: stable, I'm not sure how the commits actually relate between the now 4 branches.
I considered adding git reset --hard for stable, but I was afraid users will lose local changes.
So you have a suggestion on how to fix the guide for stable?

In T15046#2789, @Matthew wrote:

need to create a username/password passphrase credential with creds for a GitHub account that has write access to the GitHub repos, and set it in the diffusion uris.

I was hoping that wouldn't be the case. I'll create a credential against my account, since it's currently impossible to create GitHub account keys against an orginization.

In T15046#2762, @jeremy.norris wrote:

We've created https://github.com/phorgeit and started configuring it to mirror the repos.

From reading the git code, looks like there is a flag to allow this feature - uploadpack.allowReachableSHA1InWant, though I'll need to check that it actually works.

From a quick googling, it looks like this isn't a server configuration, but most likely the commit you're looking for just isn't in the remote.
Why are you using this command? Are you using submodules for deployment?

We've picked up an updated version of the pem at https://secure.phabricator.com/D21739 - it's not the latest, but is it recent enough?

I've written https://we.phorge.it/w/installation_and_setup/update_from_phabricator/, and I think it's basically ready for simple case (and considering we're still compatible with Phabricator in all technical aspects).

I think we're done here too? E13.

I've cowboy-merged this last week. Not sure why all these commits decided they are part of this task though?

I've tried locally with ./bin/remove , and it appears to work. To get the phid, I've visited the page and used "Actions -> Advanced -> View Handle" - I don't have this action available here.

I've started the a draft for the Going Public announcement - {Blog Post: Going Public} - please chime in with comments...

In T15012#2679, @MacFan4000 wrote:

We should also generate the arcanist docs.

I've re-generated the docs, and now we have two copies:

(Regarding the original task description:)

In T15110#2655, @avivey wrote:

I'll try to force the GC to run, maybe this will delete them.

I'll try to force the GC to run, maybe this will delete them.

• remove favicon, update css in php

Favicons are somehow cached server side:
<link rel="icon" id="favicon" href="http://localhost.localhost:8080/file/data/jvpvboup37hwjgpn3viv/PHID-FILE-xhmdncm6ydmubbkrfdj4/favicon" />

I didn't want to do this, but I'm actually going to test this change.

celerify

looks like the favicon doesn't actually work :/