developing with docker is way easier than deploying with docker, but I've done both and I say that deploying with docker is easier than standing up a server.
in production, I provide my own redis and postgres -- I don't try to use docker for that. There are plenty of cloud services, and for the initiated docker doesn't really provide any benefits for these plain services. It shines the most as an application container you can scale up and down and count on being the same every time, and that's how you should use it in production.
(For a web app like Saleor, anyway -- it's no longer true that Docker is wholly unsuitable for production databases, despite that screed we all read a few years ago, but the use case of the people in this room is probably more "go get a Postgres and Redis instance from AWS or on your Linode, make sure they are securely reachable from your container, and set the environment variables at runtime with
docker run -e DATABASE_URL=postgresql://my.special.db/blabla/hope_i_got_this_fake_uri_right)
The biggest learning curve for me after Docker was Celery. I have been unsuccessfully trying to use the worker with
--beat in the docker-compose image for Celery, because I want to run scheduled tasks. I think I just realized I can get the exact same effect with a crontab in the application image, so. Docker still comes in handy.
Docker rules. All the configuration and environment the app needs to run is in the docker image. My current client isn't THAT technical, and this could be a huge headache for us on delivery, and I'm definitely not going back to hand-wiring environments for each project ever again. Learn it, it's mature enough now, we've been skeptical since 2015. Engineers will nod in approval at the internals, too -- at the core it's a wrapper around Linux kernel functionality, it's like a chroot on steroids. It's fine and amazing, use it. The extra troubleshooting layer it represents is worth the troubleshooting layers it eliminates.
(But yeah, I hate this job. Relearning the whole stack every 3-5 years sucks.)
settings.PLUGINSlist as an empty object which means that Saleor doesn't use any plugin. It was changed one or two weeks ago. Now, Vatlayer and Avalara are included by default. Dashboard2.0 has a settings section to provide all mandatory data for plugins and enable/disable plugins.
hi. i have saleor on my ubuntu instance and saleor-storefront on netlify. things seem fine on the sample site but the product page on storefront doesn't load. console displays a TypeError. i wrote details about it here: https://stackoverflow.com/questions/58019716/saleor-frontend-product-page-not-loading-due-to-typeerror
can someone point me in the right direction to solve this? thanks.