Stack
The languages, libraries, services, build tools, web servers and test tools the templates use, and what Light Cloud does with each when it deploys your app.
Free plan, no card. Google or GitHub sign-in.
Send me the link for my desktopLanguages
Nothing to set up: Light Cloud builds the project with its runtime or its Dockerfile, and the build turns the code into what runs.
Frameworks and libraries
Installed with the app's other dependencies when Light Cloud builds it, from the lockfile or the template's Dockerfile. Nothing to set up.
UI and styling
Compiled into the app's HTML, CSS and JavaScript by its build script, which Light Cloud runs on every deploy. Nothing to set up.
Data and databases
Templates keep their data in a PostgreSQL database that Light Cloud creates and connects, with the connection string in an environment variable.
Services and APIs
Needs an account and keys of its own. They go in the app's environment variables on Light Cloud; the deploy form asks for the ones the template needs.
Build tools and package managers
Runs inside the Light Cloud build, in the build container, so there is nothing to install or run yourself.
Web servers
Runs inside the app's container and answers its requests; Light Cloud sends HTTPS traffic for the app's URL to the port the container listens on.
Testing and code quality
Runs on your machine or in CI. A Light Cloud build installs the dependencies and runs the build, never the tests or the linter, so run it before you push.
Formats and specifications
Part of the files in the repository: change them and push, and Light Cloud builds and deploys the new version.