Creating an issue for a D8 release of this module.
Subtasks
- Convert to Symfony routing system (in progress)
- Convert to use Configuration API (ongoing)
- Convert hook_theme() to use Twig
- Convert check functions to Plugins
Working repository
| Comment | File | Size | Author |
|---|---|---|---|
| #28 | xmlrpc_add_php_extension.patch | 298 bytes | rob holmes |
| #27 | xmlrpc_add_php.patch | 437 bytes | rob holmes |
Comments
Comment #1
malc0mn commentedkerasai, you can start from the 7.x-1.x-dev branch for this.
A D8 port will be much appreciated!!!
Cheers,
mlc.
Comment #2
kerasai commentedI'm planning to take an initial shot at doing a D8 port at MWDS, 8/15-17.
Comment #3
kerasai commentedComment #4
kerasai commentedCreated a repo on github to track changes.
https://github.com/kerasai/production_check
Comment #4.0
kerasai commentedAdded sub tasks, etc
Comment #6
malc0mn commentedComment #7
malc0mn commentedComment #22
asrobHi!
How it's going? Anyone can take care of this?
Comment #23
malc0mn commentedaspilicious is on it, hope he will have some more time in the near future... Anyone is welcome to step in, obviousely ;-)
k.
Comment #24
jax commentedWhat's the current status? It's not clear where I can start to help, there is only this issue and the Github branch is pretty outdated as well.
What's the issue?
And additionally, Acquia SPI also collects this kind of information is there any way to merge that or abstract out the common components....
Comment #25
nitebreedI just released the 8.x-1.0-alpha2 version of the Production Check. For us, this is workable and has the ability to be able to add Drupal 8 sites to monitor. Please test and issue any findings!
Comment #26
jax commentedIt seems that the Production monitor module is only available in D7. To be able toch check a D8 site I had to change
/xmlrpcto/xmlrpc.phpinxmlrpc.routing.ymlto be able to check a D8 site via XMLRPC. The check via REST is not functioning.Comment #27
rob holmes commentedHere is a patch for D8 to fix the routing definition for xmlrpc.php
Comment #28
rob holmes commentedAnother patch with correct paths
Comment #30
anybodyStill relevant. Is the list up to date @aspilicious?
Comment #31
grevil commentedI think, we can safely close this issue!
LGTM!
Comment #32
grevil commented