Demo Account

[mottosso]

Hi guys,

I've gotten permission to access a dedicated Pyblish account that we can use to write practical tutorials against. I'm thinking it would contain a demo-project that anyone can publish to, as a means of learning about pyblish-ftrack.

• http://pyblish.ftrackapp.com

We can also use it for testing, by hard-coding the address wherever it needs to have access to the API, assets and shots in a dedicated test-project.

Since I have little to no experience with FTrack, I wanted to ask how you think we could make good use of it?

• Primarily, how should we expose access to users?
• Can we demonstrate with an in-memory plug-in that somehow interacts with the demo account?
• What sort of credentials would it need, and would it make sense to make these credentials open to the public?

[mottosso]

Added a few questions.

[mkolar]

Great stuff.

Primarily, how should we expose access to users?

I'll have a think about how this could be useful. To be honest I kind of expect people who want to use to have their own server, so they wouldn't need it much, But let me think about it a bit

Can we demonstrate with an in-memory plug-in that somehow interacts with the demo account?

This shouldn't be a problem

What sort of credentials would it need, and would it make sense to make these credentials open to the public?

Well. If we wanted users to be able to use it for testing (because there is very little else to do with it), then they would need to know the user name, password, server address and API key to be able to publish to it.

I'd be careful with opening it to the public completely. Technically for some useful testing a studio potentially thinking of using it, would probably want to test it on their server anyways. If they wanted to keep the test to publish account, then I reckon they should just ask you for it and you give them the credentials, so we at least know who can get in.

It would be ideal if there were 2 users created on the account to prevent people trying it out from changing the password for the admin and locking us out

[mottosso]

It would be ideal if there were 2 users created on the account to prevent people trying it out from changing the password for the admin and locking us out

That's sounds like a reasonable idea. I'll set that up now.

If they wanted to keep the test to publish account, then I reckon they should just ask you for it and you give them the credentials, so we at least know who can get in.

That would work, but it would be very limiting.. Ideally, I would like to provide a tutorial, even for those not currently using FTrack but might in the future (maybe thinking about which is better suited for Pyblish?), by way of standalone examples that doesn't require any setup of asking permissions.

Additionally, it would make it that much easier for anyone to mock up an example of what they mean when asking for help. If everyone uses their own server, example's won't be general and thus much less frequent and therefore abstract.

A public username and password, along with a public API key.

Username: xxxx
Password: xxx
APIKey: xxx

It's out. Let's see what we can happen.

[mkolar]

Additionally, it would make it that much easier for anyone to mock up an example of what they mean when asking for help. If everyone uses their own server, example's won't be general and thus much less frequent and therefore abstract.

Very true. Ok let's do it then

[mottosso]

Cool. Could you guide me through setting up a project suitable for running the plug-ins in pyblish-ftrack? Or maybe set one up yourself?

[mkolar]

I just checked the account and we should set certain, probably fairly open permissions on it. Right now 'pyblish' user can't create shots or tasks, neither assign Pyblish user to a task, which they would probably need to in order to test..

In terms of project setup, How about we mimic what type of works is done on 'the deal'. Not for it to be used in magenta, but if people were to have a look at it, it would at least give us some content to put in there.

[mottosso]

I just checked the account and we should set certain, probably fairly open permissions on it.

May I add you as admin?

In terms of project setup, How about we mimic what type of works is done on 'the deal'. Not for it to be used in magenta, but if people were to have a look at it, it would at least give us some content to put in there.

Sounds very good.

[mkolar]

May I add you as admin?

Sure. I'll be a good boy. How is the account working right now actually? Normally you can only add as many people as you have licences of course, but with the demo I'm not sure

[mottosso]

I sent an invite to your GitHub email.

How is the account working right now actually? Normally you can only add as many people as you have licences of course, but with the demo I'm not sure

It says: "License is valid for a total of 50 enabled users, expires 2015-07-31"

[mottosso]

I'm expecting to get the account renewed and to last forever, but I'll need to confirm that. They'll have more incentive if we actually use the account, so let's see if we can make that happen first off all.

[mottosso]

Just spoke with Ftrack (the company) and have removed username and password. They prefer users to come to us and ask for an invite, and I can understand that.

I have a few other options in mind, but for now it would be best if we can narrow down exactly what it is from the demo account in order to full demonstrate the power of Pyblish for FTrack.