Локальный Сервер/en - История изменений

FuzzyBot: FuzzyBot переименовал страницу Local Server/en в Локальный Сервер/en без оставления перенаправления: Часть переводимой страницы «Local Server».

2026-03-27T06:51:01Z

FuzzyBot переименовал страницу Local Server/en в Локальный Сервер/en без оставления перенаправления: Часть переводимой страницы «Local Server».

← Предыдущая версия	Версия от 09:51, 27 марта 2026
(нет различий)

FuzzyBot: Обновление для соответствия новой версии исходной страницы.

2026-03-27T06:50:04Z

Обновление для соответствия новой версии исходной страницы.

← Предыдущая версия		Версия от 09:50, 27 марта 2026
Строка 14:		Строка 14:
	<span style="color:lightgray">		<span style="color:lightgray">

			<div class="mw-translate-fuzzy">
	==== CPU and RAM Parameters Depending on the Number of Screens ====		==== CPU and RAM Parameters Depending on the Number of Screens ====
	* Up to 200 screens: CPU: 1xXeon (4 cores), RAM: From 8 GB		* Up to 200 screens: CPU: 1xXeon (4 cores), RAM: From 8 GB
Строка 29:		Строка 30:
	* IP: static IP address		* IP: static IP address
	* Internet channel: 3 - 50 Mbps. Depends on the content size.		* Internet channel: 3 - 50 Mbps. Depends on the content size.
			</div>

			==== Hard disk size ====
			* до 200 экранов. От 100 Gb (обеспечивается хранение всего контента, статистика проигрывания контента). Зависит от кол-ва контента.
			* 200 - 500 экранов. От 250 Gb (обеспечивается хранение всего контента, статистика проигрывания контента). Зависит от кол-ва контента.
			* 500 - 2000 экранов. От 500 Gb (обеспечивается хранение всего контента, статистика проигрывания контента). Зависит от кол-ва контента.
			* 2000 - 5000 экранов. От 1 Tb (обеспечивается хранение всего контента, статистика проигрывания контента). Зависит от кол-ва контента.
			* 5000 и более: зависит от требований к платформе под определенные проектные задачи проекта
			==== Настройки сети ====
			* IP: статичный IP адрес
			* Канал Интернет: 3 - 50 Mbps. В зависимости от размера контента

	'''At the time of installation of the local server:'''		'''At the time of installation of the local server:'''

N.Bloshkin в 09:05, 23 декабря 2025

2025-12-23T09:05:26Z

