feat(livekit): add service

.env.infra-example

@@ -11,19 +11,17 @@ MYSQL_ROOT_PASSWORD="nhbnhb22"
 MYSQL_DATABASE="eatvio"
 MYSQL_USER="eatvio_user"
 MYSQL_PASSWORD="eatvio_pass_nhbnhb22"
-<<<<<<< HEAD
-MY_APP_GIT_URL="ssh://git@10.55.5.123:222/alex_chevski/eatvio.git"
-PROD_DB_USER=readonly_user
-PROD_DB_PASS=baexueShosei0AiD
-PROD_DB_FILE="latest-prod-db.sql"
-DEV2_DB_USER=readonly_user
-DEV2_DB_PASS=baexueShosei0AiD
-DEV2_DB_FILE="latest-dev2-db.sql"
-=======
 PROD_DB_USER=some_user
 PROD_DB_PASS=strong_pass
 PROD_DB_FILE="latest-prod-db.sql"
 PROD_DB_HOST="10.nn.n.n"
 PROD_DB_PORT="10nn"
 MY_APP_GIT_URL="ssh://git@10.55.5.123:222/eatvio/eatvio.git"
->>>>>>> eatvio-main
+LIVEKIT_URL="livekit.eatv.io"
+LIVEKIT_WS_URL="livekit.eatv.io"
+LIVEKIT_TURN_DOMAIN="turn.eatv.io"
+LIVEKIT_API_KEY=APITRajpYFYdtk9
+LIVEKIT_API_SECRET=VKCfO954C3OU0IeeXxZ1fiUDx9ZmWtvNNp9fCHRfO2JH
+LIVEKIT_PORT=7880
+LIVEKIT_RTC_TCP_PORT=7881
+LIVEKIT_TURN_UDP_PORT=3478

docker-compose.yml

@@ -23,6 +23,8 @@ services:
     networks:
       - ns-eatvio
     restart: always
+    labels:
+      - "traefik.enable=false"
 
   mysql:
     image: "mysql:8.0"
@@ -37,6 +39,7 @@ services:
       MYSQL_DATABASE: ${MYSQL_DATABASE}
       MYSQL_USER: ${MYSQL_USER}
       MYSQL_PASSWORD: ${MYSQL_PASSWORD}
+      TZ: "Evrope/Moscow"
     ports:
       - "1094:3306"
     labels:
@@ -71,7 +74,7 @@ services:
     working_dir: /application
     environment:
       - TZ=Europe/Moscow
-      - CHOKIDAR_USEPOLLING=true
+      #- CHOKIDAR_USEPOLLING=true
     networks:
       - ns-eatvio
     volumes:
@@ -119,7 +122,7 @@ services:
     labels:
       - "traefik.docker.network=web"
       - "traefik.enable=true"
-      - "traefik.frontend.rule=Host:dev2.eatvio.com,socket.eatvio.com"
+      - "traefik.frontend.rule=Host:wstesting.eatv.io,testing.eatv.io"
       - "traefik.port=80"
       - "traefik.protocol=http"
 
@@ -131,24 +134,80 @@ services:
       - ns-eatvio
 
   typesense:
-    image: typesense/typesense:29.0
+    build: ./phpdocker/typesense
     restart: always
     healthcheck:
-      test:
-        - CMD
-        - wget
-        - "--no-verbose"
-        - "--spider"
-        - "http://localhost:8108/health"
+      test: ["CMD", "curl", "-f", "http://localhost:8108/health"]
     networks:
       - ns-eatvio
     volumes:
       - ./typesense-data:/data
     command: "--data-dir /data --api-key=typesense --enable-cors"
 
