Yet Another Convoluted Documentation

[gander]

Is it so hard to understand that a person would like to go into the documentation, and being guided by the hand, in 5 minutes start his application instance? Version with php -S and docker compose. Would it hurt you so much to do it? It is extremely impudent to say that a given solution is easy and fast to implement, when the documentation causes physical pain when trying to start. I say this as a PHP programmer with 20 years of experience: your documentation sucks.

---

No ignoring the topic in the style of "since you succeeded, it's not a problem anymore?" I demand: put it on the first page of your documentation, and you will do the greatest benefit to future users:

composer global require phalcon/devtools:"^5.0@dev" --dev

phalcon create-project phalcon-playground

services:
    phalcon:
        image: phalconphp/cphalcon:v5.9.3-php8.4
        ports:
            - "80:80"
        volumes:
            - .:/var/www/html
        working_dir: /var/www/html
        command: ["php", "-S", "0.0.0.0:80", "-t", "public/", ".htrouter.php"]

[Jeckerson]

Hello, documentation management isn't simple stuff, but we are slowly working on that.

I demand

Here you might only suggest ;)

If you want contribute, please submit PR on docs repository with your suggestion.

[gander]

Please excuse my tone in my previous post. I was furious and tried my best to be as non-offensive as possible.

[Jeckerson]

Our full focus at that moment is cphalcon -> phalcon transition, only phql parser left, which is tedious process. After full migration to PHP, we plan to reorganize everything and simplify even more. Simplification process is continuous, so small steps are made, but slowly as we are small team...

Believe it or not, but our documentation was even worse, so we try to figure our how to manage whole legacy without forgetting nothing...