I've been coding for over 20 years now! (WOAH, do I feel old)
I've touched just about every resource imaginable under the Sun (too bad they were bought out by Oracle)
A crazy thought, but trust me from experience, it works, and is the most solid approach I've found.
I develop NOTHING locally.
That's it, it's that simple.
My production environment is FreeBSD with a Jail per application or service.
My development environment is FreeBSD with a Jail per application or service.
I have remote access into the development environment. For instance, a shared folder between dev and my "desktop", so I can edit files "locally", but they're really stored and served from that dev system.
Transitioning from dev to prod becomes effortless, because they're literally the same thing, but neighboring containerized Jails with identical deployments and characteristics.
Even accessing the dev web site goes through the same dns, load balancers, and routing paths. This ensures that the entire ecosystem is always in sight during development.
Hi Vincent, great insight. In fact, I wrote about the same in another article which I just published on Dev. There was an era where dev-prod parity was perfect and WOMM was not an issue. dev.to/roost/the-swing-of-the-work...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
A crazy thought, but trust me from experience, it works, and is the most solid approach I've found.
I develop NOTHING locally.
That's it, it's that simple.
My production environment is FreeBSD with a Jail per application or service.
My development environment is FreeBSD with a Jail per application or service.
I have remote access into the development environment. For instance, a shared folder between dev and my "desktop", so I can edit files "locally", but they're really stored and served from that dev system.
Transitioning from dev to prod becomes effortless, because they're literally the same thing, but neighboring containerized Jails with identical deployments and characteristics.
Even accessing the dev web site goes through the same dns, load balancers, and routing paths. This ensures that the entire ecosystem is always in sight during development.
Hi Vincent, great insight. In fact, I wrote about the same in another article which I just published on Dev. There was an era where dev-prod parity was perfect and WOMM was not an issue. dev.to/roost/the-swing-of-the-work...