No, we do not see repeated activity on the commit page. Just a single 'accepted commit'.

Here's the immediate trace:

(Looking into this now...)

If you visit one of the commit pages, do you see the 'somebody accept a commit' message duplicated / other duplicated activity?

Let us know if you weren't able to resolve this following @epriestley's instructions. Assuming things worked out for now... Thanks!

In Phacility, invite members from the instance administration panel instead of from the instance itself:

@epriestley I think they esentially want this: https://help.github.com/articles/setting-your-organization-s-billing-email/

(If "finance department" is approximately "a single human with an existing account", you can just add them to the payment account to achieve the same effect -- but they'll have total control over the instance.)

How do you currently handle this with other services? I don't recall seeing a way to CC an arbitrary address in other SAAS products, but maybe I just haven't looked carefully enough.

Okay, it works now………

Cool. D12973 adjusts the documentation to recommend the relevant setting in the general case. Thanks for the report, and let us know if you run into anything else.

Yes, works great now. Thanks for the prompt response!!

This seems to be working correctly now in my test case. Can you verify that things are fixed for you?

Thanks!

I've deployed a configuration change which I believe will fix this, but it affects AWS CloudFront so it will take a few minutes to propagate. Once it deploys, I'll test if it resolved the issue.

Thanks, I'll take a look at this.

This moved into an email thread so I'm going to close this out, but let us know if we can help with anything else.

Thanks. We'll get in touch after we review this internally.

https://admin.phacility.com/book/phacility/article/importing/ has more information on the process. https://admin.phacility.com/book/phacility/article/limitations/ explains some of the current limitations over a private deployment.

We do these still by hand to ensure quality of the process. @epriestley handles this. You can contact us directly at contact@phacility.com and we'll work with you directly from there.

I held the update back a little bit because some of the typeahead changes were in flux, but this is now live:

That change adds some general instance administration documentation. It will go out the next time we push the cluster, usually Saturday morning if nothing comes up before then. I'll update this once it's live.

We should organize the documentation better, but here's the relevant part:

Yeah, totally. That sounds like it's in the same direction.

We have a product Nuance that we're kicking around (helpdesk) which would I think be a good value for Phacility. It would enable non-account people to file bugs and get support without a charged account. We haven't put much time into it, but I'd hope it'd at least solve the most common cases like "Sales wants to file bugs, and nothing else, why pay $20 a person for that?"

Yeah, I agree that model is slimey. It's strict trick and sunk cost fallacy instead of progressive value increase. I think segmentation is fine when it leads to opening the ability for more people to receive value... Not when it just tricks people into buying more.

I get the sense many similar products to Phabricator charge for license packs for this very reason. That is, they sell you accounts in packs of 10s or 20s, so if you had 21 people at your company, you'd have to pay for 30 seats. This means there will always be some slack in your seats and you're more incentivized to fill them up with less contributing users, because, why not? I'm not personally a fan of this model, so we're happy to explore other options. But as far as "light" and "heavy" mixtures go, I don't think we have any programmatic means of determining that, and I'm not aware of many SaaS products that do (looking at the nearest competition).

So, let me first walk out my use case a bit further.

We're potentially open to adding limited-access accounts but haven't seen much demand yet (so we aren't sure what they should look like) and there isn't a really a bright line between "limited access" and "full access" that we can identify offhand.

That's a good point and a perfectly workable solution—good call.

@tel, Can't you create some password-protected "guest" account(s) and give out the password(s) to your customers? I'm thinking that exports are too static and would need to be updated every time the wiki sub-tree changes...

This does appear to resolve my immediate needs very nicely. I'll take a look at using this feature later today.

Presuming this is resolved, but let us know if you still have questions.

Just simply allow public and remember that "To view a wiki document, you must also be able to view all of its parents." It works almost out of the box.

Set policy.allow-public to true in your config, which will allow you to use the "Public (No Login Required)" policy setting. You can do this from the Config application on your instance.

Yeah, this is definitely motivated mostly by cowsay, we'd just get dot for free.

I appreciate your concern for safety!

I'm vaguely concerned about installing dot (and cowsay) because it's possible that they include features which can execute arbitrary commands and compromise the security of a host. Mercurial had such a vulnerability recently, see D12112 for some discussion. It is is unlikely that dot or cowsay have such issues, but I suspect neither program (particularly cowsay) was developed with malicious input at the forefront of design considerations, and the more binaries we execute directly, the greater our exposure.

I think this should be fixed now, let me know if you see it again.

Nice find!

Yeah, we'll take a look at improving this. It's definitely not as obvious as it could be. Thanks for the feedback!

Ok, thanks, that works. That was not obvious at all, though, since some work needs to be done on the instance and some on this higher level of admin.phacility.com.

We could also do a better job of leading you to "Invite Members" after an instance is created. There's a lot of stuff on that first screen, but "Invite Members" is probably where almost everyone wants to go either first or second (after visiting the instance to check it out and set things up). We could probably have a hint that displayed on the instance details screen until your instance has at least 2 members without getting in anyone's way.

You need to explicitly add him as a member of your instance. Go to Phacility Home → Instances → (Your Instance) → Invite Members to invite him.