This is my static site running on lttle.cloud
+ + +``` + +### Switch to automatic building + +Update your `lttle.yaml` to use automatic building instead of the pre-built nginx image: + +```yaml title="lttle.yaml" +app: + name: hello-lttle + build: auto + resources: + cpu: 1 + memory: 128 + expose: + public: + port: 80 + external: + protocol: https + mode: + flash: + strategy: + listen-on-port: 80 + timeout: 2 +``` + +The `build: auto` configuration tells lttle.cloud to: +1. Automatically detect your project type (static files) +2. Build an appropriate container image automatically +3. Push the image to lttle.cloud's registry +4. Deploy using the built image + +For more information about building, see [Building & Deploying > Building](../building-and-deploying/building.md). + +### Deploy your custom site + +Deploy with automatic building: + +```bash +lttle deploy +``` + +You'll see build output: +``` +→ Building image for default/hello-lttle +→ Auto-build using providers: staticfile +→ Pushing image for default/hello-lttle → registry.lttle.cloud/tenant/hello-lttle:abc123 +→ Successfully built and pushed image for default/hello-lttle +→ Successfully deployed app: default/hello-lttle +``` + +### Test your custom site + +Check the machine status: + +```bash +lttle machine ls +``` + +Once the machine reaches `suspended` state, open your site URL in the browser. You should now see your custom "Hello, lttle.cloud!" page instead of the nginx welcome page. + +## What's Next? + +You've successfully deployed a static site with: +- ✅ Automatic image building from static files +- ✅ Flash mode for cost-efficient serverless hosting +- ✅ Custom content served by nginx + +### Explore More Features + +- **Add a custom domain**: Set a custom `host` in your app's [expose external](../resources/apps.mdx#expose-external) configuration +- **Add HTTPS**: Set up [certificates](../resources/certificates.mdx) for secure connections +- **Build from source**: Learn about [advanced building options](../building-and-deploying/building.md) + +### Project Structure + +Your final project structure should look like: + +``` +my-static-site/ +├── lttle.yaml +└── index.html +``` + +The `lttle.yaml` file defines your infrastructure, while `index.html` contains your site content. lttle.cloud automatically builds everything into a deployable container image. diff --git a/docs/getting-started/deploying-an-existing-app.md b/docs/getting-started/deploying-an-existing-app.md new file mode 100644 index 0000000..749c192 --- /dev/null +++ b/docs/getting-started/deploying-an-existing-app.md @@ -0,0 +1,106 @@ +--- +sidebar_position: 4 +--- + +# Deploying an existing app + +This guide shows you how to deploy an existing application to lttle.cloud using the automatic initialization tool. + +## Prerequisites + +- lttle CLI installed and configured ([Installation guide](./installing-the-cli.md)) +- An existing application or project directory + +## Quick Start + +### Navigate to your application + +Go to your existing application directory: + +```bash +cd my-existing-app +``` + +### Initialize lttle.cloud configuration + +Run the initialization command: + +```bash +lttle gadget init +``` + +The `gadget init` command will: +- Automatically detect your application type and framework +- Generate appropriate lttle.cloud configuration files +- Provide deployment instructions specific to your project + +### Follow the initialization output + +The command will analyze your project and provide tailored instructions. Common scenarios include: + +**For web applications:** +- Detects package managers (npm, yarn, pnpm) +- Identifies frameworks (Next.js, React, Vue, etc.) +- Generates app configuration with appropriate build settings + +**For API servers:** +- Detects runtime (Node.js, Python, Go, etc.) +- Configures appropriate ports and health checks +- Sets up service exposure + +**For static sites:** +- Identifies static content +- Configures nginx or appropriate server +- Sets up automatic building + +### Deploy your application + +After `gadget init` completes, deploy using: + +```bash +lttle deploy +``` + +## What `gadget init` creates + +The initialization process typically generates: + +- **`lttle.yaml`** - Main deployment configuration +- **`.lttle/`** - Directory with additional configuration files (if needed) +- **Build configuration** - Automatic detection of build requirements + +## Customizing the configuration + +After initialization, you can modify the generated `lttle.yaml` to: + +- Adjust resource allocation (CPU, memory) +- Configure environment variables +- Set up custom domains +- Add flash mode for cost efficiency +- Configure dependencies + +For detailed configuration options, see: +- [Apps configuration](../resources/apps.mdx) +- [Building options](../building-and-deploying/building.md) + +## Troubleshooting + +**No compatible framework detected:** +- The tool may not recognize your specific setup +- Manually create a `lttle.yaml` file based on the [apps documentation](../resources/apps.mdx) + +**Build errors during deployment:** +- Check the generated build configuration +- See [Building troubleshooting](../building-and-deploying/building.md#troubleshooting) + +**Port configuration issues:** +- Verify your application listens on the correct port +- Update the `expose` configuration in `lttle.yaml` + +## What's next? + +Once your app is deployed: +- **Monitor status**: Use `lttle machine ls` to check deployment status +- **View logs**: Use `lttle machine logs