starmanmartin / efwbuilder

EFW (ELN File Watcher) builder

How to set up a EFW builder server

To host an instance of the EFW builder you simply need to clone the Repo into your server. Then copy end rename the .env.example file as .env. Make sure to replace xxx.xxx.xxx with either the domain of the server or the public server IP.

ALLOWED_HOST=0.0.0.0,django,xxx.xxx.xxx
WEBDAV_HOST=http://xxx.xxx.xxx
PORT=80
FLAVOR=production

DJANGO_SUPERUSER_USERNAME=EBA
[email protected]
DJANGO_SUPERUSER_PASSWORD=ChangePasswordFast

File: .env

Make sure that you have docker and docker-compose installed. More info here

Finally, simply run:

docker-compose up -d

You can install a local server if you only need a EFW build server and no WebDAV server. In this case replace xxx.xxx.xxx by 127.0.0.1. It is also recommender to change the port in such a case. With:

docker-compose up

a local server can be started. The page can be accessed at http://127.0.0.1:.

Welcome to the EFW manager

Full documentation here

This server-side application allows you to monitor and organise the data transmission of devices integrated in your ELN Chemotion instance (for more infos click here ). With the EFW (ELN File Watcher) manager, EFW instances adapted to the requirements can be generated quickly and simply. These instances can then be installed on the target system in just a few steps. In addition, this server provides a data storage unit with an interface to receive data from your target systems. These data are then automatically entered in the ELN.

How to install EFW

The following section introduces the installation of the EFW. Note that the installation is only intended for Windows devices.

1. Generate EFW instance:

   There will be a distinction in 2 cases how to generate an EFW instance. The first case is a new external EFW instance adapted to external WebDAV server. The second case is a new internal EFW instance adapted to this WebDAV server.

2. Install EFW instance:

   In both cases of the previous step the installation on the target system is the same. However, the installation is simple but require administration rights.

   1. Make a directory "C:\Program Files\eln_exporter"
   2. Copy the (on this server generated) efw.exe into "C:\Program Files\file_exporter"
   3. Copy the file file_exporter_task.vbs into the startup directory.

      Hint: Press Windows Key + R to open run and type shell:startup. This will open startup directory

efwbuilder's Issues

Watcher should watch any files

I noticed that files whose modification date is older than the start of the program are ignored. I would assume that these should be watched anyway, since the transfer directory does not necessarily have to be the working directory.

Move this repository to ComPlat

Dear Martin,

Continuing to work on the CV workflows in Chemotion ELN (and also publish the samples with CV data in Chemotion Repository) we noticed that it would be helpful or more clear for users and admins of Chemotion ELN instances if the GitHub repos of important components are collected at one place.

To my knowledge the ELN File Watcher (may be rebranded as EFWShuttle) https://github.com/ComPlat/ELN_file_watcher is part of the ComPlat organisation. Consequently, the EFWBilder should be also moved to ComPlat https://github.com/ComPlat .

@nicolejung : Would the mentioned one be an option for a new branding? I must agree that EFW stands for ELN File Watcher but the ELN File Watcher actually also watches folders. From a Windows perspective, this might be confusing, while from a unix perspective this is totally a'right. The question is: What would users thing who are ELN admins?

Best,
Tillmann

custom port

An alternative port to the default port 22 should be available for SFTP transfers.

Application has a high CPU load

Under Windows, the efw.exe seems to need a noticeable amount of CPU, even when idle.