6 ms·

Drupal will become More MongoDB Friendly

10 points by francesca 14y ago

deleted 14y ago
[deleted]
- mjwalshe 14y ago
  Ah I thought that was Joomla :-( At my previous employer my junior colleges refused to work on client joomla sites as they where scared that the site would crash if they looked at it in the wrong way and they woudl be blamed.
eli 14y ago
Neat. What would be really cool is if that also lets you share content between multiple Drupal sites more easily.
- pavelkaroukin 14y ago
  drupal already do it starting with version 5.x (current stable one - 7.x)
  - eli 14y ago
    I think maybe we are talking about different things, but I'm happy to be proven wrong. If I want to create a View of the latest content across a network of 10 Drupal sites, how would I do that now?
    - pavelkaroukin 14y ago
      I though you were talking about multisite, but what you are talking about much likely can be done with third-party module - Domain Access (and related ones) - http://drupal.org/project/domain http://drupal.org/project/domain
- brokentone 14y ago
  I can't imagine how this would allow for that functionality (Although I agree it could be cool). With current Drupal 7/MySQL setup each site has absolutely no knowledge of the other sites. I worked about 40 Drupal sites (most on the same domain) at my last job. Many had very similar structure, modules, themes, etc, just a different content source and it seemed to make the most sense to the devs before me to create separate sites (I don't necessarily disagree). To make updates to core, modules and the like, I wrote a couple scripts and a config with a list of the siteroots. It would cd to each directory then run the drush (the CLI client/module) commands we wanted. Before that, we had each engineer grab a couple sites and run the commands after we deployed. Less than ideal. Seems silly for common modules or core updates. First, the sites would have to have some kind of knowledge of each other. If you're looking for structural sharing, you can export views individually, but the majority of the core settings can be exported as a module with the features module. Users can be shared through the use of shared tables in the settings.php file. If you're looking for content movement/sharing, perhaps Organic Groups is worth a look. (edit: forgot the letter y)
  - eli 14y ago
    That's funny. At my last job I too had to manage about 40 Drupal sites. Administrative problems are there (though as you say Drush solves some of that), but our big problem was content sharing. I wrote a terrible, terrible hack that mucked around in Drupal core to enable cross-site queries. When I left we were making some very good progress using Apache Solr as a backend for cross-site Views and queries. We were already using it for search, so it added minimal overhead. I believe they've since rolled it out. I should bug them to open source the code. It was looking pretty slick.
pavelkaroukin 14y ago
i am not quite sure it is right fit. sql and nosql are so different, that "rewriting" module to connect to mongo will just give support, but not actual benefits, IMHO. I see only one case where it might be beneficial - integrating with another app which already use mongodb. Otherwise it would make more sense to create new nosql based CMS leveraging all nosql features instead.

10 points by francesca 14y ago

deleted 14y ago

[deleted]

mjwalshe 14y ago
Ah I thought that was Joomla :-( At my previous employer my junior colleges refused to work on client joomla sites as they where scared that the site would crash if they looked at it in the wrong way and they woudl be blamed.

eli 14y ago

Neat. What would be really cool is if that also lets you share content between multiple Drupal sites more easily.

pavelkaroukin 14y ago
drupal already do it starting with version 5.x (current stable one - 7.x)
- eli 14y ago
  I think maybe we are talking about different things, but I'm happy to be proven wrong. If I want to create a View of the latest content across a network of 10 Drupal sites, how would I do that now?
  - pavelkaroukin 14y ago
    I though you were talking about multisite, but what you are talking about much likely can be done with third-party module - Domain Access (and related ones) - http://drupal.org/project/domain http://drupal.org/project/domain
brokentone 14y ago
I can't imagine how this would allow for that functionality (Although I agree it could be cool). With current Drupal 7/MySQL setup each site has absolutely no knowledge of the other sites. I worked about 40 Drupal sites (most on the same domain) at my last job. Many had very similar structure, modules, themes, etc, just a different content source and it seemed to make the most sense to the devs before me to create separate sites (I don't necessarily disagree). To make updates to core, modules and the like, I wrote a couple scripts and a config with a list of the siteroots. It would cd to each directory then run the drush (the CLI client/module) commands we wanted. Before that, we had each engineer grab a couple sites and run the commands after we deployed. Less than ideal. Seems silly for common modules or core updates. First, the sites would have to have some kind of knowledge of each other. If you're looking for structural sharing, you can export views individually, but the majority of the core settings can be exported as a module with the features module. Users can be shared through the use of shared tables in the settings.php file. If you're looking for content movement/sharing, perhaps Organic Groups is worth a look. (edit: forgot the letter y)
- eli 14y ago
  That's funny. At my last job I too had to manage about 40 Drupal sites. Administrative problems are there (though as you say Drush solves some of that), but our big problem was content sharing. I wrote a terrible, terrible hack that mucked around in Drupal core to enable cross-site queries. When I left we were making some very good progress using Apache Solr as a backend for cross-site Views and queries. We were already using it for search, so it added minimal overhead. I believe they've since rolled it out. I should bug them to open source the code. It was looking pretty slick.

pavelkaroukin 14y ago

i am not quite sure it is right fit. sql and nosql are so different, that "rewriting" module to connect to mongo will just give support, but not actual benefits, IMHO. I see only one case where it might be beneficial - integrating with another app which already use mongodb. Otherwise it would make more sense to create new nosql based CMS leveraging all nosql features instead.