Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
@koopjs/cache-redis
Advanced tools
To use this cache: First: npm install koop-cache-redis Then: configure your host. In your config file
config/production.json
{
"cache": {
"redis": {
"host": "redis://localhost:6379"
}
}
}
If using environment variables like config/custom_environment_variables.json
{
"cache": {
"redis": {
"host": "KOOP_REDIS_HOST"
}
}
}
Then you must export the REDIS_HOST variable into your ENV e.g.
export KOOP_REDIS_HOST="redis://localhost:6379"
Then require and register the redis cache with Koop
const Koop = require('koop')
const koop = new Koop()
const config = require('config')
const cache = require('koop-cache-redis')
koop.register(cache)
insert
Insert geojson into the cache
Note: A metadata entry will be created automatically. It can be populated from an object on the inserted geojson.
const geojson = {
type: 'FeatureCollection',
features: [],
metadata: { // Metadata is an arbitrary object that will be stored in the catalog under the same key as the geojson
name: 'Example GeoJSON',
description: 'This is geojson that will be stored in the cache'
}
}
const options = {
ttl: 1000 // The TTL option is measured in seconds, it will be used to set the `expires` field in the catalog entry
}
cache.insert('key', geojson, options, err => {
// This function will call back with an error if there is already data in the cache using the same key
})
append
Add features to an existing geojson feature collection in the cache Note:
const geojson = {
type: 'FeatureCollection',
features: []
}
cache.append('key', geojson, err => {
// This function will call back with an error if the cache key does not exist
})
update
Update a cached feature collection with new features. This will completely replace the features that are in the cache, but the metadata doc will remain in the catalog.
const geojson = {
type: 'FeatureCollection',
features: []
}
const options = {
ttl: 1000
}
cache.update('key', geojson, options, err => {
// This function will call back with an error if the cache key does not exist
})
upsert
Update a cached feature collection with new features or insert if the features are not there.
const geojson = {
type: 'FeatureCollection',
features: []
}
const options = {
ttl: 1000
}
cache.upsert('key', geojson, options, err => {
// This function will call back with an error if the cache key does not exist
})
retrieve
Retrieve a cached feature collection
const options = {} // For now there are no options on retrieve. This is meant for compatibility with the general cache API
cache.retrieve('key', options, (err, geojson) => {
/* This function will call back with an error if there is no geojson in the cache
The geojson returned will contain the metadata document from the catalog
{
type: 'FeatureCollection',
features: [],
metadata: {}
}
*/
})
delete
Remove a feature collection from the cache
cache.delete('key', err => {
// This function will call back with an error if there was nothing to delete
})
createStream
Create a stream of features from the cache
cache.createStream('key', options)
.pipe(/* do something with the stream of geojson features emitted one at a time */)
The catalog stores metadata about items that are in the cache.
catalog.insert
Add an arbitrary metadata document to the cache.
Note: This is called automatically by insert
const metadata = {
name: 'Standalone metadata',
status: 'Processing',
description: 'Metadata that is not attached to any other data in the cache'
}
cache.catalog.insert('key', metadata, err => {
// this function will call back with an error if there is already a metadata document using the same key
})
catalog.update
Update a metadata entry
const original = {
name: 'Doc',
status: 'Processing'
}
cache.catalog.insert('key', original)
const update = {
status: 'Cached'
}
cache.catalog.update('key', update, err => {
// this function will call back with an error if there is no metadata in the catalog using that key
})
cache.catalog.retrieve('key', (err, metadata) => {
/*
Updates are merged into the existing metadata document
Return value will be:
{
name: 'Doc',
status: 'Cached'
}
*/
})
catalog.retrieve
Retrieve a metadata entry from the catalog
cache.catalog.retrieve('key', (err, metadata) => {
// This function will call back with an error if there is no metadata stored under the given key
// Or else it will call back with the stored metadata doc
})
catalog.delete
Remove a catalog entry from the catalog Note: This cannot be called if data is in the cache under the same key
cache.catalog.delete('key', err => {
// This function will call back with an error if there is nothing to delete or if there is still data in the cache using the same key
})
[1.0.1] - 2017-08-31
koop-cache-redis
FAQs
Redis Cache Plugin for Koop
The npm package @koopjs/cache-redis receives a total of 49 weekly downloads. As such, @koopjs/cache-redis popularity was classified as not popular.
We found that @koopjs/cache-redis demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.