domains / families / devops / cloudish

cloudish

authentic

Deploy a Dockerfile, source folder, or existing image to Cloudish as a running container at a live URL, built server-side with no local Docker, with confirmation before spending credits.

When to use

• Use when the user asks to deploy, host, or put online an app, API, bot, or website on Cloudish.
• Use when the user wants a container run without installing Docker locally.
• Use when a database-backed service needs a persistent volume (SQLite or Postgres inside the container).
• Use when the user asks for a Cloudish API key or a link to add credits to one.
• Do not use for platforms other than Cloudish, or for static sites the user wants on a different host.

When not to use

• Requires network access to `cloudish.ai` and an API key with credits; once a project is out of credits, requests to it return HTTP 402 instead of starting the container.
• One HTTP port per container. There is no managed database service; databases run inside the container.
• Volume sizes, idle timeouts, and instance sizes are fixed sets defined by the API and may change; see https://cloudish.ai/skill.md and https://cloudish.ai/instances.md.
• The API reference changes outside this repository; this skill describes the API as of its `date_added`.
• Does not configure custom domains, CI pipelines, or authentication inside the user's app (Cloudish offers an OIDC provider the app can use, documented in the API reference).

Skill page

Source