I want to develop or update agent-web without rebuild docker

[Nhagg]

Hello everyone,

I'm working on this folder and I don't see any way to deploy my JS code without rebuild Docker.
I'm using

docker-compose build agenta-web 
docker-compose up --no-deps -d agenta-web

But this command creates a new docker image cache and it's too big (3,5G per image)

Please help me to solve this issue. Thanks !

[dosubot[bot]]

Hello, @Nhagg! I'm here to help you with any bugs, questions, or contributions you have. Let's work together to solve the issue you're facing.

To update or develop your JavaScript code in the agent-web folder without rebuilding the Docker image, you can use Docker's volume mounting feature. This allows you to directly update the code without creating a large image cache. Here's how you can do it:

1. Use Volume Mounts: The docker-compose.yml file for agenta-web already includes volume mounts for the src and public directories:

   volumes:
       - ./agenta-web/src:/app/src
       - ./agenta-web/public:/app/public
       - .nextjs_cache:/app/.next

   With this setup, you can modify the JavaScript files in the src and public directories on your host machine, and the changes will be reflected inside the running container.

2. Run in Development Mode: Navigate to the agenta-web directory and run the following command to start the development server:

   npm run dev:local

   This command uses the next dev script configured in the package.json to run the application in development mode, allowing you to see changes without rebuilding the Docker image ^[1][2].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[Nhagg]

I get an error when install npm:
"$FEATURE_FLAG" was unexpected at this time.
npm ERR! code 1
npm ERR! path C:\D\projects\Agenta-POC\agenta-web
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c cd .. && husky && if [ "$FEATURE_FLAG" = "cloud-dev" ]; then cd .. && husky; fi || true

npm ERR! A complete log of this run can be found in: C:\Users\nha.le\AppData\Local\npm-cache_logs\2025-02-18T06_19_30_243Z-debug-0.log

In addition, "npm run dev:local" will run dev server in a new port. I'm not sure it will work with docker.

[mmabrouk]

Hello @Nhagg

I am not sure I understood your question. Are you trying to develop in Agenta and have live preview (each time you make a change you see what happens)? Or are you trying to deploy agenta locally and do not want to use docker? Or something else? Can you please provide more information about what are you trying to achieve (modify agenta? just deploy it?..)

A couple of things though:

• You can run Agenta in development mode through the script https://github.com/Agenta-AI/agenta/blob/main/run_oss.sh This runs the frontend outside of docker using npm run dev:local
• If you want to use Agenta, you don't need to build, just use the commands below:

mkdir agenta && cd agenta
curl -L https://raw.githubusercontent.com/agenta-ai/agenta/main/docker-compose.gh.yml -o docker-compose.gh.yml
echo "OPENAI_API_KEY=sk-xxx" > .env
docker compose -f docker-compose.gh.yml --env-file .env up -d --pull always

[Nhagg]

Hi @mmabrouk
I'm using all services from Agenta and want to modify agent-web.
However, I don't want to rebuild docker for a simple JS code in agenta-web.

Thank you for your support!

[mmabrouk]

Here are your options for updating the web interface without rebuilding the entire container:

1. Default approach: Rebuild the web image and restart the container when making changes.

2. Development mode: Run the frontend outside Docker using the run_oss.sh script. This works only in development mode but avoids rebuilds.

3. Modified approach: Adapt the run_oss.sh script for production by:

   • Building the Next.js project
   • Running npm run start instead of the dev command
   • This lets you run the frontend outside Docker without rebuilding

Choose option 2 if development mode meets your needs, or option 3 for a production-ready external frontend.

[mmabrouk]

This has been resolved starting v0.43.1