Truecrypt encryption and Open Media Vault

truecrypt will work on OMV because it is debian but there is no way to get it to work with the web interface/shared folders/etc (yet). Any script you run that makes changes to config files would be overwritten by the web interface. Give it a little more time. Volker is changing a few things in the storage backend and a truecrypt plugin may be possible in the future.

Zitat von "k567890"

hmmm. So I can't mount a tc disk in the debian backend OS and then in omv web interface choose the already mounted volume for sharing? Please confirm because I believe this is possible in omv... no?

No, it doesn't. A mounted filesystem doesn't show up in the Filesystems tab unless there is an entry in /etc/openmediavault/config.xml. I am working on this right now with a possible mhddfs plugin.

Zitat von "k567890"

With such, there should be no need for any plug-in for tc. In fact, this would make omv drastically more robust.
I could mount the volumes with the script before omv even loads, and then safely auto unmount them after omv has shut down.

Pre and post scripts wouldn't work because you can change settings in the web interface at any time which would overwrite any change made by those scripts. I disagree that this should be done without a plugin. The idea of OMV is to have a web interface that is easy to use. Plugins don't make anything less robust. If you look at the structure of a plugin, it is basically a javascript file for the web interface, php file to write to the database, and a shell script to write the config files. How is this less robust than a shell script run a start/shutdown?

Zitat von "k567890"

If I was interested in making such a plug-in, is there some resource to help me / guide me?
I saw the 3 part sticky guide in the forum. Asside from that, is there some IRC channel or something?
Or am I supposed to just post here if I get stuck?

OMV 0.5 is documented here. You can post questions on the development forum (I don't use IRC). Looking at plugins Volker has written (here) and the 3rd party plugins (here) is how I learned. I still refer to the OMV code all the time. The rest comes from your knowledge of javascript, php, and shell scripting. The three part tutorial is very good. It is hard to go much further without making it specific to a service.

Zitat von "k567890"

To answer your question, what makes plug-ins less robust is that only those who know the internals of omv can make plug-ins. I need to know all sorts of schemes and hacks you are using. Where you db is, what you are storing in db. What is connected to what and how...etc etc etc. The internals of omv are not documented any plae as far as I know.

All OMV does is give you an interface to enter values and a method to get those values to a shell script. You don't have to know the internals of OMV. You write the script that writes the config files. Once you look at the plugins more, it will make more sense.

Zitat von "k567890"

Although in principle webinterface can clash with custom shell scripts, the point is that in some cases a person could make a script that doesn't clash because they are only adding functionality that webinterface doesn't have in the first place. Most of the time, there would not be any clash and it is often a one liner in linux. Making a plugin, is something that the avg linux user doesn't have the skills for but they can write a one line script no problem.

Very few services (minidlna, transmission, virtualbox, mysql, etc...) can be used with a one line script. It is tough enough supporting a web interface let alone a script where one semi-colon may make the script non-functional.