+  livekit-redis:
+    image: redis:7-alpine
+    command:
+      [
+        "redis-server",
+        "--appendonly",
+        "no",
+        "--maxmemory",
+        "500mb",
+        "--maxmemory-policy",
+        "allkeys-lru",
+      ]
+    networks:
+      - ns-eatvio
+    volumes:
+      - livekit_redis_data:/data
+    restart: always
+    labels:
+      - "traefik.enable=false"
+
+  livekit:
+    image: livekit/livekit-server:latest
+    depends_on:
+      - livekit-redis
+    networks:
+      - ns-eatvio
+      - web
+    ports:
+      - "${LIVEKIT_PORT:-7880}:7880"
+      - "${LIVEKIT_RTC_TCP_PORT:-7881}:7881"
+      - "50000-50100:50000-50100/udp"
+      - "${LIVEKIT_TURN_UDP_PORT:-3478}:3478/udp"
+    environment:
+      LIVEKIT_CONFIG: |
+        port: 7880
+        log_level: info
+        rtc:
+          tcp_port: 7881
+          port_range_start: 50000
+          port_range_end: 50100
+          use_external_ip: true
+        redis:
+          address: livekit-redis:6379
+        keys:
+          ${LIVEKIT_API_KEY}: ${LIVEKIT_API_SECRET}
+        turn:
+          enabled: true
+          domain: ${LIVEKIT_TURN_DOMAIN}
+          udp_port: 3478
+          # tls_port: 5349
+    restart: always
+    labels:
+      - "traefik.docker.network=web"
+      - "traefik.enable=true"
+      - "traefik.frontend.rule=Host:turn.eatv.io,livekit.eatv.io"
+      - "traefik.port=${LIVEKIT_PORT:-7880}"
+      - "traefik.protocol=http"
+
 networks:
   web:
     external: true
   ns-eatvio:
     external: false
 
+volumes:
+  livekit_redis_data:
+

phpdocker/README.html

@@ -1,4 +1,5 @@
 <html>
+
 <head>
   <title>PHPDocker.io Readme</title>
   <link rel="stylesheet" href="http://yui.yahooapis.com/pure/0.6.0/pure-min.css">
@@ -12,6 +13,7 @@
     }
   </style>
 </head>
+
 <body>
 
   <div class="pure-g">
@@ -21,14 +23,18 @@
 
       <h1>Add to your project</h1>
 
-<p>Simply, unzip the file into your project, this will create <code>docker-compose.yml</code> on the root of your project and a folder
+      <p>Simply, unzip the file into your project, this will create <code>docker-compose.yml</code> on the root of your
+        project and a folder
         named <code>phpdocker</code> containing nginx and php-fpm config for it.</p>
 
-<p>Ensure the webserver config on <code>phpdocker/nginx/nginx.conf</code> is correct for your project. PHPDocker.io will have
-customised this file according to the front controller location relative to the docker-compose file you chose on the
+      <p>Ensure the webserver config on <code>phpdocker/nginx/nginx.conf</code> is correct for your project.
+        PHPDocker.io will have
+        customised this file according to the front controller location relative to the docker-compose file you chose on
+        the
         generator (by default <code>public/index.php</code>).</p>
 
-<p>Note: you may place the files elsewhere in your project. Make sure you modify the locations for the php-fpm dockerfile,
+      <p>Note: you may place the files elsewhere in your project. Make sure you modify the locations for the php-fpm
+        dockerfile,
         the php.ini overrides and nginx config on <code>docker-compose.yml</code> if you do so.</p>
 
       <h1>How to run</h1>
@@ -36,16 +42,20 @@ the php.ini overrides and nginx config on <code>docker-compose.yml</code> if you
       <p>Dependencies:</p>
 
       <ul>
-<li>docker. See <a href="https://docs.docker.com/engine/installation">https://docs.docker.com/engine/installation</a></li>
-<li>docker-compose. See <a href="https://docs.docker.com/compose/install/">docs.docker.com/compose/install</a></li>
+        <li>docker. See <a
+            href="https://docs.docker.com/engine/installation">https://docs.docker.com/engine/installation</a></li>
+        <li>docker-compose. See <a href="https://docs.docker.com/compose/install/">docs.docker.com/compose/install</a>
+        </li>
       </ul>
 
