Work related to Phorge, the organization that develops Phorge (the software).
Thu, Feb 15
Mon, Feb 12
Fri, Feb 9
TRUST ME - YOU DON'T WANT TO LISTEN MY ENGLISH :D :D
Nice! Is there a recording of the talk?
Nice, you touched on most of the advantages of Phorge. It really does have some strong competitive advantages.
Hahaha I’m just now seeing this. Thank you for putting together the presentation and giving the talk. I enjoy seeing your excitement!
Thu, Feb 8
Thanks for all the tips <3 <3
Sat, Feb 3
Thu, Feb 1
Jan 26 2024
I was able to recover the layout in PNG at least. Imagine this 3''x2''. Here:
I'M REALLY SORRY FOR WHAT YOU ARE GOING TO SEE - I'M NOT A DESIGNER
One concern that I have is that there isn't really a one-size fits all deployment. A single tiny VM image with the database and web server pre-installed would probably be ideal for evaluating and even for a tiny team's use. Once usage increases beyond a very basic level then users will fairly quickly outgrow a tiny VM and need at least a larger memory, more storage, possibly a separate database node, etc. Migrating from the tiny setup to a more robust setup might not be a fun process and I don't know how much we should encourage people to start out with a setup that won't scale very well for them.
I think there's an app-store style thing for hosted VMs in the big cloud providers
Jan 24 2024
Maybe we can wontfix this, and try other more modern approaches like flatpak. Example:
Jan 22 2024
## Contents - is Phorge good for my Organization? - differences between Phorge and GitLab, GitHub, Launchpad, Mantis, ... - what's new in Phorge (that is not in Phabricator) - practical workflows and pitfalls - how to join the Phorge community - how to propose code patches
Jan 17 2024
Jan 14 2024
As the patch was merged I assume that this issue is resolved. If not, then please reopen - thanks!
Jan 12 2024
I set this to unbreak now just to give extra visibility on the homepage :^)
Jan 11 2024
Noticed a few dangling phacility references in URLs in documentation, which could lead users to grabbing upstream Phabricator versions by mistake:
phorge/src/docs/user/field/xhprof.diviner: $ git clone https://github.com/phacility/xhprof.git phorge/src/docs/user/userguide/arcanist.diviner: some_install_path/ $ git clone https://github.com/phacility/arcanist.git phorge/src/docs/user/userguide/arcanist_quick_start.diviner: somewhere/ $ git clone https://github.com/phacility/arcanist.git
Jan 10 2024
I have some containers I put together for development which could provide a place to start
Jan 9 2024
I do not remember who was developing Docker stuff for this. I've just found again this
OH MY GOD FOR SOME REASONS THEY RE-OPENED OUR PROPOSAL \o/ IT'S HAPPENING!
Dec 20 2023
They have no space at FOSDEM 2024 for Phorge, nor in Collaboration and..., nor in Lightning talks :(
Dec 18 2023
The only trouble with maintaining a separate arcanist package is keeping the version in sync with phorge. Phabricator never followed anything like semantic versioning and there was never really any stable api version to depend on. Perhaps we could think about versioning and release cycles that follow a more predictable major version release cycle with API compatibility guarantees. It is certainly more convenient (for the upstream) to avoid all of that but it offloads quite a bit of burden on anyone trying to use the software.
Phacility was very much against this kind of things, but I actually favor supporting some packages, at least for Arcanist on the big package-managers - if nothing else, it would allow us to make sure the package with the right name is doing the right thing.
Feel free to review, in case:
Unfortunately they have not accepted our proposal in the track Collaboration and Content Management. I've proposed that again as Lightning talk as suggested to me by FOSDEM ex-speakers.
Dec 11 2023
Dec 10 2023
I'm quite sure that somebody of you will join FOSDEM. In case, please join this talk as presenter :)
Dec 8 2023
Unless something broke, this task is now complete.