Re: [Bobs-devel] rsync over ssh -> ready

[Jochen M. <ml...@om...>]

Hi Rene,
hi Joe,

now I was a bit too quick.


> 
> I guess it depends on whether we want to be able to browse the files without
> being able to restore.
Yes, that is a good question.
Practically speaking, I would open my konqueror, open a sftp to the 
backup server on left side and another sftp to the webserver on right
side and then transfer.

I think browsing the files just makes sense, when you can restore them..
What is your opinion Rene and Joe.

> 
> A few possible solutions:
> 
> 1. No access to the UI at all.
> Simple to implement.
> 
THAT was the I did it now:

I have already implemented that no.
So I have double security here. 

1st) You cannot login to the server:
 cause: It does not show up in http://bobsdomain/bobs/
        when it is of restore_method = "none"

2nd) If you would do it with the correct REQUEST var via URL,
     you still cannot, because it is prohibited
     in class_server.php (method login)

Should we leave it that way or do something else about it?
At present it is in the patch attached as unified diff.

> 2. Access to the UI but no restore functionality.
> Also fairly simple to implement.
> 
> 3. Access to the UI, and ability to restore to the originating server.
> Could be complex. How hard I'm really not able to say at the moment.
> I'm a bit rusty on the internal workings of bobs.
> 
> 4. Access to the UI, and ability to restore somewhere else than the
> originating server.
> Possibly as (hard or soft) linked files. That those files could be
> accessed using sftp, smb rsync, nfs or what else you set up.
> Or plainly just using another server as receiver of the restored files.
> This would most likely require extensive testing since this goes to the
> heart of bobs.
> Almost everything is on someway connected to 
> "$this->backupdir . '/' . $this->server . '/' . $this->share"
> Changing the usage of those three vars requires touching most of the 
> code is one way or another.
> 
I would appreciate 3. of course:

The scenario I am thinking about at present, is:

A user having an account on our webserver can 
open the bobs-browser on the backup-machine
and login with his account data (which is equal to his account
on the webserver)

Then he restores the data he needs, the data is restored using
rsync and that is it.

But, I think this is more than a footstring away at present.
Not sure about it. 

Of course this is an ideal ISP - Solution in my opinion.

> If you are too busy with other projects 
Yes, that is really my problem at present. But it does not really
change. I always squeeze some time in between to work on also im-
portant projects (like backuping now).

I suggest the second solution and
> printing a notice when users log in. 

mhm, can you have a look at current solution (1.) and tell me if 
if it fits or something like (2.) would be better?

BTW... could you give me a commit access to sf.net like suggested?

Cheers 

Jochen