Git Product home page Git Product logo

haraka-plugin-redis's Introduction

haraka-plugin-redis

Build Status Code Climate

Connects to a redis instance. By default it stores a redis connection handle at server.notes.redis. See below to get a custom DB handle attached to another database.

Config

The redis.ini file has the following sections (defaults shown):

[server]

; host=127.0.0.1
; port=6379

[pubsub]

; host=127.0.0.1
; port=6379

Publish & Subscribe are DB agnostic and thus have no db setting. If host and port and not defined, they default to the same as [socket] settings.

[opts]

; see https://github.com/redis/node-redis/blob/HEAD/docs/client-configuration.md
; database=0
; password=battery-horse-staple

Options specified in redis.ini[opts] are applied to the server config, the pubsub config, AND the configurations of any plugins that inherit this plugin. This is ideal if the redis server requires a password. Specify it once in [opts]. If other redis connections need a different value (such as a unique DB), they must specify it. For plugins, all options are stored in the plugins [redis] section of its config file.

Usage (shared redis)

Use redis in your plugin like so:

if (server.notes.redis) {
    server.notes.redis.hGetAll(...);
        // or any other redis command
}

Publish/Subscribe Usage

In your plugin:

exports.results_init = function (next, connection) {
    this.redis_subscribe(connection, () => {
        connection.notes.redis.on('pmessage', (pattern, channel, message) => {
            this.do_something_with_message(message, ...)
        })
        next()
    })
}
// be nice to redis and disconnect
exports.hook_disconnect = function (next, connection) {
    this.redis_unsubscribe(connection)
}

Custom Usage

This variation lets your plugin establish its own Redis connection, optionally with a redis db ID. All redis config options must be listed in your plugins config file in the [redis] section.

exports.register = function () {
  this.inherits('redis')

  this.cfg = this.config.get('my-plugin.ini')

  // populate plugin.cfg.redis with defaults from redis.ini
  this.merge_redis_ini()

  // cluster aware redis connection(s)
  this.register_hook('init_master', 'init_redis_plugin')
  this.register_hook('init_child', 'init_redis_plugin')
}

When a db ID is specified in the [redis] section of a redis inheriting plugin, log messages like these will be emitted when Haraka starts:

[INFO] [-] [redis] connected to redis://172.16.15.16:6379 v3.2.6
[INFO] [-] [limit] connected to redis://172.16.15.16:6379/1 v3.2.6
[INFO] [-] [karma] connected to redis://172.16.15.16:6379/2 v3.2.6
[INFO] [-] [known-senders] connected to redis://172.16.15.16:6379/3 v3.2.6

Notice the database ID numbers appended to each plugins redis connection message.

haraka-plugin-redis's People

Contributors

greenkeeper[bot] avatar msimerson avatar zazapeta avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

haraka-plugin-redis's Issues

An in-range update of eslint-plugin-haraka is breaking the build ๐Ÿšจ

The devDependency eslint-plugin-haraka was updated from 1.0.11 to 1.0.12.

๐Ÿšจ View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-haraka is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • โœ… continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).
  • โŒ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 1 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those donโ€™t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot ๐ŸŒด

haraka plugin redis error on connecting to redis

system info

Haraka Haraka.js โ€” Version: 2.8.28
Node v16.14.2
OS Linux Debian 5.10.102.1-microsoft-standard-WSL2 #1 SMP Wed Mar 2 00:30:59 UTC 2022 x86_64 GNU/Linux
openssl OpenSSL 1.1.1n 15 Mar 2022

Expected behavior

No error on connecting to redis server

Observed behavior

loaded TLD files:
  1=1495
  2=8570
  3=2448
