Skip to main content

Using Bolt.new locally using Bolt.diy and Ollama

Maybe you’ve heared about Bolt.new, the AI solution from StackBlitz that allows you to prompt, edit, and deploy full-stack web and mobile applications in a breeze. It uses an in-browser AI web development agent that leverages StackBlitz’s WebContainers to allow for full stack application development. The application presents users with a simple, chat-based environment in which one prompts an agent to make code changes that are updated in real time in the WebContainers dev environment.

I find it a great way to get a head start when building small(ler) web applications. But what if due to company policies or other reasons, you are not allowed to use bolt online?

In that case I have some good news for you, as the team from StackBlitz also created bolt.diy, the open source version of Bolt.new which allows you to choose the LLM that you use for each prompt.

Installing Bolt.diy

The easiest way to install Bolt.diy is through Docker.

  • Start by cloning the repository locally:

git clone https://github.com/stackblitz-labs/bolt.diy.git

  • Now we can build the docker image locally:

docker build . --target bolt-ai-development

  • Once the container is built, we can run it through:

docker compose --profile development up

Connecting Bolt.diy with Ollama

Before we can give Bolt.diy a try, we first need to connect it to a provider. In this example, we’ll use a local LLM exposed through Ollama. Let’s see how we can configure this. As we have Bolt.diy running in a docker container and Ollama directly on our system, we need to configure the OLLAMA endpoint.

  • Start by adding a .env.local file. Inside this file I configure the URL to my local OLLAMA instance:
  • This .env.local file is also referenced inside the docker compose yaml:
  • Remark: Don’t forget to restart the container otherwise your changes are not detected.
  • Now we can browse to Bolt.diy locally (in my case http://localhost:5173/):
    • Be patient: it can take some time before the site is loaded the first time

  • Once the site is up and running, hover over the Bolt.diy icon and click on the Settings icon in the bottom left corner.The control panel appears:

 

  • Click on Local Providers. Check that the toggle button is activated next to the Ollama provider:

Giving Bolt.diy a try

Now we are finally ready to give Bolt.diy a try.

  • Select Ollama from the dropdown list and also select a model of your choice:

 

  • Now you can describe what you want to generate and let the agent do its work:

 

That’s it! I’ll dive more in the features of Bolt.new and Bolt.diy in a later post…

More information

bolt.new

stackblitz-labs/bolt.diy: Prompt, run, edit, and deploy full-stack web applications using any LLM you want!

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

The role of ActivitySource in OpenTelemetry for .NET

While doing some pair programming to integrate OpenTelemetry tracing to a .NET application, we had a discussion on how to use the ActivitySource . It looks simple. You new one up, give it a name, start an activity, done. The discussion started when we added a second ActivitySource with the exact same name in a different class. This made us wonder: "Are we duplicating traces now? Is this a memory leak? Do we need a singleton?" So we decided to dig deeper. This post is what we learned… What ActivitySource actually is ActivitySource is part of System.Diagnostics , not part of the OpenTelemetry NuGet packages. Microsoft built tracing primitives directly into the BCL, and OpenTelemetry's .NET SDK simply listens to them. This is why you can add distributed tracing to a library without taking a dependency on OpenTelemetry at all. An ActivitySource is a factory for Activity objects, and an Activity is .NET's name for what OpenTelemetry calls a span.(don’t ask m...
Read more