Introduce setup_for_cloud #54463
Labels
No Label
legacy module
Modeling
legacy project
Blender Cloud
legacy project
Documentation
legacy project
Infrastructure: blender.org
legacy project
Infrastructure: Websites
legacy project
Modeling
legacy project
Pillar
legacy project
Pillar Framework
Priority::High
Priority::Low
Priority::Normal
Status::Archived
Status::Confirmed
Status::Duplicate
Status::Needs Triage
Status::Resolved
Type::Bug
Type::Design
Type::Report
Type::To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: archive/blender-cloud#54463
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In our quest to decouple Blender Cloud from Pillar, I suggest to:
To further control which node_types are enabled within a project, a setting in the "Edit Project" section could be provided.
Note: this feature comes from the request of enabling HDRI node_types in private Blender Cloud projects. Enabling HDRI has consequences (regarding CORS) and should be discussed in a separate issue.
Added subscribers: @fsiddi, @dr.sybren
Looks good to me!
Would
setup_for_cloud()
be automatically called when someone creates a project while theblender_cloud
extension is loaded?Yes, that's the idea.