5 questions about OneBox OS

Cyril, good afternoon! For a few comments I will try to answer your questions. [quote] Zarubin Kirill wrote: We have a boxed version and a rented server. Is it correct that OneBox OS will be uploaded to our server for free (provided that the server has the required OS and its technical parameters are suitable)? [/quote] Yes, provided you have a 50usd/user/year paid upgrade contract. If not, please contact your distributor (who sold boxed licenses to you). If there is no such distributor - let me know, you will be contacted. [quote] Zarubin Kirill wrote: When will the final list of server requirements be available? What do you need to report about the data in the system. [/quote] https://crm-onebox.com/ru/support/server-installation/8899-kakoy-nuzhen-budet-server-dlya-korobochnoy-versii-os/

[quote] Zarubin Kirill wrote: 2. The video explains that the architecture of OneBox OS is different from "standard applications" and this can complicate the work of a system administrator on the client side. Please tell us what kind of difficulties we may face? [/quote] In fact, the technology stack has become a little more complicated. If earlier it was PHP 7+ and modules, MySQL (MariaDB or Percona), Memcached, now it is PHP 7.4+ and modules, MySQL, Memcached, Redis, centos systemctl, nginx, s3. Previously, OneBox was built on the Package Engine, and now it is Eventic 2. These names do not tell anyone anything, it is easier to explain the technical essence: if earlier OneBox is a classic LAMP application, where a request was received to the web server, it passed it to php-fpm, it launched OneBox, the page was given to the web server, everything died. And so in a circle. Now OneBox is a reactive application, where the web server sends a command to OneBox (Eventic), which is already loaded and constantly hanging in memory. It quickly processes the request and renders the page, then waits for the next request. In the world of technology, node js comes closest to this thing. All this adds speed and scalability very much, but it requires that there is always enough memory on the server.

[quote] Zarubin Kirill wrote: 3. Will all the current functionality of the system be available to us, as users (excluding the store - this was mentioned in the video*)? Particularly interested in the possibility of creating processes and the use of fields - the video talked about "transferring" contacts (as an example) to different applications, and that not all applications will be able to accept them. Won't it turn out that due to the separation of the basic (current) functionality into "applications", we will have problems with prescribing logic in processes when we need to use contact/product/process data? Are there any changes in the work of actions in processes (logic of actions, execution priorities, etc.)? We're worried that migrating existing processes (some of which have hundreds of steps) will cause them to malfunction. [/quote] Yes. At the moment, we have transferred all the current functionality to "applications", these applications belong to the OneBox vendor. All paid plans assume that all OneBox vendor apps are included. Later, new applications from third-party developers (vendors) will appear - for an additional fee. payment. There will also be new applications from the OneBox vendor - and they will be included in the package. From the point of view of functionality - it has not become worse, we have not cut anything. Rather, we have greatly changed the interface and control principles, but all automation, actions and processes are the same (even more). Next week the site under OneBox OS will be updated, where everyone will be able to watch it live.

[quote] Zarubin Kirill wrote: 4. Will it be possible to synchronize with an external database? Suppose we have an internal database of the organization on MySQL - can we independently, without involving OneBox employees, set up data exchange between the database and OneBox OS? [/quote] Climbing directly into the OneBox database is better not to, because we are changing the architecture, tables, columns and do not coordinate this with anyone. It is better to take API v2, and get all the data through the OneBox API and pour it into the DBMS and systems you need. Also, all imports / exports remained, although they were visually placed in applications.

Thanks to Cyril for posing questions that concern many, and thanks to Max for answering in detail and accurately