I think this is complete.

I'm going to call this done, since we have a stable dashboard set up now.

Looks good to me!

Looks good to me.

Address code review comments

In D25009#285, @20after4 wrote:

Shouldn't we also think about changing the name of arcanist or does it make sense to have a fork with the same name?

Both revisions are landed. We just need a pull on the upstream install to regenerate the documentation. @chris could you do the pull so I don’t break anything?

Alternatively, we could include a one-time migration step that sets the default storage namespace to the database as part of the storage upgrade step… this would ideally be silent.

Fix a link that will break once we regenerate the documentation.

I created a change log just so we could begin documenting changes as they happen.

Make changes based on code review comments.

In D25006#216, @Ekubischta wrote:

My only concern here is that technically this introduces issues for any user install that already contains an untracked package support/aphlict/server/package-lock.json

I feel that this needs to be addressed in "release notes" or "upgrade notes" somewhere - However, we do not yet have this process defined?

This was handled by Phacility/Phabricator with their changelog and process for promoting stable

In T15012#423, @speck wrote:

For Diviner I don't think that's something we can do since I'm guessing all the book content is effectively static.

In T15000#408, @speck wrote:

It looks like Diviner was used to generate documentation however a lot of the documentation still refers to "Phabricator". We'll probably want a separate task just for reviewing and updating all the documentation to make sure it's appropriate.

Btw where is the source for the diviner books and how does it get generated?

In T15008#278, @avivey wrote:

I think we want an Application in an Extension...

Do we want to make this an application or an extension? I'd lean toward the latter, it might be a good one to seed our new extension library with...

Sorry about the spam... I've gone ahead and made all the component projects of Phorge public. Is there anything else we need to do here?