Documentation Index
Fetch the complete documentation index at: https://mintlify.com/stormkit-io/stormkit-io/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Zip file deployments allow you to deploy applications without connecting a Git repository. This is useful for:- Static site exports from any build system
- Pre-built applications from CI/CD pipelines
- Quick prototypes without version control
- Legacy applications without Git repositories
- Manual deployments from local builds
Creating a Bare App
Bare apps are applications without Git integration that accept zip file uploads.Deployment Types
Static Deployments
Deploy static websites with HTML, CSS, JavaScript, and assets. Configuration:- Leave Start command empty
- Upload zip with static files
Server Deployments
Deploy applications with server-side logic. Configuration:- Set Start command before uploading zip
- Include server executable or entry point in zip
Preparing Your Zip File
Static Site Structure
For static sites, your zip should contain build output:Server Application Structure
For server applications, use the.stormkit folder structure:
Creating the Zip File
Using Command Line
Using GUI
Windows:- Right-click the folder containing build files
- Select Send to > Compressed (zipped) folder
- Right-click the folder containing build files
- Select Compress “folder-name”
- Right-click the folder containing build files
- Select Compress…
- Choose ZIP format
Deploying the Zip File
The deployment process will:
- Upload your zip file
- Extract and validate contents
- Deploy static files to CDN
- Configure server functions (if applicable)
- Generate preview URL
Verifying Deployment
Example: React App Deployment
Build Your App
Typical React Build Output
Deploy
- Upload
my-react-app.zipthrough Stormkit dashboard - Wait for deployment to complete
- Access your app at the preview URL
Example: Next.js Static Export
Configure Static Export
next.config.js
Build and Package
Deploy
Uploadnextjs-app.zip to your bare app.
Example: Vue.js Deployment
Build Your App
Deploy
Uploadvue-app.zip to your bare app.
Example: Server Application (Node.js)
Prepare Server App
Server Entry Point
.stormkit/server/index.js
Package and Deploy
server-app.zip to your bare app.
CI/CD Integration
Integrate zip deployments into your CI/CD pipeline.GitHub Actions Example
.github/workflows/deploy.yml
GitLab CI Example
.gitlab-ci.yml
Limitations
No Git Integration
- No automatic deployments on push
- No deployment history from Git commits
- No branch-based environments
Manual Process
- Each deployment requires manual zip upload (unless automated via CI/CD)
- No pull request previews
- No Git-based status checks
File Size Limits
Zip file uploads have size limitations. For very large applications, consider:- Connecting a Git repository instead
- Optimizing build output
- Removing unnecessary files
Best Practices
Include Only Necessary Files
Exclude development files from your zip:Optimize Build Output
- Minify JavaScript and CSS
- Compress images
- Remove source maps (unless needed)
- Tree-shake unused code
Version Your Zips
Name zip files with versions for tracking:Test Locally First
- Extract your zip file
- Serve it with a local server
- Verify all assets load correctly
- Then upload to Stormkit
Troubleshooting
Missing index.html
If you see “Top-level /index.html missing”:- Ensure
index.htmlis at the root of your zip - Check that you’re zipping the build directory contents, not the directory itself
Broken Asset Paths
If CSS/JS files don’t load:- Check that asset paths are relative or absolute
- Verify build tool configuration for production
- Ensure base URL is set correctly
Server Function Errors
If server functions fail:- Verify
.stormkit/serverfolder structure - Check that entry file exports
handlerfunction - Include all required node_modules in zip
- Ensure
@stormkit/serverlessis installed
Related Documentation
How We Deploy
Understand folder structure and deployment process
Configuration
Configure environment settings
Application Runtime
Deploy server applications
Troubleshooting
Fix common deployment issues