Discussions about DRD, see https://www.drupal.org/project/drd - the Drupal Remote Dashboard
So, that's a reason to getting started with it.
The deployment of their code into remote sites is the tricky part. For DRD we built everything into a phar library and that gets pushed to all remote clients.
As for custom plugins I'm still wondering about the best way on how to deploy them though.
I would like to see a solution that doesn't require an update remotely when a new plugin gets introduced into your DRD.
You can now write your own action plugins for DRD. Documentation can be found here: https://www.drupal.org/docs/8/modules/drupal-remote-dashboard/for-developers/writing-your-own-action-plugin
I got it, it works. Thank you very much! You may extend it by providing the posibility of using arguments (through buildConfigurationForm, etc.), or at least explain briefly in documentation, how it works. It caused me some headache but finally I got it. But basically it was OK, easy to understand at use it. Thank you again!
Using arguments is inherited from Drush and Console, so there is nothing special for DRD plugins. But the config form is, you're right.
Have you had a look into some of the action plugins from DRD how they do it?
DRD 3.12 released with lots of improvements and fixes: https://www.drupal.org/project/drd/releases/8.x-3.12
Also, all DRD Agents have been updated too.
Just opened the issue https://www.drupal.org/project/drd/issues/2923414 to discuss encryption of sensitive data in DRD. Please join the discussion either here or in the issue.
Release 3.13 (https://www.drupal.org/project/drd/releases/8.x-3.13) with 3 new features:
- Integrates with monitoring from @MDSystems_CH (https://www.drupal.org/project/monitoring)
- Integrates with @platformsh (https://platform.sh)
- Implements encryption of passwords, keys and other sensitive data (https://www.drupal.org/project/encrypt)
Just to let everyone know, there are currently some really nice discussion going on in the issue queue at https://www.drupal.org/project/issues/drd - if you want to influence the direction we're taking, now seems to be a good time to have a look and comment there.
Hi, as I wrote several weeks ago, we use Drupal 7 and DRD in our current network. We have a lot of web sites. (We want to upgrade the whole network to Drupal 8, but we're not ready to do it yet). We have a serious issue: any time a new website is added, key settings will be lost at a lot of other sites and we have a lot of "Execution request unauthorized" and "Wrong DRD Keys" messages. Do you have any idea how it could be solved? We add several new sites weekly and it's very annoying.
Do I get this right, you're using DRD for Drupal 8 but your remote sites are on D7?
That shouldn't be a problem and I haven't seen such a behaviour before.
Sounds like either a version mismatch or either side is not storing the communiation settings properly.
Probably needs some heavy debugging to find out what's missing and why.
Hi @MrHaroldA what do you mean by "indexing all our websites"? DRD is a tool to monitor any number of remote Drupal sites and to get deep insight into configuration and status. Indexing might be something different, i.e. building an index of all the content on those sites. That's not part of DRD though, but maybe you meant something different?
We want a central place which has all software versions of all websites our company supports. Most of the sites are built on Drupal, but there are WordPress and other sites too. Is it possible to write agents for non Drupal projects? I know that many features won't work on other platforms, but a centralized CVE scanner or just a centralized database of all module/plugin/platform versions would be great too.
We of course would write and release all non Drupal agents.
OK, got it. The simple answer is Yes, that's possible. Having said that, the agent to be written for WordPress would have to respond to all the requests you want to support in the same way that a Drupal site does. That's probably not feasible!? So, maybe we should enhance the data model in DRD such that it is prepared for other remote platforms. That would mean that the remote sites can respond natively but DRD needs to be enhanced to be able to support his.
I quite like the idea, but it needs proper planning and execution. If you want to follow up on this, we should probably setup a Zoom call to exchange ideas.
Hi everyone, I am kinda new to this module and I was trying to create my own action plugin that just displays a notification message on the selected domain.
I was following the guide here: https://www.drupal.org/docs/8/modules/drupal-remote-dashboard/for-developers/writing-your-own-action-plugin
But I am not sure where the code should be imported. On the DRD instance or the DRD Agent instance?
Also, the generated code is not a module, but I create an info file, so I can install the code and import the configuration on an instance.
The warning that I am getting when executing the action is Remote instance does not support DRD.
Any tutorial on this action plugin? Currently is blurry whether to put the code on the master or the slave instance
I was following the guide here: https://www.drupal.org/docs/8/modules/drupal-remote-dashboard/for-developers/writing-your-own-action-plugin
But I am not sure where the code should be imported. On the DRD instance or the DRD Agent instance?
Also, the generated code is not a module, but I create an info file, so I can install the code and import the configuration on an instance.
The warning that I am getting when executing the action is Remote instance does not support DRD.
Any tutorial on this action plugin? Currently is blurry whether to put the code on the master or the slave instance
The ping action is working properly, also the maitenance action is working
Hi @jurgenhaas , just to update, I made the action plugin work, I also opened an issue for generating the code (https://www.drupal.org/project/drd/issues/3125390).
Now I wanted to make another customized feature. I saw that for collecting information and error logs from the domain, a cache is set and then used in the view on the route (/drd/domains/domain/{domain_id}). Is this extensible? Like for example, I wanted to get some new info with an action and could I extend the Domain entity with 1 more property to display in the view? What is the best approach for this functionality?
Now I wanted to make another customized feature. I saw that for collecting information and error logs from the domain, a cache is set and then used in the view on the route (/drd/domains/domain/{domain_id}). Is this extensible? Like for example, I wanted to get some new info with an action and could I extend the Domain entity with 1 more property to display in the view? What is the best approach for this functionality?
Regarding extending the domain entity and the caching mechanism, I need to think about. If it can't be fine yet, we can definitely build something to make that work
Hi all, first of all awesome plugin. I just wanted to know where i can get a bit more detailed documentation. For example, when you add new cores, there are options like Update Method, is there any documentation on those options. Or for example, updating Drupal core, is there any documentation on that?
welcome @taonac , glad you like DRD. Not many people are using the update functions yet and there is not much documentation yet. But a pretty comprehensive blog post at https://www.lakedrops.com/en/blog/post/big-drd-update-available-automatic-site-updates-and-ton-other-improvements which may give you the insight you're looking for