Git and Cloud Storage

Connect your Git provider

Where to find: Integration → Git

The screen features Bitbucket, Github and Gitlab, each with Information and Link. The bottom list shows provider, email and actions of linked accounts.

1. Open Integration and select Git.
2. Read Information from the desired provider to check the requirements.
3. Select Link Github, Link Gitlab or Link Bitbucket.
4. In the provider, check the account and scope of access requested before authorizing the link.
5. Return to the panel and confirm the integration into the table. Use the provider and Search filter to locate the account.
6. When creating the application, choose Git and the same provider to publish your repository.

Publish code through Git and follow updates

Where to find: Applications → Create an Application → Git

Preset repository, branch, runtime version, and public directory. Publishing a wrong branch changes the content of the site.

1. Please enter the name and domain of the application.
2. Select Git in Select a Method and choose Bitbucket, Github or Gitlab.
3. Complete the account, repository, and branch options that the panel displays after selecting the provider.
4. Check out the advanced system user options, PHP and Custom Webroot.
5. Review build requirements and project configuration. If there is deploy script field, use only required and tested commands.
6. Complete the creation and follow the records of the deploy and the published domain.
7. In the application Git tools, when present, check the branch before manually updating or setting up automatic update. Test the application after each deploy.

If the result is not expected

Connect a storage destination

Where to find: Integration → Cloud Storage

Cloud Storage offers Google Drive, Dropbox, Amazon S3, S3 Compatible Storage and Wasabi. The destination needs to be linked before being selected in a backup.

1. Choose the provider on the Cloud Storage screen and read Information.
2. For Google Drive or Dropbox, select Link and complete the authorization in the destination account by checking the requested access.
3. For Amazon S3, Wasabi or S3 Compatible Storage, open Link and fill in your provider's credentials and bucket.
4. Use Name to identify the destination; inform Access Key, Access Secret, Region Name and Bucket Name.
5. In S3 Compatible Storage, please also inform Endpoint. Bookmark Enable Path-Based Endpoint only if the provider requires the access format by path.
6. Review the data and click Save. Confirm integration in the bottom table.
7. Open the backup form and confirm that the destination appears in Storage Provider. Create a test copy of the project and check out the result and files in the destination.

Understand the fields and options

Name

Name recognizable to differentiate destinations and accounts.

Access Key / Access Secret

Storage access credentials, not the panel password.

Region Name

Region used by the bucket, with the identifier required by the provider.

Bucket Name

Exact name of the bucket that will receive the files.

Endpoint

Supported S3 service API address.

Enable Path-Based Endpoint

Access mode by path, when required by the provider.

If the result is not expected

Link the Cloudflare area of the application

Where to find: Application → Cloudflate Integration → Integrate

The integration requires Bearer Token and Zone ID to manage DNS. Check if the zone matches the application domain.

1. Open the correct application and select Integrate in the Cloudflare Integration group.
2. In your Cloudflare account, get the API token and zone identifier needed for integration.
3. Fill out Bearer Token and Zone ID.
4. Check token domain, zone, and permissions before clicking Integrate Now.
5. After the link, check the DNS actions that the panel makes available and test the domain resolution after any change.