wolf's dashboard

"Screen" is an option all right, but I'd categorize this option as a last resort. I'd prefer the clean version that employs a back-end daemon. This would enable the server to automatically start the service when occasionally it needs to be rebooted.

I'm actually kind of surprised the Wuala team didn't make this separation to begin with, as it's considered good practice to separate content and presentation.

on virtually any un*x system you could use the virtual terminal emulation tool named "screen"....
http://www.gnu.org/software/screen/

open a new screen, and create subscreens/terminals and run wualacmd (wualacommandline) there.

then simply disconnect from that screen, thus leaving the running processes alive inside that screen virtual terminal.

at any later time, you can ssh to your box, and reconnect to the disconnected screen terminal again.

this is all textmode i am talking about,
check out the screen tool if you are unfamiliar with that.
http://www.gnu.org/software/screen/

but i agree, a real server/worker and client/gui/interface separation would be even more appropriate and a good addition.

of course you can easily run wuala in a screen window to manage the -nogui programm and connect from your out-door system normally with the gui version to wuala.
But at all you ́re right. The better way will be definitely a deamon. – bagelcat, on June 08, 2008 18:41

I think the separation between UI and worker threads is essential to successful adoption of Wuala. With a daemon working in the background, a headless 24/7 server can easily provide 99.9% uptime on Wuala storage.

The only reason I'm not yet participating in the Wuala project is that my home server is an SSH access only machine; if only I could start a Wuala daemon that runs in the background and connect to that backend from a remote front-end, there would soon be dozens of shared gigs available on a reasonably high bandwidth connection.