Skip to content

Domains directory required, ENOENT if it doesn't exist #345

@adamkdean

Description

@adamkdean

I'm testing CDN 3.0.0-rc1, and unless I have the domains directory present, CDN is crashing.

I don't have any configuration for multi-domain support, the configuration is very slim.

Creating a directory named domains manually fixes the issue.

{
  "server": {
    "name": "DADI (CDN)",
    "protocol": "http",
    "host": "0.0.0.0",
    "port": 80
  },
  "images": {
    "directory": {
      "enabled": false,
      "path": "images"
    },
    "s3": {
      "enabled": false
    },
    "remote": {
      "enabled": false
    }
  },
  "assets": {
    "directory": {
      "enabled": false
    },
    "s3": {
      "enabled": false
    },
    "remote": {
      "enabled": false
    }
  },
  "caching": {
    "ttl": 3600,
    "directory": {
      "enabled": false
    },
    "redis": {
      "enabled": false
    }
  },
  "auth": {
    "clientId": "123",
    "secret": "456",
    "tokenTtl": 1800
  },
  "cluster": false,
  "env": "development"
}

The error:

> dadi-cdn@ start /app
> node server.js

fs.js:953
  return binding.readdir(pathModule._makeLong(path), options.encoding);
                 ^

Error: ENOENT: no such file or directory, scandir '/app/domains'
    at Error (native)
    at Object.fs.readdirSync (fs.js:953:18)
    at DomainManager.scanDomains (/app/node_modules/@dadi/cdn/dadi/lib/models/domain-manager.js:42:21)
    at Object.Config.loadDomainConfigs (/app/node_modules/@dadi/cdn/config.js:702:6)
    at Object.Config (/app/node_modules/@dadi/cdn/config.js:611:29)
    at Object.<anonymous> (/app/node_modules/@dadi/cdn/config.js:755:18)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions