If you decide to store files in JCR, no matter how you configure persistence 
you will only see JCR data structures in filesystem.


As Markus said, you can keep files in FS, actually you can keep your files 
anywhere in the webapp and just configure bypass in cms subchain ( 
config:/server/filters/cms/bypasses ) to expose the folder in file system.

To activate such content, you can use packager.

Other option would be to have network folder mapped for such files and share 
this between instances so you don't need to activate those files.

Either way, I would recommend to create special data type to keep meta data 
about your files inside of Magnolia and to allow users to nicely select them 
like any other asset.


HTH,
Jan

On Apr 23, 2012, at 6:42 AM, Markus Waidhofer (via Magnolia Forums) wrote:

> Hi,
> 
> in your Magnolia webapplication (on the file system), there is a folder 
> docroot (if not, you can create one).  You can put any files you want in 
> there and you can use them anywhere you want on your webpage.
> 
> For example, if you put the file someImage.jpeg in the docroot folder, it can 
> be read by localhost:8080/magnoliaAuthor/docroot/someImage.jpeg.
> 
> But, I do not know if you can use the activation mechanism for this folder 
> somehow.
> 
> -- 
> Context is everything: 
> http://forum.magnolia-cms.com/forum/thread.html?threadId=a80ef85b-eecc-4951-8209-dca5b8eed41b
> 
> 
> ----------------------------------------------------------------
> For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
> Alternatively, use our forums: http://forum.magnolia-cms.com/
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------




----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to