With D11419 implemented, is it possible to now allow Herald rules to be triggered on a cron (even a very simple 'daily' option would be good)?

I know you have focussed on the missing background, but I'm not overly fussed about that. But I am surprised that the commit subject shown twice in a row, once truncated inside a table and once not, is anything else but a bug.

I know I didn't retrieve all the info you asked for, so let me know if you want to see anything else or want me to decode the base64 email body.

I've learned some interesting things.

@hach-que Perhaps the terminology isn't really consistent then. When I add a project to an edit, it appears under a heading called "tags". Perhaps the Herald rule should say "tagged with"

It confused at least one person, but I am relatively new to this product.

OK, thanks. Because there is no documentation about what any of these choices mean would you like to make this task a documentation fixing issue?

I thought I tried that too, but perhaps I'm confused between differential and diffusion (such very confusing terminology for people new to phabricator!). I'm making inline comments against the commits, not against code reviews.

This feature is very important to me, so I've been following along. However perhaps I'm missing something and cannot get the new functionality to work as I expect.

OK. I'm not sure how to describe it differently. However if being able to display milestone end dates on the calendar or organise them by date is out of scope of phabricator, please close this task.

Does "Restricted project" now mean that this feature is no longer considered for the open source Phabricator?

Great, thanks guys. Can I recommend a small change in the text then:

Sorry, I'm confused. I read this to mean:

Not quite because I want this to fire for changed files as well as newly added files.

That makes sense. If I have the time I'll look at making a port myself. The nice thing about your "arc upgrade" command is that the macport itself need rarely be upgraded and that command executed as a normal part of the install.

I'm not how "arc upgrade" helps here, since you still need to first install arcanist. Which goes something like this:

I see you merged my arcanist task into this one. That's fine, but note that arcanist is several orders of magnitude easier than a complete configuration of httpd/nginix, a database and all the other things you want to put in place for a full install.

Yeay! Fixed it. So the end result is:

OK, thanks for your help. In the last few minutes I found where the PHP errors logs go (I'm more a Ruby/Java person) and found these logs:

Sure. I can open some firewall rules. But I'll send the URL to you privately if that's OK so every web crawler/hacker in the world doesn't have a go at it.

Woah... as explained in a previous comment I've already done that. Twice now. First I upgraded to master from github (just read up a few comments). Then I dropped all the databases and started again from scratch.

No. That works fine.

Yes, I get the error after I choose the "password" option in /passphrase/create. Same error as when doing the same thing from the diffusion application.

How do I do that differently to what I described above? Is there some other place in the UI I go to?

Can you suggest where I should look? Is this the relevant code:

Note that I get the same result when I create a new credential from this URL:

https

I have upgraded to the current master from the github repository and run
all upgrade scripts. There is no difference in behaviour.