Ortus Couchbase Cache
  • Introduction
  • Intro
    • Release History
      • What's New With 4.0.0
      • 1.1.0 Documentation
      • 1.1.2 Documentation
      • 1.1.3 Documentation
      • 2.0.0 Documentation
      • 3.0.0 Documentation
      • Changelog
    • About This Book
  • Essentials
    • Installation
    • Configuration
    • Usage
      • CFML
      • Scope Storage
      • Direct Java API
      • RAM Resources
    • Debugging
Powered by GitBook
On this page
  1. Essentials
  2. Usage

RAM Resources

Use Couchbase as a virtual file storage

PreviousDirect Java APINextDebugging

Last updated 1 year ago

Lucee has the concept and feature of virtual file systems. Our extension taps into it by allowing you to leverage the resource to talk to Couchbase for storing documents and treating Couchbase like a big file system. This means that any file or directory related tag/function can work with a Couchbase RAM resource like: fileRead(), fileWrite(), fileDelete(), directoryNew(), directoryList(), include, etc. It even works when defining application mappings. You can define Couchbase to be the default cache for resources by selecting the default element in the cache details page and pointing it to resource.

Important: Please note that Lucee only allows you to determine 1 cache connection to be the default for either object, template, query, resource or function caching. You might end up creating different cache connections if you want to leverage them as default cache locations.

Once you setup Couchbase to be your default resource cache you can leverage it in many ways:

// Create a mapping to it
this.mappings[ "/cluster-fs" ] = "ram://";


// Do some file operations
fileWrite( "/cluster-fs/suzi.txt", myContent );
include template="/cluster-fs/aop.cfm";
directoryList( "/cluster-fs/caches" );
ram://