2 ms·
Seriously??? In that case the real problem is pushing directly from a dev machine to prod. It is simply crazy not to use a staging server. I bet that even if th
by tigershark 10y ago
Seriously???
In that case the real problem is pushing directly from a dev machine to prod.
It is simply crazy not to use a staging server.
I bet that even if the Dev machine has the same OS as prod a lot of shit happens when not using a proper staging server (been there seen that).
So the production problems that you experienced are completely unrelated to the OS on the dev machine.
They are simply caused by the wrong deployment process.
- dkarapetyan 10y agoWe can go around circles for days. The fundamental issue still stands. You are losing time and spending effort working around OS mismatches because your dev machine and your production servers do not line up. Adding a staging server moves the problem one level higher. You will still spend however long it takes to fix whatever mismatch was caused by the differing environments.
- tigershark 10y agoI develop on windows and deploy on Linux. I have done that for more that 10 years and I never found a problem that wouldn't have happened if I developed on Linux. And obviously I always deployed first on test, then on stage and only at the end in production. What kind of problems did you see that happened because of developing on Mac OS instead of Linux? The only ones that I can think of are all caused by a wrong deployment process.
- dkarapetyan 10y agoTry setting up a virtualenv on windows, linux, mac and then tell me there are no issues. Sometimes the versions won't even line up for some libraries because whatever works on windows will not work on linux will not work on mac. Same with ruby gems and npm modules that require compilation.