Jump to content

block34

Members
  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About block34

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. /etc? However can you tell me exactly the commands to get the information you ask for?
  2. $ docker inspect wordpress [ { "Id": "sha256:ee2256095234b2ecd8ccdd6cb0a90e401461020ffa707323ae08a78a03a44ba7", "RepoTags": [ "wordpress:latest" ], "RepoDigests": [ "wordpress@sha256:6f609ebf8518069516df36f0ab504735f8e563c1e303c37eba4902e732fcc6c6" ], "Parent": "", "Comment": "", "Created": "2020-07-10T06:33:41.143418206Z", "Container": "a283dc2b546a4a43d0c243023641e5142976b5557a8760174f5c667549dd2966", "ContainerConfig": { "Hostname": "a283dc2b546a", "Domainname"
  3. I wrote on this forum just because I have this difficulty. What else are the forums for?
  4. $ curl http://localhost:8000 The web page shows this thing: Fatal error: Uncaught Error: Call to undefined function yaml_parse_file() in /var/www/html/wp-content/plugins/mytest/main.php Maybe I have to install the php-yaml extension (or something similar). How you do it? Here is my docker-compose.yml file: version: '3.3' services: db: image: mysql:5.7 volumes: - dbdata:/var/lib/mysql restart: always environment: MYSQL_ROOT_PASSWORD: somewordpress MYSQL_DATABASE: wordpress MYSQL_USER: wordpress MYSQL_PASS
  5. $ docker run \ --rm \ -v $(pwd):/data \ phpdockerio/php72-fpm \ --directory src \ --target docs docker: Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "exec: \"--directory\": executable file not found in $PATH": unknown. ERRO[0000] error waiting for container: context canceled But does it work for you? Can't you do some tests?
  6. I really think so. It will mean that I will await any future developments. Thanks anyway.
  7. The problem is that I don't speak English very well (I apologize). Could you explain yourself a little better? Besides the phpdoc / phpdoc container should I use a container with PHP 7.2? Could you give a practical example?
  8. $ docker run \ --rm \ -v $(pwd):/:/data phpdoc/phpdoc:7.2 \ --directory src \ --target docs Unable to find image 'phpdoc/phpdoc:7.2' locally docker: Error response from daemon: manifest for phpdoc/phpdoc:7.2 not found. See 'docker run --help'.
  9. $ docker run --rm -v $(pwd):/data phpdoc/phpdoc -d src -t docs # show the output web page (see attachment) $ firefox docs/classes/Examples.Example.html Because into the output web page, it appears Warning: count(): Parameter must be an array or an object that implements Countable......
  10. Look at these examples. Docblock only for the class: /** * Tool to format a text. */ class Formatter { function format() {} } Docblock only for the method: class Formatter { /** * Format a text. */ function format() {} } Docblocks for both (slightly diversified): /** * Tool to format a text. */ class Formatter { /** * Format a text. */ function format() {} } Identical docblocks for both (although they create a little redundancy for my taste): /** * Format a text. */ class Formatter { /** * Format a text.
  11. block34

    phpdoc not work

    Sorry, first time I use this form
  12. block34

    phpdoc not work

    ++ composer require --dev phpdocumentor/phpdocumentor Using version ^2.9 for phpdocumentor/phpdocumentor ./composer.json has been updated Loading composer repositories with package information Updating dependencies (including require-dev) Nothing to install or update Package herrera-io/json is abandoned, you should avoid using it. Use kherge/json instead. Package herrera-io/phar-update is abandoned, you should avoid using it. No replacement was suggested. Package kherge/version is abandoned, you should avoid using it. No replacement was suggested. Generating autoload files
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.