Help with setup

General
1

Hello, I’m trying to setup AYON on my local machine.

My overall goals are to learn about the system so I can begin to help with on the dev side to contribute to AYON, but I’d like to use it so I understand it better first.

I’m using Rocky Linux 9.

I’ve tried with both ynput.cloud, and locally but with the pricing of ynput.cloud and my overall goals, it seems a local server setup is better suited for me.

Issues:

  1. Currently I’ve gotten the local server running, and the app launcher installed (I think correctly). Now I’m getting an error that I do not have a release bundle set as production on my AYON server. I think I understand what this means, but when I go to my locally running server instance and go to try to create a new bundle, nothing is there. I think I might be missing this( Testing AYON pipeline early access beta (Deprecated)) however that repo doesn’t seem to exist anymore. I plan on using AYON with Blender and Houdini to start with but when I tried with the cloud setup before, it seemed there were many more packages necessary there. What am I missing here?
  2. I tried to switch back to ynput.cloud to see if my launcher setup is correct at least, however anytime I run the launcher, it tells me the error from above, that I don’t have a production bundle on my localhost server, which file / environment variable stores my current URL so that I can modify it?

Thanks for any help!

Andy

2

Hi beersandrew,

to get a running server you would need to setup and build some modules of the pipeline. Best to start to go through the steps here:

the docker image is recommended and saves you from putting together the front and backend, from the webinterface you be able to updload desired addons, along with the core addon

minimum docker image, launcher, core, dependency tool (i think ash is included with the docker image)

image
image1891×619 50.5 KB

to release a bundle you need, a launcher for your target OS and a dependency package, instructions are on the respective gits

image
image3420×841 220 KB

best of luck

1 Like
3

Thanks for the response @Jee!

I think I’m a lot closer, but not quite there yet.

My Steps:

  1. From above, I’ve run the docker image from the ayon-docker repository such that the server is running on my machine at http://localhost:5000
  2. Clone add-on repos (core, blender, houdini) into my /path/to/ayon-docker/addons/<addon-name>/<repo-root> (i.e /ayon-docker/addons/blender/ayon-blender)
  3. After doing this I see core, blender, and houdini listed in my server as addons
  4. See an error that core is missing a dependency of Launcher
  5. Clone ayon-launcher
  6. Run the dockerfile in that repo, to build the launcher
  7. Try and fail to upload this using ./tools/make.sh upload --server http://localhost:5000 --username admin --password admin
    • I tried using my local ip instead, since this command happens from within the docker image, it timed out on connecting
    • I tried copying the installer out of the docker image and uploading from my local machine, it failed on a missing dependency to ayon-api
  8. I used the web UI to upload the artifact from the build, it was successful
  9. I created a bundle
  10. I set the bundle as production
  11. Since my artist machine is the same as my server, I just tried to run the same launcher that I uploaded
  12. I get an error of AYON-launcher requires AYON core addon to be able to start

Questions / Comments:

  1. I do not have any Dependency Packages uploaded on my server, do I need them?
    • If so, how do I do this?
    • I’ve tried the following:
      1. Cloned ayon-dependencies-tool
      2. Ran docker buildx build -t ayon-dependencies-builder -f Dockerfile.rocky9
      3. Entered the docker image and went to /opt/ayon-dependencies-tool
      4. I don’t see anything here that looks like a build artifact
  2. What did I miss here, as the core does show up in my server UI?
4

Hi there,

Is there a reason why you are cloning the addon repos? It’s far easier to connect your instance to ynput cloud and install one of the pre-prepared release bundles for the market page.

image
image1919×628 89.9 KB

I’m sure @mustafa_jafar can help with any further setup?

1 Like
5

Hello, AYON is a modular system where you need to install addons to have more features.

Typically, a local AYON instance deployment is:

  1. Deploy ayon-docker locally.
  2. Login to your server and connect it to ynput cloud.
  3. Update pipeline to latest release.

Once you finish these setups, you’ll have your AYON server with default configuration and then you can start creating a project and learning about the system.

1 Like
6

Correct me if i’m wrong, since he is trying to deploy a free community edition server, he does not have the access to ynput cloud and the market? If the market ist available without subscription, I’m missing out.

@beersandrew while it is very doable to setup a server on your own, it takes time and some digging into the specifics. If you have a server running there is a lot on the pipeline that you need to be able to debug to get it running smoothly for you usecase.

7

we introduced the Update pipeline to latest release to help users get started and configure their AYON instance easily.
Connecting your AYON instance to ynput cloud is free.

2 Likes
8

That is awesome, very generous!

9

Thanks all! @mustafa_jafar Update pipeline to latest release has helped me be able to run the launcher at least, so I think I’m good for now, will try to set up some projects and work through them next.

It seems from the manual set up I was going for, I still needed these addons:

  • 3rd Party Distribution (ayon_third_party)
  • Applications (applications)

Are there github repos for these as well that can be manually cloned and set up without the Update pipeline to latest release?

11
12

Which manual?
Please, keep in mind that Update pipeline to latest release should provide you with the minimum pipeline configuration to start experimenting with AYON pipeline.

1 Like
13

@mustafa_jafar It did! And thank you for that. My last post was just out of my own curiosity to see what I might have been missing. Thanks @BigRoy