Integrations
Integrations
Section titled “Integrations”An integration is a connection to a service outside Meshploy, made once for the whole workspace and used wherever it is needed. Credentials are stored encrypted.
A git connection lets services build from private repositories and deploy on push. GitHub connects through the Meshploy GitHub App; GitLab, Gitea and Bitbucket through a token, which Meshploy also uses to add the push webhook to a repository.
Registries
Section titled “Registries”A registry is where built images are pushed and pulled from. Every workspace has a built-in registry on the gateway; connecting another, such as Docker Hub, GitHub’s or a cloud provider’s, lets services pull private images from it or build to it.
Storage
Section titled “Storage”A storage integration is an S3-compatible bucket, where database, volume and system backups are written.
DNS providers
Section titled “DNS providers”A DNS provider is an account at the host that keeps one of your domains’ zones, such as Cloudflare, connected with an API token. It is for an on-demand domain, whose DNS stays with you: instead of you adding each record by hand and each hostname getting a certificate on its first visit, Meshploy writes the records through the provider and proves it controls the domain there, so wildcard certificates, including for internal routes, are issued up front.
The token needs permission to read zones and edit their DNS records. When you add it, Meshploy checks it by writing a TXT record under _meshploy-check in each zone it sees and removing it again, and lists the zones it may write in. When you add an on-demand base domain, choose the provider under Records. Meshploy writes *.<domain> pointing at the gateway (and the domain itself, if it has no records yet), reads them back, and the domain is verified straight away, with no TXT record to add. Each record it writes carries a comment naming that domain, and it never changes or removes a record without one, so records of yours under the same names are left alone. Removing the domain, or switching its records to manual, removes what Meshploy wrote. A provider cannot be disconnected while a domain still uses it.
Notifications and email
Section titled “Notifications and email”Notification channels (Slack, Discord, email, or a signed webhook) are told about deployments, failures and other events you choose. Email is the SMTP server Meshploy sends invitations and notifications through.
- Built-in registry: The registry on the gateway every workspace starts with, where images are built to by default. More
- Storage integration: An S3-compatible bucket where backups are written. More
- DNS provider: An account at the host that keeps a domain’s zone, through which Meshploy writes that domain’s records and gets its wildcard certificates. More