|
|
|
|
|
|
by viraptor
1316 days ago
|
|
|
> dev environments or if they're developing on their host It's usable for both. Some people go one way some the other. It definitely makes developing in a container on a mac easier if you don't have to worry about compatibility with the target environment. > If you use a container for only your post-development workflow do you ever use separate containers for build and test vs the final packaged application? Yes, most of the time, mostly because the tests require extra dependencies which are not needed in prod. |
|
|
> easier if you don't have to worry about compatibility with the target environment.
I develop on Windows and deploy onto Windows right now, and as we get everything onto .Net Core (and maybe eventually) Linux I'm thinking the same thing. If I can build/test/run my app and service on the same target OS it can only make life better.
Any good guides for this or am I overthinking it and anything on containers will work?