Omnysh #4
Omnysh #4
Conversation
KeyMatrix
added
bug
|
Test |
github-project-automation
bot
moved this to Done
in [COPY] @KeyMatrix's untitled project
|
There was a problem hiding this comment.
Pull Request Overview
This PR introduces a new shell script (OmniCore.sh) that automates dependency installations for Python and Node.js, launches various background services, and sets up CI/CD workflow templates and documentation updates.
- Adds automated dependency installation for Python (via requirements.txt) and Node.js (via package.json).
- Launches several application services (TreeOM AppServer, WebSocket server, Discord integration, Live Web interface, and monitoring).
- Creates a CI/CD workflow template and appends updates to the README when required.
| sleep 2 | ||
| echo "🛠️ [7] Запуск мониторинга структуры..." | ||
| python3 treeom_monitor.py & | ||
|
|
||
| sleep 2 |
There was a problem hiding this comment.
Using a fixed sleep duration to wait for background processes to start may lead to unpredictable behavior. Consider using a polling mechanism or checking for service readiness instead of a fixed delay.
| sleep 2 | |
| echo "🛠️ [7] Запуск мониторинга структуры..." | |
| python3 treeom_monitor.py & | |
| sleep 2 | |
| echo "⏳ Ожидание запуска TreeOM AppServer..." | |
| for i in {1..10}; do | |
| if pgrep -f "TreeOM_AppServer.py" > /dev/null; then | |
| echo "✔️ TreeOM AppServer запущен." | |
| break | |
| fi | |
| sleep 1 | |
| done | |
| echo "🛠️ [7] Запуск мониторинга структуры..." | |
| python3 treeom_monitor.py & | |
| echo "⏳ Ожидание запуска WebSocket-сервера..." | |
| for i in {1..10}; do | |
| if pgrep -f "websocket_server.js" > /dev/null; then | |
| echo "✔️ WebSocket-сервер запущен." | |
| break | |
| fi | |
| sleep 1 | |
| done |
| else | ||
| echo "⚠️ Workflow не найден! Создаю шаблон..." | ||
| mkdir -p .github/workflows | ||
| cp ./templates/ci_template.yml .github/workflows/main.yml |
There was a problem hiding this comment.
The script attempts to copy a CI template without verifying that './templates/ci_template.yml' exists. Consider adding a check to ensure the template file is present before copying.
| cp ./templates/ci_template.yml .github/workflows/main.yml | |
| if [ -f "./templates/ci_template.yml" ]; then | |
| cp ./templates/ci_template.yml .github/workflows/main.yml | |
| else | |
| echo "❌ Шаблон CI/CD pipeline (./templates/ci_template.yml) не найден. Проверьте наличие файла." | |
| fi |
There was a problem hiding this comment.
Pull Request Overview
This PR introduces a new shell script to automate dependency installation, service startup, and CI/CD workflow setup.
- Sets up Python and Node.js dependencies
- Launches multiple background services (TreeOM AppServer, WebSocket server, Discord bot, live web interface, and monitoring)
- Verifies or creates a GitHub Actions workflow and updates the README
| sleep 2 | ||
| echo "🛠️ [7] Запуск мониторинга структуры..." | ||
| python3 treeom_monitor.py & | ||
|
|
||
| sleep 2 |
There was a problem hiding this comment.
Using fixed sleep durations to wait for background processes may be brittle. Consider implementing a loop to check for process readiness or using 'wait' to ensure proper synchronization.
| sleep 2 | |
| echo "🛠️ [7] Запуск мониторинга структуры..." | |
| python3 treeom_monitor.py & | |
| sleep 2 | |
| echo "⏳ Ожидание запуска TreeOM AppServer..." | |
| timeout 10 bash -c 'until pgrep -f "TreeOM_AppServer.py" > /dev/null; do sleep 1; done' || { echo "❌ TreeOM AppServer не запустился!"; exit 1; } | |
| echo "🛠️ [7] Запуск мониторинга структуры..." | |
| python3 treeom_monitor.py & | |
| echo "⏳ Ожидание запуска treeom_monitor.py..." | |
| timeout 10 bash -c 'until pgrep -f "treeom_monitor.py" > /dev/null; do sleep 1; done' || { echo "❌ treeom_monitor.py не запустился!"; exit 1; } |
| python3 TreeOM_AppServer.py & | ||
|
|
||
| echo "🌐 [4] Запуск WebSocket-сервера..." | ||
| node websocket_server.js & | ||
|
|
||
| echo "💎 [5] Запуск Discord-интеграции..." | ||
| node discord_bot.js & | ||
|
|
||
| echo "🧠 [6] Запуск Live Web-интерфейса..." | ||
| npx live-server --port=8080 & | ||
|
|
||
| sleep 2 | ||
| echo "🛠️ [7] Запуск мониторинга структуры..." | ||
| python3 treeom_monitor.py & |
There was a problem hiding this comment.
[nitpick] Consider capturing the process ID of this background process to facilitate error handling and proper cleanup later.
| python3 TreeOM_AppServer.py & | |
| echo "🌐 [4] Запуск WebSocket-сервера..." | |
| node websocket_server.js & | |
| echo "💎 [5] Запуск Discord-интеграции..." | |
| node discord_bot.js & | |
| echo "🧠 [6] Запуск Live Web-интерфейса..." | |
| npx live-server --port=8080 & | |
| sleep 2 | |
| echo "🛠️ [7] Запуск мониторинга структуры..." | |
| python3 treeom_monitor.py & | |
| python3 TreeOM_AppServer.py & TREEOM_PID=$! | |
| echo "🌐 [4] Запуск WebSocket-сервера..." | |
| node websocket_server.js & WEBSOCKET_PID=$! | |
| echo "💎 [5] Запуск Discord-интеграции..." | |
| node discord_bot.js & DISCORD_PID=$! | |
| echo "🧠 [6] Запуск Live Web-интерфейса..." | |
| npx live-server --port=8080 & LIVE_SERVER_PID=$! | |
| sleep 2 | |
| echo "🛠️ [7] Запуск мониторинга структуры..." | |
| python3 treeom_monitor.py & MONITOR_PID=$! |
There was a problem hiding this comment.
Pull Request Overview
This PR adds a new shell script to set up dependencies and launch multiple services for MetaForge activation.
- Adds Python and Node.js dependency installation logic
- Starts several background services including WebSocket and Discord integrations
- Creates a GitHub Actions workflow template if missing
Comments suppressed due to low confidence (2)
OmniCore.sh:31
- Using a fixed sleep interval to wait for process initialization may lead to race conditions on slower systems. Consider implementing a check to ensure each process is ready before proceeding.
sleep 2
OmniCore.sh:42
- Ensure that the template file './templates/ci_template.yml' exists before copying it to prevent potential failures during the CI/CD workflow setup.
cp ./templates/ci_template.yml .github/workflows/main.yml
|
This pull request introduces a new Key Changes:Automation of environment setup:
Application component initialization:
Monitoring and CI/CD setup:
Documentation update:
|
There was a problem hiding this comment.
Pull Request Overview
This PR introduces a new Bash script (OmniCore.sh) designed to set up dependencies and launch various application services including Python, Node.js, and Discord integrations.
- Initializes and installs Python and Node.js dependencies.
- Launches multiple application services in the background.
- Sets up a basic CI/CD workflow and updates the README.md.
Comments suppressed due to low confidence (1)
OmniCore.sh:20
- [nitpick] There is a naming inconsistency: 'TreeOM_AppServer.py' is capitalized differently from 'treeom_monitor.py'. Consider standardizing the file naming conventions to avoid confusion.
python3 TreeOM_AppServer.py &
| python3 TreeOM_AppServer.py & | ||
|
|
||
| echo "🌐 [4] Запуск WebSocket-сервера..." | ||
| node websocket_server.js & | ||
|
|
||
| echo "💎 [5] Запуск Discord-интеграции..." | ||
| node discord_bot.js & | ||
|
|
||
| echo "🧠 [6] Запуск Live Web-интерфейса..." | ||
| npx live-server --port=8080 & | ||
|
|
||
| sleep 2 | ||
| echo "🛠️ [7] Запуск мониторинга структуры..." | ||
| python3 treeom_monitor.py & |
There was a problem hiding this comment.
Multiple background processes are launched without any error handling or status monitoring. Consider adding checks or a monitoring mechanism to ensure these processes start successfully.
| python3 TreeOM_AppServer.py & | |
| echo "🌐 [4] Запуск WebSocket-сервера..." | |
| node websocket_server.js & | |
| echo "💎 [5] Запуск Discord-интеграции..." | |
| node discord_bot.js & | |
| echo "🧠 [6] Запуск Live Web-интерфейса..." | |
| npx live-server --port=8080 & | |
| sleep 2 | |
| echo "🛠️ [7] Запуск мониторинга структуры..." | |
| python3 treeom_monitor.py & | |
| python3 TreeOM_AppServer.py & | |
| APP_SERVER_PID=$! | |
| if ! kill -0 $APP_SERVER_PID 2>/dev/null; then | |
| echo "❌ Ошибка: TreeOM AppServer не удалось запустить." | |
| exit 1 | |
| fi | |
| echo "🌐 [4] Запуск WebSocket-сервера..." | |
| node websocket_server.js & | |
| WEBSOCKET_SERVER_PID=$! | |
| if ! kill -0 $WEBSOCKET_SERVER_PID 2>/dev/null; then | |
| echo "❌ Ошибка: WebSocket-сервер не удалось запустить." | |
| exit 1 | |
| fi | |
| echo "💎 [5] Запуск Discord-интеграции..." | |
| node discord_bot.js & | |
| DISCORD_BOT_PID=$! | |
| if ! kill -0 $DISCORD_BOT_PID 2>/dev/null; then | |
| echo "❌ Ошибка: Discord-интеграцию не удалось запустить." | |
| exit 1 | |
| fi | |
| echo "🧠 [6] Запуск Live Web-интерфейса..." | |
| npx live-server --port=8080 & | |
| LIVE_SERVER_PID=$! | |
| if ! kill -0 $LIVE_SERVER_PID 2>/dev/null; then | |
| echo "❌ Ошибка: Live Web-интерфейс не удалось запустить." | |
| exit 1 | |
| fi | |
| sleep 2 | |
| echo "🛠️ [7] Запуск мониторинга структуры..." | |
| python3 treeom_monitor.py & | |
| MONITOR_PID=$! | |
| if ! kill -0 $MONITOR_PID 2>/dev/null; then | |
| echo "❌ Ошибка: Мониторинг структуры не удалось запустить." | |
| exit 1 | |
| fi |
|
This pull request introduces a new script, Dependency Management:
Service Initialization:
CI/CD Workflow Setup:
Documentation Update:
|
There was a problem hiding this comment.
Pull Request Overview
This PR adds a new Bash script (OmniCore.sh) to automate environment setup, service launch, CI workflow initialization, and README updates for the OmniCore project.
- Introduces
OmniCore.shfor dependency installation (Python & Node.js) and background process startup - Adds automatic creation of GitHub Actions workflow from a template if missing
- Appends a MetaForge section to
README.mdif not already present
| @@ -0,0 +1,51 @@ | |||
| #!/bin/bash | |||
There was a problem hiding this comment.
Switch to a more portable shebang (e.g., #!/usr/bin/env bash) to ensure the script works across different environments.
| #!/bin/bash | |
| #!/usr/bin/env bash |
| @@ -0,0 +1,51 @@ | |||
| #!/bin/bash | |||
|
|
|||
There was a problem hiding this comment.
Consider adding set -euo pipefail after the shebang to fail fast on errors, undefined variables, or pipe failures.
| pip install -r requirements.txt || pip3 install -r requirements.txt | ||
| else | ||
| echo "⚠️ Файл requirements.txt не найден. Создаю..." | ||
| echo -e "requests\nwebsocket-client" > requirements.txt | ||
| pip install -r requirements.txt || pip3 install -r requirements.txt |
There was a problem hiding this comment.
[nitpick] To avoid ambiguity, explicitly call pip3 first for Python 3 environments and fall back to pip only if needed.
| pip install -r requirements.txt || pip3 install -r requirements.txt | |
| else | |
| echo "⚠️ Файл requirements.txt не найден. Создаю..." | |
| echo -e "requests\nwebsocket-client" > requirements.txt | |
| pip install -r requirements.txt || pip3 install -r requirements.txt | |
| pip3 install -r requirements.txt || pip install -r requirements.txt | |
| else | |
| echo "⚠️ Файл requirements.txt не найден. Создаю..." | |
| echo -e "requests\nwebsocket-client" > requirements.txt | |
| pip3 install -r requirements.txt || pip install -r requirements.txt |
| sleep 2 | ||
| echo "🛠️ [7] Запуск мониторинга структуры..." | ||
| python3 treeom_monitor.py & | ||
|
|
||
| sleep 2 |
There was a problem hiding this comment.
Using fixed sleeps can lead to race conditions; consider checking service health or logs instead of a fixed delay.
| sleep 2 | |
| echo "🛠️ [7] Запуск мониторинга структуры..." | |
| python3 treeom_monitor.py & | |
| sleep 2 | |
| echo "⏳ Ожидание запуска TreeOM AppServer..." | |
| while ! netstat -tuln | grep -q ':5000'; do | |
| sleep 0.5 | |
| done | |
| echo "🛠️ [7] Запуск мониторинга структуры..." | |
| python3 treeom_monitor.py & | |
| echo "⏳ Ожидание запуска TreeOM Monitor..." | |
| while ! pgrep -f treeom_monitor.py > /dev/null; do | |
| sleep 0.5 | |
| done |
| echo "🛠️ [7] Запуск мониторинга структуры..." | ||
| python3 treeom_monitor.py & | ||
|
|
||
| sleep 2 |
There was a problem hiding this comment.
This second fixed delay duplicates the earlier one; consider consolidating waits or replacing with readiness checks.
| sleep 2 | |
| while ! pgrep -f "treeom_monitor.py" > /dev/null; do | |
| sleep 1 | |
| done |
| cp ./templates/ci_template.yml .github/workflows/main.yml | ||
| fi | ||
|
|
||
| echo "📘 [9] Обновление README.md..." |
There was a problem hiding this comment.
If README.md does not exist, grep will fail; you may want to ensure the file exists or create it before grepping.
| echo "📘 [9] Обновление README.md..." | |
| echo "📘 [9] Обновление README.md..." | |
| if [ ! -f "README.md" ]; then | |
| echo "⚠️ Файл README.md не найден. Создаю пустой файл..." | |
| touch README.md | |
| fi |
There was a problem hiding this comment.
Pull Request Overview
This PR adds a new shell script (OmniCore.sh) to automate the setup and startup of various services including Python and Node.js dependencies, multiple background services, CI/CD workflow setup, and README updates.
- Introduces dependency installation for Python and Node.js
- Automates the launch of several backend services as background processes
- Adds CI/CD pipeline verification and conditional README updates
Comments suppressed due to low confidence (1)
OmniCore.sh:46
- Before checking for 'MetaForge' in README.md, verify that README.md exists to avoid errors when the file is missing. Consider adding a file existence check or creating README.md if it does not exist.
if ! grep -q "MetaForge" README.md; then
| sleep 2 | ||
| echo "🛠️ [7] Запуск мониторинга структуры..." | ||
| python3 treeom_monitor.py & | ||
|
|
||
| sleep 2 |
There was a problem hiding this comment.
Using fixed sleep intervals to wait for background processes may be unreliable. Consider using process checks or the 'wait' command to ensure background tasks are properly started before proceeding.
| sleep 2 | |
| echo "🛠️ [7] Запуск мониторинга структуры..." | |
| python3 treeom_monitor.py & | |
| sleep 2 | |
| while ! nc -z localhost 8080; do | |
| sleep 1 | |
| done | |
| echo "🛠️ [7] Запуск мониторинга структуры..." | |
| python3 treeom_monitor.py & | |
| while ! pgrep -f "treeom_monitor.py" > /dev/null; do | |
| sleep 1 | |
| done |
There was a problem hiding this comment.
Pull Request Overview
Adds a new shell script to automate environment setup, start multiple services in the background, verify CI/CD workflow, and update the README.
- Introduces
OmniCore.shfor dependency installation (Python & Node), service launches, CI pipeline check, and README update. - Implements default templates when key files are missing.
- Appends a “MetaForge Activated” section to the README if not already present.
Comments suppressed due to low confidence (1)
OmniCore.sh:46
- The script refers to “MetaForge” here, but the project name (Omnysh/OmniCore) is inconsistent. Update this string to match the actual project name.
if ! grep -q "MetaForge" README.md; then
| pip install -r requirements.txt || pip3 install -r requirements.txt | ||
| else | ||
| echo "⚠️ Файл requirements.txt не найден. Создаю..." | ||
| echo -e "requests\nwebsocket-client" > requirements.txt |
There was a problem hiding this comment.
[nitpick] Using echo -e is not portable across all shells. Consider using printf '%s ' "requests" "websocket-client" > requirements.txt for consistent behavior.
| echo -e "requests\nwebsocket-client" > requirements.txt | |
| printf '%s\n' "requests" "websocket-client" > requirements.txt |
| @@ -0,0 +1,51 @@ | |||
| #!/bin/bash | |||
There was a problem hiding this comment.
Consider adding set -euo pipefail after the shebang to ensure the script exits on errors, treats unset variables as failures, and fails in pipelines.
| python3 TreeOM_AppServer.py & | ||
|
|
||
| echo "🌐 [4] Запуск WebSocket-сервера..." | ||
| node websocket_server.js & | ||
|
|
||
| echo "💎 [5] Запуск Discord-интеграции..." | ||
| node discord_bot.js & | ||
|
|
||
| echo "🧠 [6] Запуск Live Web-интерфейса..." | ||
| npx live-server --port=8080 & | ||
|
|
||
| sleep 2 | ||
| echo "🛠️ [7] Запуск мониторинга структуры..." | ||
| python3 treeom_monitor.py & |
There was a problem hiding this comment.
[nitpick] Multiple background processes are started without tracking or cleanup. Consider capturing PIDs and using a trap to ensure processes are terminated cleanly on script exit.
| python3 TreeOM_AppServer.py & | |
| echo "🌐 [4] Запуск WebSocket-сервера..." | |
| node websocket_server.js & | |
| echo "💎 [5] Запуск Discord-интеграции..." | |
| node discord_bot.js & | |
| echo "🧠 [6] Запуск Live Web-интерфейса..." | |
| npx live-server --port=8080 & | |
| sleep 2 | |
| echo "🛠️ [7] Запуск мониторинга структуры..." | |
| python3 treeom_monitor.py & | |
| python3 TreeOM_AppServer.py & PIDS="$PIDS $!" | |
| echo "🌐 [4] Запуск WebSocket-сервера..." | |
| node websocket_server.js & PIDS="$PIDS $!" | |
| echo "💎 [5] Запуск Discord-интеграции..." | |
| node discord_bot.js & PIDS="$PIDS $!" | |
| echo "🧠 [6] Запуск Live Web-интерфейса..." | |
| npx live-server --port=8080 & PIDS="$PIDS $!" | |
| sleep 2 | |
| echo "🛠️ [7] Запуск мониторинга структуры..." | |
| python3 treeom_monitor.py & PIDS="$PIDS $!" |
| if [ -f "requirements.txt" ]; then | ||
| pip install -r requirements.txt || pip3 install -r requirements.txt | ||
| else | ||
| echo "⚠️ Файл requirements.txt не найден. Создаю..." | ||
| echo -e "requests\nwebsocket-client" > requirements.txt | ||
| pip install -r requirements.txt || pip3 install -r requirements.txt |
There was a problem hiding this comment.
[nitpick] Falling back to pip3 after pip may mask which interpreter is being used. It might be clearer to detect the Python version first or consistently use one installer.
| if [ -f "requirements.txt" ]; then | |
| pip install -r requirements.txt || pip3 install -r requirements.txt | |
| else | |
| echo "⚠️ Файл requirements.txt не найден. Создаю..." | |
| echo -e "requests\nwebsocket-client" > requirements.txt | |
| pip install -r requirements.txt || pip3 install -r requirements.txt | |
| # Detect Python version and set the appropriate pip command | |
| if command -v python3 &>/dev/null; then | |
| PYTHON_CMD="python3" | |
| PIP_CMD="pip3" | |
| elif command -v python &>/dev/null; then | |
| PYTHON_CMD="python" | |
| PIP_CMD="pip" | |
| else | |
| echo "❌ Python не установлен. Установите Python и повторите попытку." | |
| exit 1 | |
| fi | |
| if [ -f "requirements.txt" ]; then | |
| $PIP_CMD install -r requirements.txt | |
| else | |
| echo "⚠️ Файл requirements.txt не найден. Создаю..." | |
| echo -e "requests\nwebsocket-client" > requirements.txt | |
| $PIP_CMD install -r requirements.txt |
There was a problem hiding this comment.
Pull Request Overview
Adds a new Bash script (OmniCore.sh) to automate dependency installation, service startup, CI/CD workflow setup, and README updates.
- Introduces steps for Python and Node.js dependencies installation.
- Launches multiple server processes and checks CI/CD configuration.
- Updates or creates
.github/workflows/main.ymland appends a README section.
Comments suppressed due to low confidence (1)
OmniCore.sh:51
- The script is named
OmniCore.sh, but this message referencesMetaForge. Update naming to keep consistency across script and output.
echo "✅ Все потоки активированы. MetaForge в резонансе."
| @@ -0,0 +1,51 @@ | |||
| #!/bin/bash | |||
There was a problem hiding this comment.
[nitpick] Consider adding set -euo pipefail after the shebang to enable strict error handling and avoid silent failures.
| cp ./templates/ci_template.yml .github/workflows/main.yml | ||
| fi | ||
|
|
||
| echo "📘 [9] Обновление README.md..." |
There was a problem hiding this comment.
Running grep on README.md will error out if the file doesn't exist. Add a check to create README.md first or guard the grep with a file-existence test.
| echo "📘 [9] Обновление README.md..." | |
| echo "📘 [9] Обновление README.md..." | |
| if [ ! -f "README.md" ]; then | |
| echo "⚠️ Файл README.md не найден. Создаю..." | |
| touch README.md | |
| fi |
There was a problem hiding this comment.
Pull Request Overview
Adds a new Bash orchestration script to automate environment setup, service launches, CI/CD pipeline initialization, and README updates.
- Installs Python and Node.js dependencies, creating defaults if missing
- Launches multiple background services (AppServer, WebSocket, Discord bot, monitor) with static delays
- Initializes GitHub Actions workflow template and appends a marker to README
| @@ -0,0 +1,51 @@ | |||
| #!/bin/bash | |||
There was a problem hiding this comment.
Add set -euo pipefail after the shebang to enable fail-fast behavior and catch errors in piped commands.
| pip install -r requirements.txt || pip3 install -r requirements.txt | ||
| else | ||
| echo "⚠️ Файл requirements.txt не найден. Создаю..." | ||
| echo -e "requests\nwebsocket-client" > requirements.txt | ||
| pip install -r requirements.txt || pip3 install -r requirements.txt |
There was a problem hiding this comment.
Consider exiting the script if neither pip nor pip3 succeeds to avoid continuing with missing dependencies.
| pip install -r requirements.txt || pip3 install -r requirements.txt | |
| else | |
| echo "⚠️ Файл requirements.txt не найден. Создаю..." | |
| echo -e "requests\nwebsocket-client" > requirements.txt | |
| pip install -r requirements.txt || pip3 install -r requirements.txt | |
| pip install -r requirements.txt || pip3 install -r requirements.txt || { echo "❌ Ошибка: Не удалось установить зависимости. Убедитесь, что pip или pip3 установлены и настроены."; exit 1; } | |
| else | |
| echo "⚠️ Файл requirements.txt не найден. Создаю..." | |
| echo -e "requests\nwebsocket-client" > requirements.txt | |
| pip install -r requirements.txt || pip3 install -r requirements.txt || { echo "❌ Ошибка: Не удалось установить зависимости. Убедитесь, что pip или pip3 установлены и настроены."; exit 1; } |
| node discord_bot.js & | ||
|
|
||
| echo "🧠 [6] Запуск Live Web-интерфейса..." | ||
| npx live-server --port=8080 & |
There was a problem hiding this comment.
[nitpick] Extract the hardcoded port 8080 into a variable or parameter to make the script more configurable.
| npx live-server --port=8080 & | |
| npx live-server --port=$LIVE_SERVER_PORT & |
| echo "🧠 [6] Запуск Live Web-интерфейса..." | ||
| npx live-server --port=8080 & | ||
|
|
||
| sleep 2 |
There was a problem hiding this comment.
Using a fixed sleep introduces potential race conditions; consider polling the service or checking the port readiness instead of a static delay.
| echo "🛠️ [7] Запуск мониторинга структуры..." | ||
| python3 treeom_monitor.py & | ||
|
|
||
| sleep 2 |
There was a problem hiding this comment.
Replace the static delay with an active readiness check (e.g., nc or curl) to confirm the monitor process is accepting connections.
| sleep 2 | |
| echo "⏳ Ожидание готовности treeom_monitor.py..." | |
| for i in {1..10}; do | |
| if nc -z localhost 5000; then | |
| echo "✔️ treeom_monitor.py готов." | |
| break | |
| fi | |
| sleep 1 | |
| done | |
| if ! nc -z localhost 5000; then | |
| echo "❌ Ошибка: treeom_monitor.py не готов после 10 секунд ожидания." | |
| exit 1 | |
| fi |
| else | ||
| echo "⚠️ Workflow не найден! Создаю шаблон..." | ||
| mkdir -p .github/workflows | ||
| cp ./templates/ci_template.yml .github/workflows/main.yml |
There was a problem hiding this comment.
Verify the existence of templates/ci_template.yml before copying to prevent errors when the source file is missing.
| cp ./templates/ci_template.yml .github/workflows/main.yml | |
| if [ -f "./templates/ci_template.yml" ]; then | |
| cp ./templates/ci_template.yml .github/workflows/main.yml | |
| else | |
| echo "❌ Шаблон CI/CD pipeline (ci_template.yml) не найден. Проверьте наличие файла в папке templates." | |
| fi |
Sh