@kindlydodo I've updated my PR #863 with Docker dev env setup. Please try. Is it what you need?
You could start by reading the comment at the beginning of Dockerfile-dev

Looks awesome, thank you!
What I try to achieve is to have a container where the ui/ and api/ folder and the uncompiled source files are. This way I can change code and try it out live in my browaer

@kindlydodo Mapping the source code inside the container is easy by adding a new volume to the Photoview service in the docker-compose. However, now it is pretty useless, as you anyway need to recompile the code and reload it on the web server. Right now the code compilation and web server building are done in the same way, as for the production image (at the time of building the image).

To let you see the result of modifying the code on the fly, the development container should run the development web server. For the frontend code, the nodeamon or webpack can be used. For the Golang Realize or Air could be used.

I'm not a developer, so I don't know how exactly to configure these servers to work with this project. The additional challenge might be to make them work together, as now everything is served by the same server, while in this development setup, there should be separate processes (ideally different containers) for the frontend and backend.

So, if you can configure that and make it work, provide me the detailed guide to replicate that in the PR or step in and commit there your working config.

If you only want to modify the front end, maybe using a reverse proxy server can be a choice.

npm start -- --port 8003

nginx-1.24.0\conf\nginx.conf

http {
    include       mime.types;
    default_type  application/octet-stream;
	include "D:/code/nginx-1.24.0/sites-enabled/*.conf";  # add this line

nginx-1.24.0\sites-enabled\localhost_8002.conf 

server {
        listen       8002;
        server_name  localhost;
        location /api {
			proxy_pass http://localhost:8000/api;
			proxy_http_version 1.1;
			proxy_set_header Upgrade $http_upgrade;
			proxy_set_header Connection "upgrade";
		}
	location / {
			proxy_pass http://localhost:8003/;
	}	
}

We might need to review this issue after #863 is merged to provide a consistent environment. Also, a help from a frontend and backend developer will be needed to correctly configure the nodeamon or an alternative code watching server for both frontend and backend, potentially separating the dev environment to 2 images