Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Two or more buffalo app in the same windows server #1603

ajoses opened this Issue Feb 23, 2019 · 0 comments


None yet
1 participant
Copy link

ajoses commented Feb 23, 2019


I'm putting several buffalo apps in a windows server 2008 machine, but each one has it's own configuration.
I tried using .env files for each application but after initializing the first one, the second take the environment variables setted by the first one.

Steps to Reproduce the Problem

Install in the same windows machine two application in different directorys and each one with the .env. Each application .evn has the "PORT" variable configured with different values (for example one with 3000 and the other with 3001).
Run the first application, and it run correctly.
Run the second and get an error of port already used or sometimes it exit after trying to bind to the port, because it takes the same port of the first application.

Expected Behavior

I want each application take it's own configuration without being affected by the other.

Actual Behavior

The second application take the parameters setted by the first one, causing an error in the second application because the port is already taken.


Right now my "solution" was to put a prefix by application to the variables in order to get them running side by side. For example for the "PORT" I changed to "FP_PORT".

I know that in Linux I can use Docker, however right now I'm attached to a windows server 2008.

I want to know if this is the correct behavior or what I need to do in order to get them running without the prefix in the variables.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.