Skip to content

Instantly share code, notes, and snippets.

@GDXbsv
GDXbsv / README.md
Created July 22, 2023 13:48 — forked from fesor/README.md
Symfony without ORM

Удобный менеджмент миграций с Symfony и Doctrine

Мало кто знает, но что бы работал migration:diff вам не нужно ставить ORM.

Что бы это работало объявим простой сервис:

<?php
@GDXbsv
GDXbsv / Dockerfile
Created March 15, 2023 09:22 — forked from hermanbanken/Dockerfile
Compiling NGINX module as dynamic module for use in docker
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));
@GDXbsv
GDXbsv / README.md
Created April 4, 2019 13:55 — forked from fesor/README.md
Project Structure

Структура проекта

Нагло своровано у angular styleguide и адаптировано под Symfony

LIFT

Структура проекта должны быть интуитивно понятна новому человеку в проекте. Для этого можно воспользоваться принципами LIFT. Согласно им структура проекта должна позволять

  • L - (Locate) легко находить нужный нам код
  • I - (Identify) идентифицировать ответственность с первого взгляда
@GDXbsv
GDXbsv / kube-registry.yaml
Created August 24, 2018 11:34 — forked from coco98/kube-registry.yaml
Docker registry on minikube
apiVersion: v1
kind: ReplicationController
metadata:
name: kube-registry-v0
namespace: kube-system
labels:
k8s-app: kube-registry
version: v0
spec:
replicas: 1
@GDXbsv
GDXbsv / README.md
Created July 3, 2018 21:10 — forked from Ocramius/README.md
`__invoke` vs `function` vs `Closure`
@GDXbsv
GDXbsv / docker_dedicated_filesystem.md
Created June 7, 2018 08:56 — forked from hopeseekr/docker_dedicated_filesystem.md
Putting Docker on its own pseudo filesystem

Docker 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