It took me a little while to understand the problem because I thought we were talking about the blog image, instead this problem probably affects any file in any description of any Task.

In D25334#9617, @valerio.bozzolan wrote:

1. Probably we can avoid to create a "dummy" DifferentialTestCommitMessageField and just use something like DifferentialSubscribersCommitMessageField in the test case

OK I can reproduce now. I was missing the php-gd extension for some reasons.

Remove blank line

As already said the legacy situation deserved an additional check to me to prevent confusing situations of --stop --start "" wrongly recognized as stopped.

Try now - adding PHABRICATOR_TESTCONFIG_BUILD_STORAGE_FIXTURES has resolved the Database isolation exception in other test cases I've done.

I know, the attached video is beautiful

Originally the image was just set to grayscale using CSS, but now it's also blurred.

About offering hosting services massively, AFAIK Phorge is already ready for multi-configuration. I mean, you can quickly offer multi-hosting of a Phorge from a very single installation, but having completely different and separated environments, based for example on the incoming request (domain).

I'm trying to reproduce this, but in my local installation I do not have any allowed file formats. I also do not remember how to make that list available.

Thanks :) Soft +1 to wait for other thoughts. The test plan works for me.

Thanks. Some tips:

I like changes that have unit tests.

Handle renderFieldValue in DifferentialRevisionIDCommitMessageField as well

What do you suggest as reproduce steps here?

Thanks, I love this minimal change.

I think this is a Good Starter Task...

(I think I'm still interested in continuing some of this discussion, but I'm far behind on reading it already. I might resurrect [parts of] it later...)

It does seem like it is not designed for development use either..

Uhm. Have we any idea about how to unlock this situation?

I don't know if this should be a Feature Requests

The current workaround was to put the Tags in the description. So, adding this feature could cause the Tags to be "somehow shown twice".

ihih I always thought the lack of tags was a feature. So I always manually Tagged also the Description. Thanks for the Task.

In T15525#11410, @valerio.bozzolan wrote:

I would like to mention #diagrams_extension in the Repository description, but I do not have enough permissions.

I would like to mention #diagrams_extension in the Repository description, but I do not have enough permissions.

@speck I think I can see now where we have fundamental differences in our views.

• Is it possible to make Phorge use a different database? Adding SQLite support could greatly reduce complexity and lower the barrier for entry for new developers and allow running Phorge as a standalone app.

Phorge/Phab support a variety of different setups, including support of clustered MySQL/MariaDB databases. Moving to SQLite would be a large undertaking and would not support clustering/replication without major overhauls. For a move like this I can only conceive of many downsides and no benefits.

Thanks for your replies!

This task is mostly done now that the repository is present and someone made an initial release of Diagram.

It all comes from the fact that PHP was designed for a web 1.0

I don't follow this logic.

And you can manage Diagrams (Extension), which has access to manage the repo.

We don't really have a concrete flow setup.
I'll file a task and have you fill some details...

I'm ready to publish a first version, but I don't understand how to publish it under Phactory?
Do I need to publish on Github first ?

I think the current actionable steps we can take are:

Also, I don't know for sure, but I don't believe the technical issues had a serious effect on Phacility's shutdown - I believe it was the business of trying to compete with GitHub in the low end, and with Phabricator on the high-end - Phabricator/Phorge is at its best when it's being managed in-house, with customizations for integration with the rest of the business tools. Using it as a sealed product is missing half the fun.

I'm not sure what is being suggested.

Side note: indeed PHP allows threads and async. For example in the Config page, Phorge executes 6+ git commands in async.

I posted this in a separate thread, but it is definitely related: https://we.phorge.it/T15524

The default case was $this->getFieldValue(), so, returning that as-is.

\o/

Remove earlier changes to DiffusionBrowseTableView