Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
This section addresses the integration of third party applications with Drupal. Some tips may be unique to a third party application, and some may be reusable by several applications. The most frequent asked questions relate to:
- Sharing a user base
- Sharing authentication
- Synchronizing a dual user base
- External authentication
- Session handler issues
- Theme engine integration
- Import scripts
Comments
Custom Module Configuration File Best Practice?
I'd like to see "Module Integration" added to this list but would like feedback on this problem:
There is a discussion about how best to handle Node.js multi-site management for node.js configuration files. What is the best way to handle flat-file configurations that have different values per-site?
nodejs/nodejs.config.js <- stores site-specific configuration variables read by nodejs.
This structure blocks us from having the module in /sites/all/modules since each site must have a unique configuration. The only option is to place the module with the site-specific modules folder.
The other issue is that we have to modify the files in the module folder which could be considered a hack. Is there a best practice for managing this scenario?
Some ideas:
sites/mysite1/modules/nodejs/[config 1]
sites/mysite2/modules/nodejs/[config 2]
sites/mysite3/modules/nodejs/[config 3]