Мало кто знает, но что бы работал migration:diff вам не нужно ставить ORM.
Что бы это работало объявим простой сервис:
<?php| FROM nginx:alpine AS builder | |
| # nginx:alpine contains NGINX_VERSION environment variable, like so: | |
| # ENV NGINX_VERSION 1.15.0 | |
| # Our NCHAN version | |
| ENV NCHAN_VERSION 1.1.15 | |
| # Download sources | |
| RUN wget "http://nginx.org/download/nginx-${NGINX_VERSION}.tar.gz" -O nginx.tar.gz && \ |
| <?php | |
| function file_get_contents(string $pathname): string | |
| { | |
| $result = ''; | |
| $fp = fopen($pathname, 'rb'); | |
| while (!feof($fp)) { | |
| $chunk = 1024; | |
| Fiber::getCurrent() && ($chunk = (Fiber::suspend() ?: 1024)); |
Here is the list of talks that I found most useful to me.
Нагло своровано у angular styleguide и адаптировано под Symfony
Структура проекта должны быть интуитивно понятна новому человеку в проекте. Для этого можно воспользоваться принципами LIFT. Согласно им структура проекта должна позволять
| apiVersion: v1 | |
| kind: ReplicationController | |
| metadata: | |
| name: kube-registry-v0 | |
| namespace: kube-system | |
| labels: | |
| k8s-app: kube-registry | |
| version: v0 | |
| spec: | |
| replicas: 1 |
This gist is about:
Mainly:
function cannot (should not) be used when side-effects occurDocker on BTRFS is very buggy and can result in a fully-unusable system, in that it will completely butcher the underlying BTRFS filesystem in such a way that it uses far more disk space than it needs and can get into a state where it cannot even delete any image, requiring one to take drastic actions up to and including reformatting the entire affected BTRFS root file system.
According to the official Docker documentation:
btrfs requires a dedicated block storage device such as a physical disk. This block device must be formatted for Btrfs and mounted into /var/lib/docker/.
In my experience, you will still run into issues even if you use a dedicated partition. No, it seems it requires a standalone