frontend/backend: continuous deployment for production and development

[RobertRosca]

We have the domains damnit.xfel.eu and damnit-dev.xfel.eu, these two domains are currently cnames pointing at the da server:

❯ doggo damnit.xfel.eu
NAME                	TYPE 	CLASS	TTL   	ADDRESS             	NAMESERVER    
damnit.xfel.eu.     	CNAME	IN   	86400s	exfldadev01.desy.de.	127.0.0.53:53	
exfldadev01.desy.de.	A    	IN   	86400s	131.169.220.242     	127.0.0.53:53	

❯ doggo damnit-dev.xfel.eu
NAME                	TYPE 	CLASS	TTL   	ADDRESS             	NAMESERVER    
damnit-dev.xfel.eu. 	CNAME	IN   	86400s	exfldadev01.desy.de.	127.0.0.53:53	
exfldadev01.desy.de.	A    	IN   	86400s	131.169.220.242     	127.0.0.53:53	

Idea is that once we have a dedicated server for damnit web those cnames can just be updated to point to it.

My plan is to have CI/CD deploy releases to damnit.xfel.eu, and on a PR to deploy to damnit-dev.xfel.eu/BRANCH/NAME.

The production deployment is easy enough, but the dev one is a bit more awkward as it has proxying to a path. For the backend this shouldn't be a big issue as it does not have many relative path references, not too sure about the frontend though.