Replies: 1 comment 1 reply
|
That fatal is expected on a fresh clone, nothing you broke. Your |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Greetings- I've been playing/hacking for several hours to get just up through the curl command in the getting started doc. I'm running with GitBash on Windows and can run make build and the make upd commands ok.
But when i run the curl to get overall status I get this:
$ curl -s http://localhost:8081/healthz <br /> <b>Warning</b>: require_once(/app/vendor/autoload_runtime.php): Failed to open stream: No such file or directory in <b>/app/public/index.php</b> on line <b>5</b><br /> <br /> <b>Fatal error</b>: Uncaught Error: Failed opening required '/app/vendor/autoload_runtime.php' (include_path='.:/usr/local/lib/php') in /app/public/index.php:5 Stack trace: #0 {main} thrown in <b>/app/public/index.php</b> on line <b>5</b><br />I was able to get a docker exec to install some necessary packages, and finally got the status to come back ok afterward, but I wanted to get a clean, consistent build and run so started hacking at the Makefile so that anyone trying a clean install could get the right installations out-of-the-box. But, that became a rabbit hole since I don't know the entire architecture of the various make/compose files. So, before going down that rabbit hole, I just wondered if this curl error was indeed expected behavior for a clean install?
Here's the after-install ad-hoc command to get extras installed, btw:
docker compose exec backend-symfony composer installAll reactions