Skip to main content
When a site needs something only an app has, such as its own domain or server rendering, convert it. See Site or App? for the rule.
Run it in the site’s folder, or pass the folder as an argument. Converting needs an admin login whose role can manage the company’s sites and create and code Mist apps. It asks before it starts; pass --yes to skip the question. The app is built in the background, and its first deployment usually follows within a few minutes.

​
What happens

  • The code. The app starts from the site’s source repository when it has one. Otherwise the files of the site’s live build become the app’s repository and are served as they are, never built again.
  • The address. Once the app’s first deployment is ready, the site is archived, not deleted, and /sites/<handle> sends visitors to the app’s address at the same path.
Environment variables and secrets aren’t carried over. Set them again on the app.

​
What can’t be converted

Only a public company site converts, because an app has no Fluid sign-in to keep a private or members-only site closed. A conversion is refused, and nothing is created, for:
  • a member’s own site;
  • a private site, or one that declares visitor data;
  • a site with a database. Its rows can’t be moved into an app yet. Download the database first if you need them;
  • a branch, a site a company admin took down, or an archived site;
  • a site that isn’t published through the sites gateway;
  • a site that is already being converted, or was converted;
  • a company with no credits for a new app.

​
Through the API

Convert a company site into a Mist app starts a conversion, and read a site’s conversion shows how it’s going.