Private documents made Public

1. Access to selected areas of private content is provided by symbolic links.
   
   
2. Private and Public URLs are very similar with only the following differences:
   
   
   1. http://z.lam1.us for public version
      
   2. https://q.lam1.us for private version

    Example

1. Capture private URL
   
   For this page: https://q.lam1.us/Zz/z09/z0901/090110/Public-by-link.html
   
   
2. Replace "https://q.lam1.us" with "ln -s /mnt/ts" to create a command to be executed at the shell when current directory is the the appropriate folder within the public directory.
   
   
3. Open shell and navigate to the appropriate folder within the public directory creating parent folders as necessary.
   
   
4. Execute the command created above.
   
   For this page: ln -s /mnt/ts/Zz/z09/z0901/090110/Public-by-link.html

    More Examples

    Why do this?

1. Only one version of the document exists. It exists in a place that although set up for secure authenticated access already is backed up on a regular basis.
2. The link provides a record of the documents published status.
3. Little space is used on the web server where only the symbolic link actally exists. Space usage is actually on the file server where document access is controlled by authentication and files are protected by RAID and backed up daily.
4. The UNIX/Linux symbolic link and Apache FollowSymLinks seems like the right way to do this.

Sunday, December 29, 2024 @ 2:49:38 AM
z.ServerAdmin@lam1.us