pg_db_1 |
pg_db_1 | PostgreSQL Database directory appears to contain a database; Skipping initialization
pg_db_1 |
pg_db_1 | 2023-11-16 20:09:24.713 UTC [1] LOG: starting PostgreSQL 16.0 (Debian 16.0-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
pg_db_1 | 2023-11-16 20:09:24.715 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
pg_db_1 | 2023-11-16 20:09:24.715 UTC [1] LOG: listening on IPv6 address "::", port 5432
pg_db_1 | 2023-11-16 20:09:24.727 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
pg_db_1 | 2023-11-16 20:09:24.811 UTC [30] LOG: database system was shut down at 2023-11-16 20:08:45 UTC
pg_db_1 | 2023-11-16 20:09:24.900 UTC [1] LOG: database system is ready to accept connections
pg_db_1 | 2023-11-16 20:14:24.911 UTC [28] LOG: checkpoint starting: time
pg_db_1 | 2023-11-16 20:14:25.043 UTC [28] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.048 s, sync=0.014 s, total=0.131 s; sync files=2, longest=0.008 s, average=0.007 s; distance=0 kB, estimate=0 kB; lsn=0/191A688, redo lsn=0/191A650
pg_db_1 | 2023-11-16 20:26:28.937 UTC [1] LOG: received fast shutdown request
pg_db_1 | 2023-11-16 20:26:28.957 UTC [1] LOG: aborting any active transactions
pg_db_1 | 2023-11-16 20:26:28.972 UTC [1] LOG: background worker "logical replication launcher" (PID 33) exited with exit code 1
pg_db_1 | 2023-11-16 20:26:28.986 UTC [28] LOG: shutting down
pg_db_1 | 2023-11-16 20:26:29.005 UTC [28] LOG: checkpoint starting: shutdown immediate
php | [16-Nov-2023 20:09:22] NOTICE: fpm is running, pid 1
pg_db_1 | 2023-11-16 20:26:29.145 UTC [28] LOG: checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.051 s, sync=0.001 s, total=0.158 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=0 kB; lsn=0/191A738, redo lsn=0/191A738
pg_db_1 | 2023-11-16 20:26:29.184 UTC [1] LOG: database system is shut down
pg_db_1 |
php | [16-Nov-2023 20:09:22] NOTICE: ready to handle connections
pg_db_1 | PostgreSQL Database directory appears to contain a database; Skipping initialization
pg_db_1 |
pg_db_1 | 2023-11-19 20:40:34.888 UTC [1] LOG: starting PostgreSQL 16.0 (Debian 16.0-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
pg_db_1 | 2023-11-19 20:40:34.889 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
pg_db_1 | 2023-11-19 20:40:34.889 UTC [1] LOG: listening on IPv6 address "::", port 5432
pg_db_1 | 2023-11-19 20:40:34.903 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
pg_db_1 | 2023-11-19 20:40:34.990 UTC [29] LOG: database system was shut down at 2023-11-16 20:26:29 UTC
pg_db_1 | 2023-11-19 20:40:35.149 UTC [1] LOG: database system is ready to accept connections
pg_db_1 | 2023-11-19 20:45:35.056 UTC [27] LOG: checkpoint starting: time
pg_db_1 | 2023-11-19 20:45:35.183 UTC [27] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.040 s, sync=0.012 s, total=0.127 s; sphp | 172.21.0.4 - 23/Nov/2023:19:56:40 +0000 "GET /index.php" 200
php | 172.21.0.4 - 23/Nov/2023:19:56:41 +0000 "GET /index.php" 200
php | 172.21.0.4 - 23/Nov/2023:19:56:41 +0000 "GET /index.php" 200
php | 172.21.0.4 - 23/Nov/2023:19:56:50 +0000 "POST /app.php" 400
php | [23-Nov-2023 19:59:17] NOTICE: Finishing ...
php | [23-Nov-2023 19:59:17] NOTICE: exiting, bye-bye!
adminer_1 | [Thu Nov 16 20:09:22 2023] PHP 7.4.33 Development Server (http://[::]:8080) started
adminer_1 | [Sun Nov 19 20:40:31 2023] PHP 7.4.33 Development Server (http://[::]:8080) started
version: '3'
services:
webserver:
build:
context: ./webserver
dockerfile: Dockerfile
container_name: webserver
image: localapp/webserver
ports:
- "80:80"
volumes:
- ./code:/var/www/my-application.local
networks:
- app-network
php:
build:
context: ./php-fpm
dockerfile: Dockerfile
image: localapp/php
container_name: php
volumes:
- ./code:/var/www/my-application.local
networks:
- app-network
pg_db:
build:
context: ./postgres
dockerfile: Dockerfile
image: postgres
restart: always
environment:
POSTGRES_DB: "db_name"
POSTGRES_USER: "db_user"
POSTGRES_PASSWORD: "db_password"
volumes:
- ./postgres/data:/var/lib/postgresql/data
ports:
- "5432:5432"
networks:
- app-network
adminer:
image: adminer
restart: always
ports:
- "8080:8080"
networks:
app-network:
driver: bridge
на каждое значение свойства "Бренд" Вы создаёте отдельное условие. Очевидный минус - трудоёмкость.
Я бы порекомендовал собрать свой комплексный компонент, который бы работал со следующими ЧПУ:
Дело в том что у вас конфликт с SEF
"SEF_URL_TEMPLATES" => [
"brand" => "#SECTION_CODE_PATH#/brands/#BRAND_CODE#/",
],
ну а если самому тестировать?
проблемы никакой нет - патитаун это ж lazy load
вы изучите как ставят аналитику на Single Page App
Разве на хабре запрещено задавать вопросы по Битриксу?! Для этого тут вроде отдельная тема имеется
К тому-же мой вопрос не столько по Битриксу, сколько по MySQL
И да на форум Битрикса и саппортам модуля, я тоже разумеется написал, но не факт что там, а не здесь с проблемой смогут разобраться быстрее