-<p>Once you're done, simply <code>cd</code> to your project and run <code>docker-compose up -d</code>. This will initialise and start all the
+      <p>Once you're done, simply <code>cd</code> to your project and run <code>docker-compose up -d</code>. This will
+        initialise and start all the
         containers, then leave them running in the background.</p>
 
       <h2>Services exposed outside your environment</h2>
 
-<p>You can access your application via <strong><code>localhost</code></strong>. Mailhog and nginx both respond to any hostname, in case you want to
+      <p>You can access your application via <strong><code>localhost</code></strong>. Mailhog and nginx both respond to
+        any hostname, in case you want to
         add your own hostname on your <code>/etc/hosts</code></p>
 
       <table>
@@ -99,42 +109,53 @@ add your own hostname on your <code>/etc/hosts</code></p>
 
       <ul>
         <li>Start containers in the background: <code>docker-compose up -d</code></li>
-<li>Start containers on the foreground: <code>docker-compose up</code>. You will see a stream of logs for every container running.
+        <li>Start containers on the foreground: <code>docker-compose up</code>. You will see a stream of logs for every
+          container running.
           ctrl+c stops containers.</li>
         <li>Stop containers: <code>docker-compose stop</code></li>
         <li>Kill containers: <code>docker-compose kill</code></li>
-<li>View container logs: <code>docker-compose logs</code> for all containers or <code>docker-compose logs SERVICE_NAME</code> for the logs of
+        <li>View container logs: <code>docker-compose logs</code> for all containers or <code>docker-compose logs
+            SERVICE_NAME</code> for the logs of
           all containers in <code>SERVICE_NAME</code>.</li>
-<li>Execute command inside of container: <code>docker-compose exec SERVICE_NAME COMMAND</code> where <code>COMMAND</code> is whatever you want
+        <li>Execute command inside of container: <code>docker-compose exec SERVICE_NAME COMMAND</code> where
+          <code>COMMAND</code> is whatever you want
           to run. Examples:
 
           <ul>
             <li>Shell into the PHP container, <code>docker-compose exec php-fpm bash</code></li>
             <li>Run symfony console, <code>docker-compose exec php-fpm bin/console</code></li>
             <li>Open a mysql shell, <code>docker-compose exec mysql mysql -uroot -pCHOSEN_ROOT_PASSWORD</code></li>
-</ul></li>
+          </ul>
+        </li>
       </ul>
 
       <h1>Application file permissions</h1>
 
-<p>As in all server environments, your application needs the correct file permissions to work properly. You can change the
+      <p>As in all server environments, your application needs the correct file permissions to work properly. You can
+        change the
         files throughout the container, so you won't care if the user exists or has the same ID on your host.</p>
 
       <p><code>docker-compose exec php-fpm chown -R www-data:www-data /application/public</code></p>
 
       <h1>Recommendations</h1>
 
