You’ll most likely want something in front of varnish to terminate TLS/SSL. A CDN can offer this, but for e-commerce it’s best to terminate on the local network of the server. A reverse-proxy that terminates SSL and proxies the HTTP request to varnish is the usual solution. Traefik is a great choice, and can even generate that cert with Let’s Encrypt. You can also wire this up directly with NGNIX, or indirectly with Kubernetes with an Ingress Controller.

Continue reading →

Magento doesn’t store passwords directly, it stores a hash. The same is probably true for WooCommerce. You wouldn’t be able to re-hash the password but you may be able to tweak Woo’s hashing logic to match Magento’s. I would avoid this though, password resets aren’t very burdensome and even give you an excuse to engage with customers. The rest you can probably migrate. www.reddit.com/r/magento…

Magento upgrades are intense, agencies charge hundreds of hours for some. I’d say back out now before you get yourself in over your head. www.reddit.com/r/Magento…

If you’re interested in writing something somewhat useful, take a look at Elasticsearch which has good PHP support and is used on many projects. www.reddit.com/r/PHP/com…

Generally, I think you should build docker images and perform testing and linting against those using the functionality of the pipeline of your favorite git service. You can then trigger deployments with services that leverage docker images, and you feed it the same build images you were testing for deployments. Different applications have different deployment details, but whatever the application, if you can dockerize it then you can generally roll it out with little to no downtime, and it’s usually fairly portable to other services at that point too.

Continue reading →