# Alterar a porta do Unicorn de 3000 no desenvolvimento **URL:** \ **Category:** Development\ **Created:** [Agosto 14, 2018, 6:07pm UTC](https://meta.discourse.org/t/change-unicorn-port-from-3000-in-development/94737 "2018-08-14T18:07:53Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\ **Post date:** [Agosto 15, 2018, 12:38am UTC](https://meta.discourse.org/t/change-unicorn-port-from-3000-in-development/94737/5 "2018-08-15T00:38:56Z")
> [@typeoneerror](#): > > Any way to work around this? There are 2 schools of thought when it comes to launching a `rails server` in development. The @sam school of thought, where you want to keep console pristine cause you are a fanatical [puts debugger](https://tenderlovemaking.com/2016/02/05/i-am-a-puts-debuggerer.html). That way you can just add `puts` statements around the app and see the output in the same window you run the server. If you subscribe to @sam’s school of thought you launch your rails server with: ```plaintext bin/unicorn ``` If you want a different port, you run ```plaintext bin/unicorn -p 7777 ``` The other school of thought is the @tgxworld school of thought / Rails official setup. In this case are not a puts debugger and want to see **all the debug rails logs** in the console. If you are like this you would launch unicorn in dev via ```plaintext bin/rails s ``` If you want a custom port you will use ```plaintext bin/rails s -p 7777 ``` Note, I had to push a few fixes to make this post true, so pull latest. --- _[View the full topic](https://meta.discourse.org/t/change-unicorn-port-from-3000-in-development/94737)._