Public release of the addon

[ymoriaud]

Hi !

I'm using that issue to centralize all small things that need to be done in order to publicly release the addon:

• [ ] Where should we store Ayon aquarium service images ?
  • In Ynput Docker hub ?
  • In this repository ?
• [ ] Add the Addon in Ayon market. Milan told me sent him a .zip file.
• [x] Merge https://github.com/ynput/ayon-documentation/pull/150 to publish documentation
• [ ] Build dependencies (optional since I added dependencies in the code)
• [ ] Add Aquarium logo on Ynput Discord ? :D
• [x] Changing this repository from private to public

If you thing I forget something, let me know !

[BigRoy]

@ymoriaud what's the status of this for currently?

---

@MustafaJafar noticed on https://fatfi.sh/aquarium/features#integrations this image:

Would be great if that would be AYON, with the AYON logo and AYON URL - and potentially not "soon" but already there? Not sure what might still be lingering to get that across the finish line?

[ymoriaud]

Thanks. Regarding the website, an upgrade is in progress. We already integrated Ayon mention instead of Openpype.

Regarding the general status, some PR was created and merged. But we are looking for more users to provide feedback.

[MustafaJafar]

@ymoriaud , wow that was a quick response, many thanks.

---

• [ ] Where should we store Ayon aquarium service images ?
  • In Ynput Docker hub ?
  • In this repository ?

I should leave this question for @mkolar or @dee-ynput

Personally, I think this question depends on who will make the releases and upload the services (as they will need some permission depending on who and where)

I've checked manage.ps1 scripts, I followed them and the image paths they were pointing to

• ghcr.io/fatfish-lab/ayon-aquarium-processor:0.0.4
• ghcr.io/fatfish-lab/ayon-aquarium-leecher:0.0.4

side note, package.py should point to the same paths e.g.

services = {
    "leecher": {"image": f"ghcr.io/fatfish-lab/ayon-aquarium-leecher:{version}"},
    "processor": {"image": f"ghcr.io/fatfish-lab/ayon-aquarium-processor:{version}"}
}

[ymoriaud]

Yes, you are right. Regarding docker, I prefer to store them on the repository. So it's easier to develop and we can be more independent when a new deployment is required.

Currently we host them under fatfish-lab umbrella. If needed we can move the images under ynput umbrella, but you will need to allow us to push new images on this repository. Another solution is to move this repository under fatfish-lab.

I'm creating an issue to track your side node.