Explore >> Select a destination
|
You are here 
|
shyamjos.com | ||
| | | | |
til.simonwillison.net
|
|
| | | | | This recipe for deploying the official datasetteproject/datasette container in Kubernetes just worked for me. It uses an interesting (possibly nasty?) trick to install plugins and download a SQLite database file on container startup, without needing to bake a brand new container image. | |
| | | | |
b.agilob.net
|
|
| | | | | ||
| | | | |
danielrotter.at
|
|
| | | | | It was not trivial to setup nginx with php-fpm to run in separate containers in kubernetes. Therefore I want to explain how I got it to work. | |
| | | | |
sookocheff.com
|
|
| | | Disaster events are one of the biggest challenges that a software organization can face. Natural disasters like earthquakes or floods, technical failures such as power or network loss, and human actions such as unauthorized attacks can disable an entire fleet of systems, leading to complete failure for a business. To deal with disaster scenarios requires a proactive approach to prepare and recover from failure. One of the key benefits of running in the cloud is how easy it is to run workloads in multiple regions. This allows you to deploy a resilient architecture that supports disaster recovery, even in the cases where an entire region is disabled. | ||
