Browse Source
			
			
			Update README.md
			
				Added infos about enabling https when softwares getting certs are using symlinks
			
			
				pull/182/head
			
			
		 
		
			
				
					
						
						dobunzli
					
					7 years ago
					
						
							committed by
							
								
								GitHub
							
						 
					
				 
				
			 
		 
		
			
				
					
					No known key found for this signature in database
					
						
							GPG Key ID: 4AEE18F83AFDEB23
						
					
				
			
		
		
		
	
		
			
				 1 changed files with 
14 additions and 
0 deletions
			 
			
		 
		
			
				- 
					
					
					 
					README.md
				
 
			
		
		
			
			
			
			
			
			
				
				
					
						
							
								
									
	
		
		
			
				
					| 
						
						
							
								
							
						
						
					 | 
					@ -176,6 +176,20 @@ docker run -d --name bitwarden \ | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					``` | 
					 | 
					 | 
					``` | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					Note that you need to mount ssl files and you need to forward appropriate port. | 
					 | 
					 | 
					Note that you need to mount ssl files and you need to forward appropriate port. | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					
 | 
					 | 
					 | 
					
 | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					 | 
					 | 
					 | 
					Softwares used for getting certs are often using symlinks. If that is the case, both locations need to be accessible to the docker container. | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					 | 
					 | 
					 | 
					Example: certbot will create a folder that contains the needed cert.pem and privacy.pem files in /etc/letsencrypt/live/mydomain/ | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					 | 
					 | 
					 | 
					
 | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					 | 
					 | 
					 | 
					These files are symlinked to ../../archive/mydomain/mykey.pem | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					 | 
					 | 
					 | 
					
 | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					 | 
					 | 
					 | 
					So to use from bitwarden container: | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					 | 
					 | 
					 | 
					
 | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					 | 
					 | 
					 | 
					```sudo docker run -d --name bitwarden \ | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					 | 
					 | 
					 | 
					  -e ROCKET_TLS='{certs="/ssl/live/mydomain/cert.pem",key="/ssl/live/mydomain/privkey.pem"}' \ | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					 | 
					 | 
					 | 
					  -v /etc/letsencrypt/:/ssl/ \ | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					 | 
					 | 
					 | 
					  -v /bw-data/:/data/ \ | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					 | 
					 | 
					 | 
					  -p 443:80 \ | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					 | 
					 | 
					 | 
					  mprasil/bitwarden:latest | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					 | 
					 | 
					 | 
					``` | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					### Enabling WebSocket notifications | 
					 | 
					 | 
					### Enabling WebSocket notifications | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					*Important: This does not apply to the mobile clients, which use push notifications.* | 
					 | 
					 | 
					*Important: This does not apply to the mobile clients, which use push notifications.* | 
				
			
			
		
	
		
		
			
				
					 | 
					 | 
					
 | 
					 | 
					 | 
					
 | 
				
			
			
		
	
	
		
		
			
				
					| 
						
							
								
							
						
						
						
					 | 
					
  |