Hi,
Phabricator is now running on https://phabricator.wmflabs.org/. If you haven't before indicated that you trust wmflabs.org certificates, your browser may warn you that the site's identity is untrusted. You should add an exception.
You should be able to log in using your WMF Google Apps credentials. If you prefer to have a separate username and password, please contact Steven Walling (swalling@wikimedia.org) who has volunteered to help manage accounts during the trial run.
Be aware that this is a trial run and that the setup hasn't been thoroughly tested for security vulnerabilities. So the usual caveats apply: don't put anything in that is dear to you or private. Other than that, go nuts.
Mark Traceur will administer this machine -- please direct questions to him (but also be prepared to offer help). :)
Thanks to Ryan and Jeremy for their help with configuring this machine.
-- Ori Livneh ori@wikimedia.org
On Wed, Aug 8, 2012 at 2:36 PM, Ori Livneh ori@wikimedia.org wrote:
You should be able to log in using your WMF Google Apps credentials. If you prefer to have a separate username and password, please contact Steven Walling (swalling@wikimedia.org) who has volunteered to help manage accounts during the trial run.
I'm also StevenW on the usual freenode channels.
On Wed, Aug 8, 2012 at 2:36 PM, Ori Livneh ori@wikimedia.org wrote:
Mark Traceur will administer this machine -- please direct questions to him (but also be prepared to offer help). :)
Is it possible to set it up in such a way that all read operations can be performed without logging in, or does Phabricator currently lack that configuration option?
AFAIK, you can expose activity feeds to non-logged-in users, but other views require authentication. You can have an open registration policy. Not sure there's a complete interface available to anonymous users, though. I'll check the docs later and make sure.
-- Ori Livneh ori@wikimedia.org
On Wednesday, August 8, 2012 at 3:26 PM, Erik Moeller wrote:
On Wed, Aug 8, 2012 at 2:36 PM, Ori Livneh <ori@wikimedia.org (mailto:ori@wikimedia.org)> wrote:
Mark Traceur will administer this machine -- please direct questions to him (but also be prepared to offer help). :)
Is it possible to set it up in such a way that all read operations can be performed without logging in, or does Phabricator currently lack that configuration option? -- Erik Möller VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org (mailto:Wikitech-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/wikitech-l
All right, I think we need to seriously consider this problem right now:
There's seemingly no way to disable required-login in the conf files. We need people to be allowed into our code review system, and right now, they need to either have a Google account (nasty) or ask someone on the machine for a login (slow). That's pretty much the state of things for *committing* right now, in Gerrit, but people should be able to see changesets and the discussions thereof without logging in.
I tried setting "policy.allow-public" to true, but that did nothing obvious. The docs in default.conf say something about "setting objects to be publicly accessible", but there are no extra configuration settings in the policy group, and no mention of "public" in either the docs or the default.conf example.
Can anyone help me figure this one out?
On Fri, Aug 10, 2012 at 2:29 PM, Mark Holmquist marktraceur@riseup.net wrote:
All right, I think we need to seriously consider this problem right now:
There's seemingly no way to disable required-login in the conf files. We need people to be allowed into our code review system, and right now, they need to either have a Google account (nasty) or ask someone on the machine for a login (slow). That's pretty much the state of things for *committing* right now, in Gerrit, but people should be able to see changesets and the discussions thereof without logging in.
I tried setting "policy.allow-public" to true, but that did nothing obvious. The docs in default.conf say something about "setting objects to be publicly accessible", but there are no extra configuration settings in the policy group, and no mention of "public" in either the docs or the default.conf example.
Can anyone help me figure this one out?
This is just not a current feature at all AIUI. the upstream instance has a demo:demo account which we could set up on ours too but the demo account has write permissions.
This is filed already as https://secure.phabricator.com/T603
See also https://secure.phabricator.com/project/view/404/
-Jeremy
wikitech-l@lists.wikimedia.org