loaded 9192 Public Suffixes
loglevel: INFO
log format: DEFAULT
[WARN] [-] [core] smtp.ini.nodes unset, using 1, see https://github.com/haraka/Haraka/wiki/Performance-Tuning
Starting up Haraka version 2.8.28
[INFO] [-] [core] Loading plugins
[INFO] [-] [core] Loading plugin: tls
[INFO] [-] [core] loading tls.ini
[INFO] [-] [core] Loading plugin: auth/flat_file
[INFO] [-] [core] Loading plugin: auth/auth_bridge
[INFO] [-] [core] Loading plugin: dkim_sign
[INFO] [-] [core] Loading plugin: redis
[INFO] [-] [core] Loading plugin: queue/smtp_forward
[NOTICE] [-] [queue/smtp_forward] outbound enabled, will default to disabled in Haraka v3 (see #1472)
[INFO] [-] [redis] connected to redis://192.168.0.100:6379
[CRIT] [-] [server] Plugin redis timed out on hook init_master - make sure it calls the callback
[INFO] [-] [server]  hook=init_master plugin=redis function=init_redis_shared params="" retval=DENYSOFT msg="plugin timeout"
[ERROR] [-] [server] init_master returned error: plugin timeout
[NOTICE] [-] [core] Shutting down

Steps to reproduce

add redis to config/plugin
create redis.ini in config

I am having trouble to connect redis with haraka in order to run haraka-plugin-watch. Even though I put redis.ini in config folder it did not load new config for host or port

An in-range update of eslint is breaking the build ๐Ÿšจ

Version 4.5.0 of eslint just got published.

Branch Build failing ๐Ÿšจ
Dependency eslint
Current Version 4.4.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint is โ€œonlyโ€ a devDependency of this project it might not break production or downstream projects, but โ€œonlyโ€ your build or test tools โ€“ preventing new deploys or publishes.

I recommend you give this issue a high priority. Iโ€™m sure you can resolve this ๐Ÿ’ช

Status Details
  • โœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • โŒ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes v4.5.0
  • decdd2c Update: allow arbitrary nodes to be ignored in indent (fixes #8594) (#9105) (Teddy Katz)
  • 79062f3 Update: fix indentation of multiline new.target expressions (#9116) (Teddy Katz)
  • d00e24f Upgrade: chalk to 2.x release (#9115) (Stephen Edgar)
  • 6ef734a Docs: add missing word in processor documentation (#9106) (Teddy Katz)
  • a4f53ba Fix: Include files with no messages in junit results (#9093) (#9094) (Sean DuBois)
  • 1d6a9c0 Chore: enable eslint-plugin/test-case-shorthand-strings (#9067) (่–›ๅฎš่ฐ”็š„็Œซ)
  • f8add8f Fix: don't autofix with linter.verifyAndFix when fix: false is used (#9098) (Teddy Katz)
  • 77bcee4 Docs: update instructions for adding TSC members (#9086) (Teddy Katz)
  • bd09cd5 Update: avoid requiring NaN spaces of indentation (fixes #9083) (#9085) (Teddy Katz)
  • c93a853 Chore: Remove extra space in blogpost template (#9088) (Kai Cataldo)
Commits

The new version differs by 12 commits.

  • ff8c4bb 4.5.0
  • 480bbee Build: changelog update for 4.5.0
  • decdd2c Update: allow arbitrary nodes to be ignored in indent (fixes #8594) (#9105)
  • 79062f3 Update: fix indentation of multiline new.target expressions (#9116)
  • d00e24f Upgrade: chalk to 2.x release (#9115)
  • 6ef734a Docs: add missing word in processor documentation (#9106)
  • a4f53ba Fix: Include files with no messages in junit results (#9093) (#9094)
  • 1d6a9c0 Chore: enable eslint-plugin/test-case-shorthand-strings (#9067)
  • f8add8f Fix: don't autofix with linter.verifyAndFix when fix: false is used (#9098)
  • 77bcee4 Docs: update instructions for adding TSC members (#9086)
  • bd09cd5 Update: avoid requiring NaN spaces of indentation (fixes #9083) (#9085)
  • c93a853 Chore: Remove extra space in blogpost template (#9088)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot ๐ŸŒด

connecting via socket instead of tcp

Using a unix socket instead of tcp is useful for improving performance on same-machine clients. While it's not documented, it does seem possible to connect via a unix socket with a config like:

[server]
path=/var/run/redis/redis-server.sock
host=ignored
port=ignored

It results in some misleading logging, though:

[INFO] [-] [redis] connected to redis://ignored:ignored

It might be worthwhile to document this and/or change how the logging works.

An in-range update of eslint-plugin-haraka is breaking the build ๐Ÿšจ

Version 1.0.6 of eslint-plugin-haraka just got published.

Branch Build failing ๐Ÿšจ
Dependency eslint-plugin-haraka
Current Version 1.0.5
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-plugin-haraka is โ€œonlyโ€ a devDependency of this project it might not break production or downstream projects, but โ€œonlyโ€ your build or test tools โ€“ preventing new deploys or publishes.

I recommend you give this issue a high priority. Iโ€™m sure you can resolve this ๐Ÿ’ช

Status Details
  • โœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details
  • โŒ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 6 commits.

  • 99d1051 bump version
  • 0906a4a reduce no-useless-escape to warn only
  • 968b392 SublimeLint breaks if you don't use full path (#4)
  • d6ab389 add node env to .eslintrc
  • c04dd99 add .eslintrc.json
  • 508f6b7 version bump 1.0.5

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot ๐ŸŒด

An in-range update of eslint-plugin-haraka is breaking the build ๐Ÿšจ

The devDependency eslint-plugin-haraka was updated from 1.0.9 to 1.0.10.

๐Ÿšจ View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-haraka is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • โœ… continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).
  • โŒ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those donโ€™t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot ๐ŸŒด

An in-range update of eslint is breaking the build ๐Ÿšจ

Version 4.0.0 of eslint just got published.

Branch Build failing ๐Ÿšจ
Dependency eslint
Current Version 3.19.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint is โ€œonlyโ€ a devDependency of this project it might not break production or downstream projects, but โ€œonlyโ€ your build or test tools โ€“ preventing new deploys or publishes.

I recommend you give this issue a high priority. Iโ€™m sure you can resolve this ๐Ÿ’ช

Status Details
  • โœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details
  • โŒ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v4.0.0
  • 4aefb49 Chore: avoid using deprecated rules on ESLint codebase (#8708) (Teddy Katz)
  • 389feba Chore: upgrade deps. (#8684) (่–›ๅฎš่ฐ”็š„็Œซ)
  • 3da7b5e Fix: Semi-Style only check for comments when tokens exist (fixes #8696) (#8697) (Reyad Attiyat)
  • 3cfe9ee Fix: Add space between async and param on fix (fixes #8682) (#8693) (Reyad Attiyat)
  • c702858 Chore: enable no-multiple-empty-lines on ESLint codebase (#8694) (Teddy Katz)
  • 34c4020 Update: Add support for parens on left side for-loops (fixes: #8393) (#8679) (Victor Hom)
  • 735cd09 Docs: Correct the comment in an example for no-mixed-requires (#8686) (Fangzhou Li)
  • 026f048 Chore: remove dead code from prefer-const (#8683) (Teddy Katz)
Commits

The new version differs by 119 commits.

  • c61194f 4.0.0
  • 821a1e6 Build: changelog update for 4.0.0
  • 4aefb49 Chore: avoid using deprecated rules on ESLint codebase (#8708)
  • 389feba Chore: upgrade deps. (#8684)
  • 3da7b5e Fix: Semi-Style only check for comments when tokens exist (fixes #8696) (#8697)
  • 3cfe9ee Fix: Add space between async and param on fix (fixes #8682) (#8693)
  • c702858 Chore: enable no-multiple-empty-lines on ESLint codebase (#8694)
  • 34c4020 Update: Add support for parens on left side for-loops (fixes: #8393) (#8679)
  • 735cd09 Docs: Correct the comment in an example for no-mixed-requires (#8686)
  • 026f048 Chore: remove dead code from prefer-const (#8683)
  • a8e1c1c 4.0.0-rc.0
  • 1768dc0 Build: changelog update for 4.0.0-rc.0
  • 0058b0f Update: add --fix to no-debugger (#8660)
  • b4daa22 Docs: Note to --fix option for strict rule (#8680)
  • 4df33e7 Chore: check for root:true in project sooner (fixes #8561) (#8638)

There are 119 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot ๐ŸŒด

An in-range update of eslint is breaking the build ๐Ÿšจ

Version 5.0.1 of eslint was just published.

Branch Build failing ๐Ÿšจ
Dependency [eslint](https://github.com/eslint/eslint)
Current Version 5.0.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • โœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details
  • โŒ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes v5.0.1
  • 196c102 Fix: valid-jsdoc should allow optional returns for async (fixes #10386) (#10480) (Mark Banner)
  • 4c823bd Docs: Fix max-lines-per-function correct code's max value (#10513) (Rhys Bower)
Commits

The new version differs by 4 commits.

  • caeb223 5.0.1
  • 125dc34 Build: changelog update for 5.0.1
  • 196c102 Fix: valid-jsdoc should allow optional returns for async (fixes #10386) (#10480)
  • 4c823bd Docs: Fix max-lines-per-function correct code's max value (#10513)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those donโ€™t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot ๐ŸŒด

An in-range update of eslint is breaking the build ๐Ÿšจ

The devDependency eslint was updated from 5.16.0 to 6.0.0.

๐Ÿšจ View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • โœ… continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).
  • โŒ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v6.0.0
  • 81aa06b Upgrade: [email protected] (#11869) (Teddy Katz)
  • 5f022bc Fix: no-else-return autofix produces name collisions (fixes #11069) (#11867) (Milos Djermanovic)
  • ded9548 Fix: multiline-comment-style incorrect message (#11864) (golopot)
  • cad074d Docs: Add JSHint W047 compat to no-floating-decimal (#11861) (Timo Tijhof)
  • 41f6304 Upgrade: sinon (#11855) (Toru Nagashima)
  • 167ce87 Chore: remove unuseable profile command (#11854) (Toru Nagashima)
  • c844c6f Fix: max-len properly ignore trailing comments (fixes #11838) (#11841) (ZYSzys)
  • 1b5661a Fix: no-var should not fix variables named 'let' (fixes #11830) (#11832) (Milos Djermanovic)
  • 4d75956 Build: CI with Azure Pipelines (#11845) (Toru Nagashima)
  • 1db3462 Chore: rm superfluous argument & fix perf-multifiles-targets (#11834) (่–›ๅฎš่ฐ”็š„็Œซ)
  • c57a4a4 Upgrade: @babel/polyfill => core-js v3 (#11833) (่–›ๅฎš่ฐ”็š„็Œซ)
  • 65faa04 Docs: Clarify prefer-destructuring array/object difference (fixes #9970) (#11851) (Oliver Sieweke)
  • 81c3823 Fix: require-atomic-updates reports parameters (fixes #11723) (#11774) (Toru Nagashima)
  • aef8ea1 Sponsors: Sync README with website (ESLint Jenkins)
Commits

The new version differs by 134 commits.

  • a7985a6 6.0.0
  • be74dd9 Build: changelog update for 6.0.0
  • 81aa06b Upgrade: [email protected] (#11869)
  • 5f022bc Fix: no-else-return autofix produces name collisions (fixes #11069) (#11867)
  • ded9548 Fix: multiline-comment-style incorrect message (#11864)
  • cad074d Docs: Add JSHint W047 compat to no-floating-decimal (#11861)
  • 41f6304 Upgrade: sinon (#11855)
  • 167ce87 Chore: remove unuseable profile command (#11854)
  • c844c6f Fix: max-len properly ignore trailing comments (fixes #11838) (#11841)
  • 1b5661a Fix: no-var should not fix variables named 'let' (fixes #11830) (#11832)
  • 4d75956 Build: CI with Azure Pipelines (#11845)
  • 1db3462 Chore: rm superfluous argument & fix perf-multifiles-targets (#11834)
  • c57a4a4 Upgrade: @babel/polyfill => core-js v3 (#11833)
  • 65faa04 Docs: Clarify prefer-destructuring array/object difference (fixes #9970) (#11851)
  • 81c3823 Fix: require-atomic-updates reports parameters (fixes #11723) (#11774)

There are 134 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those donโ€™t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot ๐ŸŒด

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! ๐ŸŽŠ

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml

If youโ€™re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didnโ€™t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didnโ€™t touch job or matrix configurations because these tend to be quite specific and complex, and itโ€™s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what youโ€™re doing it may require additional work or may not be applicable at all. Weโ€™re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, Iโ€™m a humble robot and wonโ€™t feel rejected ๐Ÿค–


FAQ and help

There is a collection of frequently asked questions. If those donโ€™t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot ๐ŸŒด

TLS SUPPORT

Hi,

I forked your project to add TLS support.
Is this repo still active ?
I can make a PR if so :)

I am not able to connect to redis with custom plugin

Hello

I have followed the guide, this is my plugin:

const outbound = require('/usr/lib/node_modules/Haraka/outbound');

exports.register = function () {
    this.inherits('redis');
    this.cfg = this.config.get('my-plugin.ini');
    // populate plugin.cfg.redis with defaults from redis.ini
    this.merge_redis_ini();

    // cluster aware redis connection(s)
    this.register_hook('init_master', 'init_redis_plugin');
    this.register_hook('init_child',  'init_redis_plugin');
}

Console:

[INFO] [-] [greylist] connected to redis://127.0.0.1:6379/11
[INFO] [-] [redis] connected to redis://127.0.0.1:6379
[INFO] [-] [custom] using server.notes.redis
[INFO] [-] [redis] connected to redis://127.0.0.1:6379

I have installed the haraka-plugin-redis via npm, and configured the redis.ini to the default:
[server]
host=127.0.0.1
port=6379

An in-range update of haraka-test-fixtures is breaking the build ๐Ÿšจ

Version 1.0.21 of haraka-test-fixtures just got published.

Branch Build failing ๐Ÿšจ
Dependency haraka-test-fixtures
Current Version 1.0.20
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As haraka-test-fixtures is โ€œonlyโ€ a devDependency of this project it might not break production or downstream projects, but โ€œonlyโ€ your build or test tools โ€“ preventing new deploys or publishes.

I recommend you give this issue a high priority. Iโ€™m sure you can resolve this ๐Ÿ’ช

Status Details
  • โŒ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
  • โŒ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 2 commits ahead by 2, behind by 4.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot ๐ŸŒด

An in-range update of eslint is breaking the build ๐Ÿšจ

The devDependency eslint was updated from 6.7.1 to 6.7.2.

๐Ÿšจ View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • โœ… continuous-integration/travis-ci/push: The Travis CI build passed (Details).
  • โŒ continuous-integration/appveyor/branch: AppVeyor build failed (Details).

Release Notes for v6.7.2
  • bc435a9 Fix: isSpaceBetweenTokens() recognizes spaces in JSXText (fixes #12614) (#12616) (Toru Nagashima)
  • 4928d51 Fix: don't ignore the entry directory (fixes #12604) (#12607) (Toru Nagashima)
  • b41677a Docs: Clarify suggestion's data in Working with Rules (refs #12606) (#12617) (Milos Djermanovic)
  • ea16de4 Fix: Support tagged template literal generics in no-unexpected-multiline (#11698) (Brad Zacher)
  • fa6415d Sponsors: Sync README with website (ESLint Jenkins)
  • e1e158b Sponsors: Sync README with website (ESLint Jenkins)
Commits

The new version differs by 8 commits.

  • dbbba83 6.7.2
  • bc54d15 Build: changelog update for 6.7.2
  • bc435a9 Fix: isSpaceBetweenTokens() recognizes spaces in JSXText (fixes #12614) (#12616)
  • 4928d51 Fix: don't ignore the entry directory (fixes #12604) (#12607)
  • b41677a Docs: Clarify suggestion's data in Working with Rules (refs #12606) (#12617)
  • ea16de4 Fix: Support tagged template literal generics in no-unexpected-multiline (#11698)
  • fa6415d Sponsors: Sync README with website
  • e1e158b Sponsors: Sync README with website

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those donโ€™t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot ๐ŸŒด

Haraka main redis database instance is hardcoded to database 0

system info

Haraka: 2.8.24
Node: 11.13.0
OS: FreeBSD mail 12.0-RELEASE-p3 FreeBSD 12.0-RELEASE-p3 GENERIC amd64
OpenSSL: OpenSSL 1.1.1a-freebsd 20 Nov 2018

Expected behavior

The main Redis database, as set in redis.ini (default stanza: "db=0") should accept any value between 0 and 16.

Observed behavior

It seems that the main Redis database, as set in redis.ini (stanza: "db=0") cannot be changed to anything else.

Steps to reproduce

Trying to set a different database number seems to be ignored.

Am I missing something? Thank you

Chris

redis: standardize & modernize

  • populate [files] in package.json. Delete .npmignore.
  • automated code linting. #3308
    • dep: eslint-plugin-haraka -> @haraka/eslint-config
    • update 'lint' script in package.json
    • verify 'lint' CI test config
  • lint: remove duplicate / stale rules from .eslintrc
  • automated code formatting (see also #3308)
  • automated CI testing.
    • mostly done, verify that local copy of ci.yml is up-to-date.
  • CONTRIBUTORS: see 3309
  • consistent naming of "special" files like CHANGELOG.md.
  • CHANGELOG: verify links at bottom (due to inconsistent tag naming)
    • latest .release does this, fixes most, and warns of errors it can't fix
  • verify GitHub repo About link points to npm package
  • convert test suites to mocha "style"
    • works great today and with node --test in v18+

Haraka does not seem to accept Redis passwords

system info

Haraka: 2.8.24
Node: 11.13.0
OS: FreeBSD mail 12.0-RELEASE-p3 FreeBSD 12.0-RELEASE-p3 GENERIC amd64
OpenSSL: OpenSSL 1.1.1a-freebsd 20 Nov 2018

Expected behavior

The ability to add the Redis password into the redis connection URI, or to add it via a "password=" stanza

Observed behavior

Passwords do not seem to be accepted at present.

Steps to reproduce

Trying to connect to a password-protected Reids instance using a URI connection string with password fails. Likewise, a "password=[my_redis_password]" entry does not seem to be recognised.

Am I missing something? Thank you

Chris

An in-range update of haraka-test-fixtures is breaking the build ๐Ÿšจ

Version 1.0.20 of haraka-test-fixtures just got published.

Branch Build failing ๐Ÿšจ
Dependency haraka-test-fixtures
Current Version 1.0.19
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As haraka-test-fixtures is โ€œonlyโ€ a devDependency of this project it might not break production or downstream projects, but โ€œonlyโ€ your build or test tools โ€“ preventing new deploys or publishes.

I recommend you give this issue a high priority. Iโ€™m sure you can resolve this ๐Ÿ’ช

Status Details
  • โŒ continuous-integration/travis-ci/push The Travis CI build failed Details
  • โœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details

Commits

The new version differs by 6 commits ahead by 6, behind by 1.

  • 6432dbb update eslint with es6 declaration
  • e768f99 travis-ci: node 4 -> 8
  • 450ad00 sprinkle some es6 around
  • 069e01c use haraka-notes
  • f32da45 fix appveyor image URL (#23)
  • 0530cd3 remove version from haraka-results (#22)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot ๐ŸŒด

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.