This is my FileContent Site - I have created my own small Content link scripts and Macro's - as no Confluence Plugins supports files in a filestructure.

Requirements

Software

Atlassian CLI (Notice the 3.X versions are not free, last free download versions at Atlassian CLI

 

Scripts

Gallery Configurations (config.txt)

Script for linking files into a Confluence page (updateFileContent.sh)

Optional: Script for refreshing Confluence pages (refreshPages.sh)

A Lightbox as Floatbox

User Macros

User Macro: make-top

User Macro: go-top

User Macro: me-filecontent 

 

The setup

Install the Software and packages needed

Config Atlassian CLI (Set username, password and URL in confluence.sh)

Config Tomcat to support symbolic links (see this currently unsolved issue regarding special UTF-8 characters)

Create a Script directory and place the 2 scripts and the config.txt files into them

Edit the config.txt to fit Your installation

Create the User Macro me-filecontent in Your Confluence installation

Start adding pictures to Your installation using the updategallery.sh and optional refreshpages.sh scripts

 

The workings

All content (Pictures and Video) are place on the servers filesystem in a Tree Structure, from a Basic root (called ContentRoot in the config.txt file)

All the top directories under the ContentRoot are linked into the Confluence installation by the makesymlinks.sh script)

For each top directory, a subdirectory or one or more phrases, a collection of content can be placed on a Confluence Page with the updategallery.sh script

When the script runs, it travels an entire directory-structure and :

• Creates thumbnails for the content (image or video) in a subdir called something with "thumbs"
• Adds a macro onto the specified Confluence page to show (render) the content (image or video)
• Finally, saves the page into Confluence

 

Architecture

 

Questions and Answers

Q: Is there a manuel maintenance between the config.txt and the me-image macro?

A: Yes, the ThumbSize and DisplaySize numbers must match in the file and macro, otherwise images will give a 404 Error

 

Q: My Thumbnail Image is not displayed?

A: Check the following:

• Tomcat Linking is allowed
• The Paths etc in the macro on the Confluence Page - does it exist in the filesystem
• Permissions on the filesystem

 

Q: Images are so slow...why?

A: This can be bandwith, server hardware, memory - or the DisplaySize parameter - hence how large an image that must be fetched. 800 is default.

 

Q: Why does the me-image macro have both an parth/image-name and md5 sum parameter

A: The path/image-name is pure legacy, the md5 is the future workings, as this better supports moving images around in dirs, or renaming them.