reform frontend out of Docker stuff + other Docker

[jtagcat]

• other Docker things

to get all images on cli:
docker build -t t:latest-celery-fast . --target=celery-fast
docker build -t t:latest-celery-slow . --target=celery-slow
docker build -t t:latest . --target=api
docker build -t t:latest-gpu -f gpu.Dockerfile .
(compose: see docker-compose files)

Closes #122

GPU not tested, others tested.

[JeffreyCA]

Suggested change

	target: api
	context: .
	target: api

Unable to run docker compose without the context field for api and other services

[jtagcat]

huh, I had the issue the other way around (when context had subargs, target was needed)
(tested the thing asw)

[jtagcat]

might be that here.. it does not have subargs :)

[JeffreyCA]

Thanks for reorganizing!

I'd like to keep the existing behaviour with docker-compose.dev.yml where a frontend service is running npm run dev (webpack in watch mode) and has a shared volume that maps to the local host machine's frontend/src. It simplifies debugging/development by rebuilding the frontend automatically after modifying the source on the host machine. It doesn't seem to work anymore with these changes.

[jtagcat]

Would using a separate Dockerfile for debug (stop at step before adding frontend + frontend separate)/prod be fine?

[jtagcat]

anygay, I'll try to split up the commit if I can

edit: can do: include frontend in api, but it can be overwritten by mounting to the same location (making using frontend image optional)

[JeffreyCA]

Yeah that's fine