Explore >> Select a destination
|
You are here 
|
major.io | ||
| | | | |
vsevolod.net
|
|
| | | | | Vsevolod Solovyov's blog | |
| | | | |
antzucaro.com
|
|
| | | | | The Scenario Let's suppose you are modeling a database in MySQL 5.5. Based on your knowledge of the requirements for the application behind this database you can guess which of the tables within it are going to be huge. For those huge tables you want to plan ahead to make sure that you can scale out your data such that you have less headaches in the future. Here's the catch: you want to keep it simple until it comes time to scale out. | |
| | | | |
dnsmichi.at
|
|
| | | | | Ghost v5 has been released, the underlying stack for this website, running in containers. In this blog post, I'll look into the upgrade to the latest v4, MySQL8 collation changes, database migrations, and the final v5 upgrade. There are a few required steps for v5: * Upgrade to the latest v4 | |
| | | | |
davquar.it
|
|
| | | A GitHub Action is the automatic execution of a job, after a specified trigger on a GitHub repository. For example, let's say that we want to run a linter on each new commit, we can create a GitHub action to do it. In this post we'll see a workflow to automatically deploy a Hugo site on GitHub Pages. | ||
