You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
Please describe the feature you have in mind and explain what the current shortcomings are?
There is a room for some improvements when setting up local AYON instance without actually using boostrap process. Bootstrap provides you with already build AYON Launcher, dependency package and set of addons so you don't have to do all of it manually.
So when you setup the instance, you need to do several obvious things in specific order:
build ayon-launcher and upload it
create addons from openpype and upload them
create bundle and set all necessary addon versions and installer
create dependency package for the bundle and upload it and set it for the bundle
When you do all those steps, you can run AYON Launcher, but you'll quickly find that there are still few critical things missing.
ayon-third-party addon
this addon provides ffmpeg and OpenImageIO tools. You'll find out that it is missing indirectly, most likely when you'll try publish some image data and Extract Review plugin will crash on missing ffmpeg probe.
Here lies first point of improvement - errors rising from missing ffmpeg and OIIO components should suggest that you are probably missing ayon-third-party addon. Maybe even validator that validates that would be in order.
ayon-ocio
another addon that is needed whenever you turn on Color Management in AYON settings. When missing, this result in error directly when launching DCC from the Tray, stating that OCIO configs cannot be found (but not mentioning the addon at all)
How would you imagine the implementation of the feature?
I understand that when you skip bootstrapping, you are taking all technical responsibility on yourself, but there should be at least hints in resulting errors about what might be wrong. This needs to be documented obviously too.
Are there any labels you wish to add?
I have added the relevant labels to the enhancement request.
I think this is more about documentation and cleanup of dependencies than anything else. If ayon-core gets a dependency on third party libraries and ocio, that should be hint enough + noting in the docs what is the actually minimal installation.
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
There is a room for some improvements when setting up local AYON instance without actually using boostrap process. Bootstrap provides you with already build AYON Launcher, dependency package and set of addons so you don't have to do all of it manually.
So when you setup the instance, you need to do several obvious things in specific order:
When you do all those steps, you can run AYON Launcher, but you'll quickly find that there are still few critical things missing.
ayon-third-party addon
this addon provides ffmpeg and OpenImageIO tools. You'll find out that it is missing indirectly, most likely when you'll try publish some image data and Extract Review plugin will crash on missing ffmpeg probe.
Here lies first point of improvement - errors rising from missing ffmpeg and OIIO components should suggest that you are probably missing ayon-third-party addon. Maybe even validator that validates that would be in order.
ayon-ocio
another addon that is needed whenever you turn on Color Management in AYON settings. When missing, this result in error directly when launching DCC from the Tray, stating that OCIO configs cannot be found (but not mentioning the addon at all)
How would you imagine the implementation of the feature?
I understand that when you skip bootstrapping, you are taking all technical responsibility on yourself, but there should be at least hints in resulting errors about what might be wrong. This needs to be documented obviously too.
Are there any labels you wish to add?
Describe alternatives you've considered:
No response
Additional context:
No response
[cuID:OP-7605]
The text was updated successfully, but these errors were encountered: