Hi guys, current my phabricator user is local register users, if I add openldap to authentication, can I combine the current users with ldap users? like current there is a users named yushanzhi and email is firstname.lastname@example.org, and the new ldap users is shanzhi.yu, email also be email@example.com;
If you believe you've found a bug in Phabricator, please file a report with version information and reproduction steps following the guidelines in Contributing Bug Reports.
I can not reproduce the issue you describe (self-hosted repositories sending load "through the roof"). Here's load for secure001.phabricator.com over the last week -- note that it never rises above 15%. Beyond self-hosting a number of repositories, we also serve 500K web requests per day per host in this service cluster:
@epriestley At this stage, I don't know if it's a bug or a feature. Oddly enough, CPU usage is hardly noticeable, but every time a repository update happens, 10 min load averages spikes to 10+. So I guess my question becomes: if, for self-hosted repositories, an update happens for every push, why are there additional automatic updates?
We are hosting phabricator ourselves. The site path would be the domain name, my mistake on that term. So once I changed as much of the security settings that I could find, I am not longer able to clone one of the two repositories. It was both of them, but somehow one is now working fine with no changes.
I've never managed to turn bundle2 off completely. Tried tinkering with the server *and* client side hgrc, to no avail. And downgrading, well, I've heard of security issues but haven't investigated them myself. Anything older than 3.8 is just not available on Gentoo for example, which usually means it isn't deemed safe enough :/
@LeCoyote - I'm pretty sure the security issues are if you use an older of mercurial for hosting the service. When I use 3.4 it's only on the client to push to the server (running 3.8+). All I did was download the source from mercurial-scm and run make local (it's in the README). It results in a standalone binary that I use only for pushing changes to phabricator services. It's the only way I've found to not run into bundle2 issues.