Svelte as a pure SPA built by Vite is the lightest of the frontend stacks in the Saplo catalog - no virtual DOM, no Node process kept in memory after the build, just static files under nginx. Below is a step-by-step guide, including deploying your own code via `git push` and the difference compared to SvelteKit.
#Git Deploy#JavaScript#GuideAngular is the choice for large enterprise applications with extensive routing and multiple modules, and on Saplo you deploy it just like …
#Angular#Git Deploy#JavaScriptNot every project fits a ready-made recipe from the catalog. A clean server on Saplo is an empty Debian 12 container with …
#Linux#Guide#SSHA Django application needs a running gunicorn process in the background, not just a directory with files, exactly like a Next.js app …
#Django#Git Deploy#GuidePlain HTML, CSS, and JS files, or the output of any static site generator, can be deployed on Saplo with no build …
#Git Deploy#HTML#GuideDocker is the most flexible option in the Saplo catalog - you provide your own Dockerfile or docker-compose.yml, and Saplo builds and …
#Docker#Docker Compose#Git DeployNode.js is not a framework, but a runtime - the "Node.js" stack in the Saplo catalog doesn't impose any conventions. You can …
#Backend#Git Deploy#JavaScriptSvelteKit compiles components to pure JavaScript during the build, so the finished application is extremely lightweight and starts quickly, even on older …
#Git Deploy#JavaScript#GuideNuxt is to Vue what Next.js is to React - full server-side rendering that requires a long-running Node process in the background, …
#Git Deploy#JavaScript#NuxtAstro defaults to generating a fully static site and lets you add interactive components (islands) from React, Vue, or Svelte only where …
#Astro#Git Deploy#JavaScript
