Org-wide deployments
Ainize (Deploy) GitHub repositories
You can Ainize a GitHub repository to an organization cluster the same way you Ainize to a public cluster. Check out the Ainize (Deploy) page for detailed instructions.
Private repository
If an organization member Ainizes private GitHub repositories, those repositories are deployed to an organization cluster. Org-wide deployments have the following characteristics:
A non-organization member who knows the exact deployment page URL is able to view the page. However, access to the Ainize endpoint can be configured based on the organization's network security policies.
Deployments are listed under the Organization category on the Explore page.
Organization categories are NOT exposed to the public.
Endpoint URLs have the following format:
https://{ip-address}:{port-number}
Since org-wide deployments use the resources provided by the organization cluster, they are affected by the organization's resources and any other limitations the organization cluster has.
Public repository
A public repository is Ainized to a public cluster, even if the user is a member of an organization. These public deployments have the following characteristics:
ALL users of Ainize, including the public and organization members, can access the deployment page as well as the Ainized endpoint.
Endpoint URLs have the following format:
https://{branch-repository-user}.endpoint.ainize.ai
Public deployments use public clusters, thus they are not affected by the organization's resources or any other limitations the organization cluster has.
Ainize GitHub app access
If you encounter the below message, follow these steps to check if proper access is granted to the repository:
Click the
GitHub App Settings
Choose an organization or an account that the repository belongs to
Check if Ainize is permitted to access the repository. If not, include the repository and click
Install
Then, click
try again
If the repository belongs to others, you are not able to Ainize it.
Last updated