Publishing

#Deploy

Deploy in the header ships the current files and gives the app its own address on Ripping's hosting (a .vercel.app address). After the first deploy the button reads Update. It goes grey when the live app already has these exact files ("The live app already has these changes") and comes back when anything changes.

Deploying records a version; History shows which version is live. Put live on an older version is instant when that version was deployed before. Building never changes the live site; only Deploy and Put live do.

What can stop it:

• "There's nothing to deploy yet. Build the app first."
• Plan limits. Free includes one live app; Singularity ten. Over the limit: "Your plan plan includes N live apps. Take another app offline from its History tab, or upgrade, to deploy this one."
• "That's a lot of deploys in an hour. Try again in a few minutes." (30 deploys per hour per account.)

Take offline (History tab) removes the live app. Versions, data and users stay; Deploy puts it back.

#How it appears

On the Settings tab: tab title (empty uses what the app says about itself), meta description (300 characters; search engines show about 155), favicon (an emoji or a square PNG, JPEG or WebP), and Let search engines index it (off adds a noindex tag, useful while it is a draft). These apply the next time you deploy.

#Custom domains

Domains need a paid plan (Free includes none; Singularity ten). Add one from the project's Settings tab under Domain, or from account Settings, where you can also buy one.

1. Deploy the app first. A domain connects on the app's first deploy; before that the status says "Deploy the app first. The domain connects on its first deploy."
2. Type the domain (app.yourcompany.com or yourcompany.com) and press Add.
3. The card shows the records to add at the company you bought the domain from:
   • A subdomain: CNAME with name app (the part before your domain) and value cname.vercel-dns.com.
   • A root domain: A with name @ and value 76.76.21.21.
   • Sometimes a TXT record to prove the domain is yours, shown only when needed. The card uses whatever values hosting recommends; copy what it shows rather than these defaults.
4. Wait for DNS (usually minutes, up to an hour) and press the refresh icon to check now. Status moves from Waiting on DNS to Connected. SSL is automatic.

Errors you may see: "That doesn't look like a domain", "That domain is already added", "This domain is connected to another Vercel project. Remove it there first, then check again." Taking the app offline sets its domains back to pending until the next deploy.

Invited users and approval emails link to a connected domain first, then the published address.

#Chrome extensions

An extension project has no hosted URL. Instead of Deploy, the header has:

• Download extension: a zip named <project>-extension.zip. Inside: manifest.json (Manifest V3, version filled in, icons wired), popup.html, popup.js, popup.css (Tailwind compiled in), background.js and content.js when the project has them, icons/icon16.png, icon48.png, icon128.png drawn in your primary colour, and a README.md with the install steps. Nothing loads from the network at runtime.
• How to install:
  1. Click Download extension and unzip the file.
  2. Open chrome://extensions and turn on Developer mode at the top right.
  3. Click Load unpacked and choose the unzipped folder.
  4. Pin it from the puzzle-piece menu next to the address bar, then click its icon.

After a change, download again and click the reload arrow on the extension's card. The same zip uploads to the Chrome Web Store developer console. Downloads are limited to ten a minute; the button waits until the first build is done.

#Sharing

Share in the header puts the project on a public page. Add one line about it (200 characters) and press Make public. The link is getripping.com/p/<slug>; copy it from the dialog. The page shows the running app, view and remix counts, a Live site link when deployed, and Remix, which copies the code into the visitor's own account (after sign-in). Your chat history and connections stay private. Make private takes it down.

#Exporting the code

The download icon on the preview tab bar saves the whole project as a zip. Every file is also readable on the Code tab.