Do not set port for puma if it is bound to unix socket (#2289)
Setting port after binding a unix socket puma listen to both of an unix socket and TCP/IP, which is not a desired behavior.
This commit is contained in:
		@@ -3,9 +3,10 @@ threads threads_count, threads_count
 | 
			
		||||
 | 
			
		||||
if ENV['SOCKET'] then
 | 
			
		||||
  bind 'unix://' + ENV['SOCKET']
 | 
			
		||||
else
 | 
			
		||||
  port ENV.fetch('PORT') { 3000 }
 | 
			
		||||
end
 | 
			
		||||
 | 
			
		||||
port        ENV.fetch('PORT') { 3000 }
 | 
			
		||||
environment ENV.fetch('RAILS_ENV') { 'development' }
 | 
			
		||||
workers     ENV.fetch('WEB_CONCURRENCY') { 2 }
 | 
			
		||||
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user