[Leaplist] discussion - ways to share/access data

[Bryan J. Smith]

From: Dan Cherry <dan.s.cherry at gmail.com>
> ONce work is complete, it goes to a /share/category folder
> for use with nfs - but also rsync-ed to a local /bkup/share
> /folder for use when nfs won't get me to the true shared area.

Not to be "anal," but take care when creating new TLDs (top
level directories).  If you're unsure where to put something,
consult the defacto-standard:    
  http://www.pathname.com/fhs/pub/fhs-2.3.html  

Unfortunately, shares aren't covered.  But I tend to stick
with /export because that identifies the directory as
"exported" ("shared" is Windows-centric).  Everything I
export goes under it.

If I need to, I bind mount to /home for local access.

> overkill for my case - but would be useful if I was
> managing several users, though.

I find the combination of a read-only browse of my repo
with a wiki to be extremely powerful for even just my wife
and I.  I can go back to previous versions of files, jot
down notes and other info in the wiki, have a web front-end
for access to the files (running HTTP-SSL on a non-standard
port) so I can access them from the Internet (or tunnel via
SSH if I'm really anal).

Trac+SVN (there is also a GIT plug-in now) is very, very
powerful when it comes to organizing your work.


-- 
Bryan J Smith          Professional, Technical Annoyance
b.j.smith at ieee.org    http://www.linkedin.com/in/bjsmith
--------------------------------------------------------
I don't have a "favorite Linux distro."  I use, develop
and support community efforts, often built around Linux.
Technology and solutions are my focus, not dragging in
assumptions, marketing and other concepts which dominate
non-community developed software, which I left long ago.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.