Uploading New Versions
Deploy from a zip or tar without Git, and review every new upload as a diff before it's built. Roll back to any earlier upload.
No Git repository? An App can get its code from a zip or tar you upload instead. Every new upload is kept as a version, and nothing you upload is built until you've seen exactly what changed.
The first upload
Pick Upload archive when you create the App and choose a .zip, .tar, .tar.gz or .tgz file. That upload becomes the App's first version and its current one: what the first deploy builds.
If your archive wraps everything in a single folder (as zipping a project's folder usually does), Raklane looks inside it, so a package.json or go.mod inside that folder is found the same as one at the top.
Uploading a new version
Open the App's Settings → Source versions and click Upload new version. Raklane compares it with what's running and opens Review changes:
- how many files were added, changed and removed, and how many lines;
- every changed file, which you can expand to see its line-by-line diff (added lines in green, removed ones in red);
- binary files, such as images, marked as binary instead of shown line by line.
From there:
- Deploy this version builds exactly these files and rolls them out with the usual health check and automatic rollback (see Deploying Your App). It also becomes the App's current version, so a later Redeploy builds it too.
- Discard drops the upload. Nothing in it is ever built.
- Close keeps it pending review, so you can come back to it later from the version list.
Uploading files identical to the current version, or to one already waiting for review, does nothing: you're told it has no changes.
The version list
Settings → Source versions lists every upload, newest first, with its size, when it was uploaded and its changes:
| Label | Meaning |
|---|---|
| Running | What the App's live release was built from. |
| Current | What the next deploy without a choice builds. |
| Pending review | Uploaded, not deployed yet. Review or Discard it. |
| Previously deployed | An earlier version. Deploy this version rolls back to it. |
Rolling back
Click Deploy this version on any previously deployed version. It's built and rolled out like any other deploy and becomes the current version again. Your later uploads stay in the list.
What's kept
Raklane keeps your uploads compactly: a file that didn't change between uploads is stored once. It keeps the current version, the versions your last few releases ran (so you can always roll back to them), and your last 10 deployed versions. Uploads left pending review for more than 7 days are discarded. Deleting the App deletes all of its versions.
What's in a version
A version holds exactly the files your build gets, so what you review is what's built:
- a
.gitignorein your archive doesn't hide anything — every file in the archive is built; - a
.gitfolder inside the archive is left out, and so are.DS_Store,Thumbs.dband__MACOSX/files; - symbolic links and empty folders aren't kept, and file permissions are reduced to whether a file is executable.
The size limits are the same as for any archive upload: by default 200 MB uploaded, and at most 1 GB or 100,000 files once extracted.