-<p>It's hard to avoid file permission issues when fiddling about with containers due to the fact that, from your OS point
-of view, any files created within the container are owned by the process that runs the docker engine (this is usually
+      <p>It's hard to avoid file permission issues when fiddling about with containers due to the fact that, from your
+        OS point
+        of view, any files created within the container are owned by the process that runs the docker engine (this is
+        usually
         root). Different OS will also have different problems, for instance you can run stuff in containers
-using <code>docker exec -it -u $(id -u):$(id -g) CONTAINER_NAME COMMAND</code> to force your current user ID into the process, but
-this will only work if your host OS is Linux, not mac. Follow a couple of simple rules and save yourself a world of
+        using <code>docker exec -it -u $(id -u):$(id -g) CONTAINER_NAME COMMAND</code> to force your current user ID
+        into the process, but
+        this will only work if your host OS is Linux, not mac. Follow a couple of simple rules and save yourself a world
+        of
         hurt.</p>
 
       <ul>
-<li>Run composer outside of the php container, as doing so would install all your dependencies owned by <code>root</code> within your
+        <li>Run composer outside of the php container, as doing so would install all your dependencies owned by
+          <code>root</code> within your
           vendor folder.</li>
-<li>Run commands (ie Symfony's console, or Laravel's artisan) straight inside of your container. You can easily open a
+        <li>Run commands (ie Symfony's console, or Laravel's artisan) straight inside of your container. You can easily
+          open a
           shell as described above and do your thing from there.</li>
       </ul>
 
@@ -187,11 +208,13 @@ xdebug.start_with_request = yes
       <ul>
         <li>In PHPStorm open Preferences | Languages &amp; Frameworks | PHP | Servers</li>
         <li>Add new server</li>
-<li>The “Name” field should be the same as the parameter “serverName” value in “environment” in docker-compose.yml (i.e. *
+        <li>The “Name” field should be the same as the parameter “serverName” value in “environment” in
+          docker-compose.yml (i.e. *
           Docker* in the example above)</li>
         <li>A value of the "port" field should be the same as first port(before a colon) in "webserver" service in
           docker-compose.yml</li>
-<li>Select "Use path mappings" and set mappings between a path to your project on a host system and the Docker container.</li>
+        <li>Select "Use path mappings" and set mappings between a path to your project on a host system and the Docker
+          container.</li>
         <li>Finally, add “Xdebug helper” extension in your browser, set breakpoints and start debugging</li>
       </ul>
     </div>
@@ -205,4 +228,5 @@ docker-compose.yml</li>
     }
   </script>
 </body>
+
 </html>

phpdocker/README.md

@@ -142,3 +142,4 @@ environment:
 
 
 
+

phpdocker/front-end/Dockerfile

@@ -14,4 +14,3 @@ RUN apt-get update && \
   rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/* /usr/share/doc/*
 
 ENV PATH=node_modules/.bin:$PATH
-

phpdocker/front-end/laravel-worker.conf

@@ -15,9 +15,10 @@ stdout_logfile=/application/storage/logs/worker.log
 stopwaitsecs=3600
 
 [program:php-fpm]
-command=php-fpm8.3 -F
+command=php-fpm8.2 -F
 process_name=%(program_name)s_%(process_num)02d
 stdout_logfile=/dev/stdout
 stdout_logfile_maxbytes=0
 stdderr_logfile=/dev/stderr
 stderr_logfile_maxbytes=0
+

phpdocker/php-fpm/laravel-worker.conf

@@ -15,9 +15,10 @@ stdout_logfile=/application/storage/logs/worker.log
 stopwaitsecs=3600
 
 [program:php-fpm]
-command=php-fpm8.3 -F
+command=php-fpm8.2 -F
 process_name=%(program_name)s_%(process_num)02d
 stdout_logfile=/dev/stdout
 stdout_logfile_maxbytes=0
 stdderr_logfile=/dev/stderr
 stderr_logfile_maxbytes=0
+

phpdocker/php-fpm/php-ini-overrides.ini

@@ -1,2 +1,3 @@
 upload_max_filesize = 100M
 post_max_size = 108M
+

phpdocker/typesense/Dockerfile

@@ -0,0 +1,3 @@
+FROM typesense/typesense:29.0
+USER root
+RUN apt-get update && apt-get install -y curl && rm -rf /var/lib/apt/lists/*

phpdocker/worker/laravel-worker.conf

@@ -53,3 +53,4 @@ numprocs=8
 redirect_stderr=true
 stdout_logfile=/application/storage/logs/scout-worker.log
 stopwaitsecs=3600
+

phpdocker/worker/php-ini-overrides.ini

@@ -1,2 +1,3 @@
 upload_max_filesize = 100M
 post_max_size = 108M
+