# Switching Puma ↔ Unicorn

**URL:** https://meta.discourse.org/t/switching-puma-unicorn/243363
**Category:** Self-hosting
**Tags:** unsupported-install
**Created:** [October 31, 2022, 9:22am UTC](https://meta.discourse.org/t/switching-puma-unicorn/243363 "2022-10-31T09:22:25Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [October 31, 2022, 9:22am UTC](https://meta.discourse.org/t/switching-puma-unicorn/243363/1 "2022-10-31T09:22:25Z")

</div>

I’m investigating an issue which I’m suspecting may relate to the specific flavour of web server employed.

Discourse supports both Puma and Unicorn web servers, apparently.

What is the most minimal configuration and right way to switch between Puma and Unicorn in a bespoke environment?

For some reason I have two installs, one appears to spin up Puma, one Unicorns, and both have `RAILS_ENV: development`

---

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [October 31, 2022, 9:29am UTC](https://meta.discourse.org/t/switching-puma-unicorn/243363/2 "2022-10-31T09:29:31Z")

</div>

If I recall correctly, `rails s` starts puma and `unicorn_rails` starts unicorn.

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [October 31, 2022, 9:35am UTC](https://meta.discourse.org/t/switching-puma-unicorn/243363/3 "2022-10-31T09:35:06Z")

</div>

![image](https://global.discourse-cdn.com/meta/original/4X/9/2/5/925cf8a35e62886b964a3fb9773049fc930341a7.png)

Appears to lead to on my Ubuntu Dev install?:

 ![image](https://global.discourse-cdn.com/meta/original/4X/7/c/a/7ca6084faa49ecfcba11cdf687ee05b447b993bd.png)

But I’m going to try your other command to switch from Puma, thanks!

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [October 31, 2022, 9:54am UTC](https://meta.discourse.org/t/switching-puma-unicorn/243363/4 "2022-10-31T09:54:11Z")

</div>

I had to use `bundle exec unicorn_rails` within my docker container for some reason (it’s a gem?), but that was extremely useful.

So: I simply cannot recommend Puma when using Ember-CLI in Combo with NGINX as this causes problems.

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [October 31, 2022, 11:58am UTC](https://meta.discourse.org/t/switching-puma-unicorn/243363/5 "2022-10-31T11:58:12Z")

</div>

There is still an open question here, how come in some installs, Unicorn appears to be the default web server employed when issuing `bin/rails s`?

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [November 30, 2022, 11:59am UTC](https://meta.discourse.org/t/switching-puma-unicorn/243363/6 "2022-11-30T11:59:00Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.