Working with Git repositories in the context of the Greennode AI Platform offers several benefits such as version control, collaboration, branching and merging, code review, traceability and auditing. Follow the guidance below to learn more about how to work with Git Repository in the concept of the Greennode AI Platform.
When creating notebook instance, our Greennode AI Platform allow you to fetch source code or any related data stored on Git Repository, follow these steps:
Mount directory: The mount directory is where you mount the s3 bucket to the notebook instance, and once mounted, your source code will be placed in that directory. Input exactly the path to the folder containing your source code within the notebook instance. e.g., “/home/aiproject”.
Git repository URL: Leave the path to your git repository in 2 cases
Public repository: Input full path access to your git repository, e.g., “https://github.com/miguelgfierro/ai_projects.git“.
Private repository: When accessing a private Git repository via HTTPS, you'll need to provide your Git credentials (username and password) for authentication. The URL format for accessing a private Git repository via HTTPS is typically: https://username:password@github.com/owner/repository.git. Replace username with your Git username, password with your Git password (or a personal access token), owner with the repository owner's username or organization name, and repository with the name of the repository. For example https://yourusername:yourpassword@github.com/owner/repository.git.
Once the source code is successfully fetched (only when your notebook instance runs successfully), it will be available in the Notebook instance in the mount directory for further use.
Security Considerations: Using passwords directly in URLs is not recommended due to security reasons. Instead, consider using personal access tokens for authentication.
Risk of Data Inconsistency: Users should be aware that the Greennode AI Platform does not support automatic synchronization with Git repositories. Lack of synchronization with Git repositories can disrupt collaborative workflows and hinder team members' ability to track changes, review code, and coordinate development efforts effectively. Therefore, we recommend our using S3 bucket for the same situation instead.