Please do *not* use the devserver settings as-is. This will make your install insecure as everybody has access to that secret. You can use it as a basis, but change the secret so that it's totally new and random. The best way to do this is to create a new OAuth Application in the Blender ID admin and use the devserver settings as a template. Then delete the devserver OAuth Application.

I work with @Arthur Toussaint (konfiot1) on this project. I successfully installed Blender ID locally and it seems to work fine. However, I can't figure out how to connect the local instance of blender cloud and blender id: when I click on "sign in" on the local blender cloud page, that redirects me to the blender id login form, but once I'm logged in, the redirection back to the blender cloud won't work, stating that there is an "Invalid client_id parameter value".

Authentification : I can create local accounts using the CLI, but how can I use them and login with them on the web interface ?

Hi, for buerocratic reasons, I'll change this to TODO, and would kindly ask @Sybren A. Stüvel (sybren) to share his wisdom? [I havent been through setting this up here myself...]

Some useful settings for the GA folks: https://support.google.com/analytics/answer/7667196

I agree that at this point a Knowledge Base would be useful (how to sign up, how to check subscription status, how to use add-on, how to set up Flamenco, etc).

Yes, that's the idea.

Looks good to me!

I agree, Blender can easily save a file as JPEG in some temporary location before uploading.

It looks like Pillow does not support EXR images. Therefore we can:

That's exactly what I did yesterday.

• downloaded daily build
• moved whole folder 2.79 from Application Support
• downloaded addon available from cloud, installed

Same error.

What if you move directory /Users/filip/Library/Application Support/Blender/2.79/ away and start blender again, and install the latest cloud addon?

Here it is, just a note when I started now from terminal I was still logged in (by official 2.79b version) and I tried to open cloud from image editor, or should I log out first?

No pressure =)
Let's do also factory startup so your preferences and some addons aren't affecting this:

Thanks for reliance :) but what the hell is "start the build with all debugging options on"? :) Sorry, simple designer on this side of cable.
I would like to help you, but be a bit more descriptive for me, thank you. I will try my best.

Oops, that one level up is correct. Could you start the build with all debugging options on. And then just hit import ssl to python console and post the whole debug output.
Marking this as incomplete for now.

No.
In folder "site-packages" is only "easy_install.py"
Filtering with blender's file browser displayed only this file containing SSL.

That's just as it should. If you go that folder, does it have ssl.py ?

@Philipp Oeser (lichtwerk) yeah, that's ok.

@Arto Kitula (akitula) If you mentioned "translocation" issue - Do you mean "double docking" issue? Because I already moved blender out and in a directory, to "fix" that with mentioned build. But SSL error appeared before and after (double docking) anyway.

@Arto Kitula (akitula) , assigning to you then?

@Sergey Sharybin (sergey) It is possible. I've got script that works, just needs some caring to do neat dmg. I'll push it when ready (next week latest).

@Arto Kitula (akitula), do you think it will be smart idea and possible to sign buildbot binaries? Last time i've tried to sign in a headless mode, codesign gave me error code 0xffffffff...

Buildbot should also be making signed dmg files I think, really the only difference with release builds should be the revision it's built from.

@Sergey Sharybin (sergey) Actually just now realized that this happens because of the application translocator, the very reason we give releases on signed DMG.

@Arto Kitula (akitula), can you reproduce the issue with buildbot builds on your machine?

On my macOS local build, this is working. Might be that buildbot isn't working as it should. svn problem or something like that. @Sergey Sharybin (sergey) ? Or anyone who has access to mac buildbot.

fixed in 79dc5c91f722194c3bc6b97d6575e80084d8d122

Closing this issue as ElasticSearch has been running in production and is doing fine :)

Closing due to inactivity.

This task it too vague and partially related to T53729. We address that first.

By actually using the brain and reading the error, it turns out that that the node referenced in header_node should exist (not be deleted). As a solution, we should make sure that when deleting a node in a project, we also check if it's used in the the project header_node property.

Fixed in 18fe240b931ab8dbd3a8a9fb6760c8b8cdba7ad3 and 90c62664a6713a9330a4fe44f2cfe58124b29ed3.