You could ask IT team to spin you a windows machine in network itself or hosted
- Using Google Drive/Dropbox to Sync CSV files which syncs to #2.
- Use a Remote Machine to access Windows KVM / Cloud Machine.
I am pretty sure, that a dockerized version would appeal as well. I don’t know how many licenses that would sell, if it’s only a cli implementation, where you would need a regular license as well to build the transforms.
It would more or less be a headless version, which one could deploy on Linux if needed. One of my software partners has 35 windows virtual machines which he would like to port over to Linux for better performance.
For one he is using EDT, but he cannot which keeps him from porting over. On the other hand there are 30+ Linux installations, where he might also use EDT later on, but cannot.
If you would say, for instance, for the users of EDT you would supply this headless version for a discounted price compared to the real thing, it would be a nobrainer.
Just my 2cts.
1 Like
You might do it for one, but not a deployment for a larger audience. And why to setup things more complicated as they have to be? In that case they’d rather say ‘Thank you, but, no, thank you’.
This needs to be an easy way to do without too much extra effort for It and also for the maintenance.
And in a real IT environment of a large corporation, you cannot deal with Google drive / Dropbox, because security guidelines won’t allow you to. We have to have a security assessment each year, with a lot of paperwork, but neither GDrive nor Dropbox is being accepted by them.
A CLI only version for Linux might be a possibility to think about.
1 Like
Sounds good to me. Would be helpful.
Any news here for v2 perhaps, hopefully?
Best
There won’t be a Linux version for v2.0. It is still on the wishlist somewhere.
Oh, hmm. ok, if you move this up on the wishlist and want to tackle it i volunteer for testing.
Thanks for getting back.
Ok, thanks. We are very focussed on shipping v2 right now and can’t commit to any additional features.
I would like a cli-only version for linux, too… very much, indeed!
I guess you could think about a containerized version. Docker is available on every linux (and other OSes, too) . You would get freed from supporting several distribution styles, but would still have to support several architectures.
A Docker container brings all parts of a distribution with it that is needed. Usually, developers tend to use small base images to have the smallest possible overhead. That’s why there are so many containers that are based on Alpine Linux instead of Debian or Ubuntu…
But codewise I guess this would mean bigger changes as there are probably issues communication with the dockerized EDT…
a linux version would be perfect… I am thinking about a program for a customer right now… the programm will be fed via Excel-Files… I would love to have EDT available as a preprocessor/validator for this data… This is a very common use case, I guess. For me it would be a no brainer to include a EDT license for the customer instead of having to write the validation by myself…
Best,
Jochen
The first step is probably to make the CLI a separate program, rather than just running the GUI program ‘headless’. Once that is done, it should be relatively straightforward to create a Linux version of the CLI. Dealing with all the Linux distributions is an issue though, and we haven’t decided on the best way to do it.
Docker could be a way out of this situation, at least for some time. With Docker you can run on every distro that has docker. In the Container you bring the parts of a distro of your choice that are needed for EDT to run…
I’ve not used Docker, so I can’t really comment. I believe there are other possibilities, such as:
Definitely! I don’t know Flatpak, but from a quick look at the site, it is for GUI. Docker is already pretty common and widely used.
In my case, I might probably bundle a docker container of my own with the EDT-Container to have it run on Windows…