ciplink-server 0.3.5

One server per site that owns the PLC connections and serves tag values over a WebSocket
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46

//! A tag server on the ciplink core: one process per site owns the PLC connections and serves tag values to web
//! apps over a WebSocket (the protocol of ciplink-tagserver and `@ciplink/react`).
#![warn(missing_docs)]

use std::path::Path;

pub mod cli;
pub mod codegen;
pub mod config;
pub mod hub;
pub mod logging;
pub mod mock;
pub mod planner;
pub mod plc;
pub mod rules;
pub mod server;
pub mod service;
pub mod values;
pub mod worker;

#[cfg(test)]
mod server_tests;
#[cfg(test)]
mod testing;

pub use config::{Config, load_config};
pub use server::ServerHandle;

/// The driver factory: simulated PLCs from their `mock_tags` files with `mock`, else real controllers.
pub fn factory(mock: bool) -> plc::Factory {
    if mock {
        mock::factory().0
    } else {
        plc::LogixPlc::factory()
    }
}

/// Serves the config file until Ctrl+C.
pub fn run(config_path: &Path, mock: bool) -> Result<(), String> {
    let config = load_config(config_path)?;
    let runtime = tokio::runtime::Builder::new_multi_thread()
        .enable_all()
        .build()
        .map_err(|e| e.to_string())?;
    runtime.block_on(server::run(config, factory(mock)))
}