Getting started
Jollop is a zero-config deploy platform. You drop code, in any language, and get a running service at a public HTTPS URL. There is no Dockerfile to write, no manifest to fill in, and no language flag to pass. The platform works out how to build and run your code by actually running it and watching what it does.
Deploy in one command
Install nothing on the server. From a project directory:
jollop deploy .
That tars your tree, uploads it, and streams the pipeline: ingest → detect → build → probe →
publish. When it goes green you get a URL like https://a3f9c2.jollop.run.
You can also deploy without the CLI: open the app, drag a folder or a .zip onto the drop zone, and
the same pipeline runs in the browser.
What you can deploy
Anything that runs. A web server, a raw TCP service, a background worker, a one-shot job, a folder of static files, a bundle of documents, a container image, even a desktop GUI app streamed to the browser. The app kinds page covers each shape.
The three ideas worth knowing
- Detection by execution. Static analysis only ranks guesses; the probe proves the right one by running your code. This is why unusual projects tend to just work.
- The run contract. Once an app goes green, the resolved plan becomes a user-editable contract. If the platform ever infers something wrong, you fix it in the UI, no Dockerfile required.
- Sharing & visibility. Every app gets a URL you can make public, share with a secure link, scope to your organization, or keep private.
Next steps
- Ways to deploy: local directory, git URL, archive, or container image.
- CLI reference:
deploy,login,share, and more. - The Jollop agent: build and manage deploys in natural language.