← Предыдущая версия		Версия от 12:05, 23 декабря 2025
Строка 56:		Строка 56:
	* Secondary DNS		* Secondary DNS
	* DNS suffix		* DNS suffix
			== Option 3. Deployment on the Customer's Server, Using Hyper-V Virtualization ==
			A disk with the fully installed platform is exported. The next step is for the network administrator to import the virtual machine into their virtualization environment; after starting the server, a fully functional platform is ready.<br>
			'''Delivery contents:'''
			# Archive with Ubuntu-server, exported from Hyper-V.
			'''Required for image preparation:'''<br>
			* A static IP address (domain name) where the Ubuntu server, personal account, and configured paths to client applications will be deployed;
			* {{Note\|''Optional''\|warn}} complete network settings. During image preparation, a fully ready and functional network interface is created.
			'''Complete network settings include:'''<br>
			# Static IP address
			# Gateway address
			# Network mask
			# Primary DNS
			# Secondary DNS
			# DNS suffix
			'''(Installation of this solution is carried out for an additional fee, please check with your manager)'''
			== '''Hardware Requirements for Installing the Server Application in Clustering Mode''' ==
			Clustering is a method that allows combining several servers into a single system so they can work together and perform common tasks. In this case, these servers are called cluster nodes. The main idea of clustering is to increase the reliability, performance, and availability of the application.<br>
			For the correct operation of the server application in clustering mode, the requirements for each element are specified below:
			Master Node is the control center of the entire cluster. It manages all processes and coordinates the work of the remaining nodes, called worker nodes.
			{\| class="wikitable"
			\|+ Master node CPU
			\|-
			! CPU !! RAM
			\|-
			\| 1xXeon (12 cores) \|\| From 32 GB
			\|}
			Worker Node is the working capacity of the cluster, which directly performs all the tasks and processes necessary for the applications to run. Each Worker Node handles the execution of the container and service on which the application runs.
			{\| class="wikitable"
			\|+ Worker node
			\|-
			! CPU !! RAM
			\|-
			\| 1xXeon (8 cores) \|\| From 24 GB
			\|}
			It is recommended to use/add one "worker node" per 1500-2000 devices.
			S3 storage is a type of cloud storage created for storing large volumes of data. "S3" stands for Simple Storage Service.
			S3 is a unified storage to which servers connect during clustering.
			{\| class="wikitable"
			\|+ S3
			\|-
			! CPU !! RAM
			\|-
			\| 1xXeon (12 cores) \|\| From 24 GB
			\|}
			{{Note\|There is a dependency on the generation of the client application version. The earlier the version of the client application installed, the more it loads the server due to a larger number of requests. Therefore, it is always recommended to have the latest version of the client application.\|warn}}
			== <span id="internalNetwork">Answers to Frequent Questions on Working with the Customer's Internal Network</span> ==
			* Question: Which ports need to be opened?
			* Answer: For the local server (deployed on the customer's infrastructure) to work, port 80 (HTTP server) and port 443 (HTTPS server). For the operation of the SmartPlayer cloud server within network restrictions, request the document from the integrator or SmartPlayer representative.
			---------
			* Question: The direction of port opening on the client application side (it can be IN or OUT)?
			* Answer: It is necessary to open in both directions, IN and OUT.
			---------
			* Question: Description of data exchange between the cloud server and the client application?
			* Answer: The server can work using two protocols: HTTP or HTTPS. When implementing the server using the HTTPS protocol, the customer provides the certificate and independently monitors its renewal after the certificate's expiration date. Communication between the server and client applications is carried out via port 80 (HTTP server) or port 443 (HTTPS server). For interaction, the WebSocket (WS) or WebSocketSecure (WSS) protocol is used, depending on the server configuration. Required ports in the local network: port 80 or port 443, depending on the server configuration. If there is a proxy in the network, packets transmitted between the server and the personal account, client applications must not be modified. The connection opening initialization comes from the client application side.
			---------
			* Question: What is the traffic volume?
			* Answer: Depends on the content played on the devices. In ping-pong mode, traffic consumption is minimal, calculated in kilobytes.
			---------
			* Question: When will traffic exchange occur?
			* Answer: Let's divide traffic into two categories:
			** ping-pong traffic exchange occurs around the clock
			** traffic for receiving content on client applications occurs at the moment it is loaded onto the device. Content loading can be scheduled, for example, set at night when the communication channel is less loaded.

N.Bloshkin в 09:02, 23 декабря 2025

2025-12-23T09:02:36Z

← Предыдущая версия		Версия от 12:02, 23 декабря 2025
Строка 46:		Строка 46:
	*UbuntuServer.ovf - template with settings for the virtual machine		*UbuntuServer.ovf - template with settings for the virtual machine

	~~<div class="mw-translate-fuzzy">~~
	'''To prepare the image, you need:'''		'''To prepare the image, you need:'''
	* Static IP address (domain name) on which the server will be deployed, personal account, configured paths to client applications.		* Static IP address (domain name) on which the server will be deployed, personal account, configured paths to client applications.
Строка 57:		Строка 56:
	* Secondary DNS		* Secondary DNS
	* DNS suffix		* DNS suffix
	~~</div>~~

FuzzyBot: Обновление для соответствия новой версии исходной страницы.

2025-12-23T09:02:08Z

Обновление для соответствия новой версии исходной страницы.

@@ Строка 46: / Строка 46: @@
 *UbuntuServer.ovf - template with settings for the virtual machine
 '''To prepare the image, you need:'''
 * Static IP address (domain name) on which the server will be deployed, personal account, configured paths to client applications.
@@ Строка 56: / Строка 57: @@
 * Secondary DNS
 * DNS suffix
-==Вариант 3. Развертывания на сервере заказчика, с использованием виртуализации Hyper-V ==
+</div>

N.Bloshkin в 09:00, 23 декабря 2025

2025-12-23T09:00:16Z

← Предыдущая версия		Версия от 12:00, 23 декабря 2025
Строка 41:		Строка 41:
	The disc is ejected with the platform fully installed. The network administrator imports the virtual machine into his virtualization environment, after starting the server, a fully operational platform is ready.		The disc is ejected with the platform fully installed. The network administrator imports the virtual machine into his virtualization environment, after starting the server, a fully operational platform is ready.

	~~<div class="mw-translate-fuzzy">~~		'''Delivery contents:'''
	'''~~To prepare the image, you need~~:'''		*UbuntuServer-disk1.vmdk - disk with the installed platform. Approximately 3-4 GB.
	* ~~Static IP address (domain name) on which~~ the ~~server will be deployed, personal account, configured paths to client applications~~.		*UbuntuServer.mf - manifest file
	*~~[Not necessary]~~. ~~Full network settings, when preparing the image, a completely ready~~-~~made working network interface is created~~.		*UbuntuServer.ovf - template with settings for the virtual machine
	~~'''Full network~~ settings ~~include:'''~~
	* Static IP address
	* Gateway address
	* Network mask
	* Primary DNS
	* Secondary DNS
	* DNS suffix
	~~</div>~~

	'''To prepare the image, you need:'''		'''To prepare the image, you need:'''

N.Bloshkin: Новая страница: «'''To prepare the image, you need:''' * Static IP address (domain name) on which the server will be deployed, personal account, configured paths to client applications. [Not necessary]. Full network settings, when preparing the image, a completely ready-made working network interface is created. '''Full network settings include:''' Static IP address * Gateway address * Network mask * Primary DNS * Secondary DNS * DNS suffix»

2025-12-23T08:59:38Z

Новая страница: «'''To prepare the image, you need:''' * Static IP address (domain name) on which the server will be deployed, personal account, configured paths to client applications. *[Not necessary]. Full network settings, when preparing the image, a completely ready-made working network interface is created. '''Full network settings include:''' * Static IP address * Gateway address * Network mask * Primary DNS * Secondary DNS * DNS suffix»

← Предыдущая версия		Версия от 11:59, 23 декабря 2025
Строка 54:		Строка 54:
	</div>		</div>

	'''~~Для подготовки образа требуются~~:'''		'''To prepare the image, you need:'''
	*~~Статичный~~ IP ~~адрес~~(~~доменное имя~~) ~~на котором будет развернут сервер~~, ~~личный кабинет~~, ~~сконфигурированные пути к клиентским приложения~~.		* Static IP address (domain name) on which the server will be deployed, personal account, configured paths to client applications.
	*[~~Необязательно~~]. ~~Полные сетевые настройки~~, ~~при подготовке образа создается полностью готовый работоспособный сетевой интерфейс~~.		*[Not necessary]. Full network settings, when preparing the image, a completely ready-made working network interface is created.
	'''~~Полные сетевые настройки включают в себя~~:'''		'''Full network settings include:'''
	*Static IP address		* Static IP address
	*Gateway address		* Gateway address
	*Network mask		* Network mask
	*Primary DNS		* Primary DNS
	*Secondary DNS		* Secondary DNS
	*DNS suffix		* DNS suffix
	==Вариант 3. Развертывания на сервере заказчика, с использованием виртуализации Hyper-V ==		==Вариант 3. Развертывания на сервере заказчика, с использованием виртуализации Hyper-V ==
	Выгружается диск с полностью установленной платформой. Следующим шагом сетевой администратор импортирует виртуальную машину в свою среду виртуализации, после запуска сервера полностью работоспособная платформа готова.<br>		Выгружается диск с полностью установленной платформой. Следующим шагом сетевой администратор импортирует виртуальную машину в свою среду виртуализации, после запуска сервера полностью работоспособная платформа готова.<br>

N.Bloshkin в 08:59, 23 декабря 2025

2025-12-23T08:59:13Z

← Предыдущая версия		Версия от 11:59, 23 декабря 2025
Строка 39:		Строка 39:
	== Option 2. Deployment on the customer's server, using the vmWare virtualization system. ==		== Option 2. Deployment on the customer's server, using the vmWare virtualization system. ==

	~~<div class="mw-translate-fuzzy">~~		The disc is ejected with the platform fully installed. The network administrator imports the virtual machine into his virtualization environment, after starting the server, a fully operational platform is ready.
	~~'''Scope of delivery:'''~~
	* UbuntuServer-disk1.vmdk - the disk with the installed ~~platform~~. ~~About 3-4 Gb.~~
	* UbuntuServer.mf - manifest file
	* UbuntuServer.ovf - template with settings for a virtual machine
	~~</div>~~

	<div class="mw-translate-fuzzy">		<div class="mw-translate-fuzzy">

N.Bloshkin в 08:58, 23 декабря 2025

2025-12-23T08:58:53Z

← Предыдущая версия		Версия от 11:58, 23 декабря 2025
Строка 37:		Строка 37:

	<span id="Вариант_2._Развертывания_на_сервере_заказчика,_с_использования_системы_виртуализации_vmWare"></span>		<span id="Вариант_2._Развертывания_на_сервере_заказчика,_с_использования_системы_виртуализации_vmWare"></span>
	~~<div class="mw-translate-fuzzy">~~
	== Option 2. Deployment on the customer's server, using the vmWare virtualization system. ==		== Option 2. Deployment on the customer's server, using the vmWare virtualization system. ==
	The disc is ejected with the platform fully installed. The network administrator imports the virtual machine into his virtualization environment, after starting the server, a fully operational platform is ready.
	~~</div>~~

	<div class="mw-translate-fuzzy">		<div class="mw-translate-fuzzy">

N.Bloshkin: Новая страница: «'''At the time of installation of the local server:''' * remote ssh access for user with root rights - used for configuration * remote sftp access for a user with root rights - used to upload files to the server * Internet access - used to install dependencies for the server application * [Optional] first account (e-mail address) is the main account on the local server, if not provided by default root@smartplayer.org»

2025-12-23T08:58:52Z

Новая страница: «'''At the time of installation of the local server:''' * remote ssh access for user with root rights - used for configuration * remote sftp access for a user with root rights - used to upload files to the server * Internet access - used to install dependencies for the server application * [Optional] first account (e-mail address) is the main account on the local server, if not provided by default root@smartplayer.org»

← Предыдущая версия		Версия от 11:58, 23 декабря 2025
Строка 30:		Строка 30:
	* Internet channel: 3 - 50 Mbps. Depends on the content size.		* Internet channel: 3 - 50 Mbps. Depends on the content size.

	'''~~На время установки локального сервера~~:'''		'''At the time of installation of the local server:'''
	*~~удаленный~~ ssh ~~доступ для пользователя с~~ root ~~правами~~ - ~~используется для настройки~~		* remote ssh access for user with root rights - used for configuration
	*~~удаленный~~ sftp ~~доступ для пользователя с~~ root ~~правами~~ - ~~используется для закачки файлов на сервер~~		* remote sftp access for a user with root rights - used to upload files to the server
	*~~доступ в сеть интернет~~ - ~~используется для установки зависимостей для серверного приложения~~		* Internet access - used to install dependencies for the server application
	*[~~Необязательно~~] ~~первая учетка~~ (e-mail ~~адрес~~) ~~- главная учетка на локальном сервере~~, ~~если не предоставлено по умолчанию~~ root@smartplayer.org		* [Optional] first account (e-mail address) is the main account on the local server, if not provided by default root@smartplayer.org

	<span id="Вариант_2._Развертывания_на_сервере_заказчика,_с_использования_системы_виртуализации_vmWare"></span>		<span id="Вариант_2._Развертывания_на_сервере_заказчика,_с_использования_системы_виртуализации_vmWare"></span>