After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 546627 - ssh sync should require folder option
ssh sync should require folder option
Status: RESOLVED DUPLICATE of bug 473329
Product: tomboy
Classification: Applications
Component: General
0.11.x
Other Linux
: Normal enhancement
: ---
Assigned To: Tomboy Maintainers
Tomboy Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-06 17:03 UTC by Pedro Villavicencio
Modified: 2008-08-06 17:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Pedro Villavicencio 2008-08-06 17:03:07 UTC 
this bug has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/tomboy/+bug/184106

"The ssh sync should require the folder option to be entered,
or at least default to something else than the user's home directory.

This would also then allow the folder sync to default to the
same local location to easily set up two machine ssh syncing."

"It would make a lot of sense for it to default to ~/.tomboy on the remote machine in order to sync with existing data. This is the behavior that most users are probably expecting from the plugin."

Thanks,
Comment 1 Sandy Armstrong 2008-08-06 17:28:57 UTC 
It should NOT default to ~/.tomboy.  Synchronization does NOT work by linking to another user's ~/.tomboy directory!  One machine (the "server") needs to have a directory specifically for storing Tomboy synchronization data.  Other machines may connect to that directory using ssh, webdav, or local folder, whichever is most convenient.  Before the first sync occurs, this directory needs to be empty!

That being said, there is no good default folder because for a new setup you'll want a new empty folder.  Perhaps we should pick something like ~/tomboy-sync and offer to create it?

Marking as a duplicate of bug 473329.

*** This bug has been marked as a duplicate of 473329 ***