Bun HTTP Server
This guide explains how to create and deploy a Bun app. To run this example, follow these steps:
- Install the CLI. Use the unikraft CLI or the legacy kraft CLI. You need a BuildKit builder. The easiest way to get one is via Docker. Alternatively, you can also directly set up and use BuildKit, see the quick start.
The unikraft CLI is the current standard, while kraft is the legacy version. Choose one of the CLIs below and only run the commands associated with it for the rest of this guide.
- Clone the
examplesrepository andcdinto theexamples/httpserver-bundirectory:
Code
Make sure to log into Unikraft Cloud and pick a metro close to you.
This guide uses fra (Frankfurt, 🇩🇪):
When done, invoke the following command to deploy this app on Unikraft Cloud:
The output shows the instance address and other details:
In this case, the instance name is httpserver-bun-700mp and the address is https://quiet-pond-ao44imcg.fra.unikraft.app.
They're different for each run.
Use curl to query the Unikraft Cloud instance of the Bun HTTP web server:
Code
Code
You can list information about the instance by running:
When done, you can remove the instance:
Customize your app
To customize the app, update the files in the repository, listed below:
Kraftfile: the Unikraft Cloud specificationDockerfile: the Docker-specified app filesystemserver.ts: the Bun server implementation
Lines in the Kraftfile have the following roles:
-
spec: v0.7: The currentKraftfilespecification version is0.7. -
runtime: base-compat:latest: The kernel to use. -
rootfs: Build the app root filesystem.source: ./Dockerfilemeans the filesystem is built using theDockerfile.format: erofsmeans the filesystem type is EROFS. -
cmd: ["/usr/bin/bun", "run", "/usr/src/server.ts"]: Use/usr/bin/bun run /usr/src/server.tsas the starting command of the instance.
Lines in the Dockerfile have the following roles:
-
FROM scratch: Build the filesystem from thescratchcontainer image, to create a base image. -
COPY ...: Copy required files to the app filesystem: thebunbinary executable, libraries, configuration files, the/usr/src/server.tsimplementation. -
RUN ...: Run specific commands to generate or to prepare the filesystem contents.
The following options are available for customizing the app:
-
If you only update the implementation in the
server.tssource file, you don't need to make any other changes. -
If you want to add extra files, you need to copy them into the filesystem using the
COPYcommand in theDockerfile. -
If you want to replace
server.tswith a different source file, update thecmdline in theKraftfileand replace/usr/src/server.tswith the path to your new source file. -
More extensive changes may require extending the
Dockerfile(seeDockerfilesyntax reference).
Learn more
Use the --help option for detailed information on using Unikraft Cloud:
Or visit the CLI Reference or the legacy CLI Reference.