Understanding the Dev environment about slim-api-skeleton HOT 2 CLOSED

How and where is my database created and hosted respectively?

These two lines create the database. Database itself lives inside the Vagrant machine.

Like if I want to access local DB, how to do I do that.

Using the mysql command in the Vagrant machine.

$ mysql -u root example

One addition to this setup will be to add phpMyAdmin to view database.

Yes, you can easily add phpMyAdmin if it fits your needs. It is however outside of the scope of this skeleton.

I am building a Microservices framework, where I want to clone multiple instances of this project to create various services. Now these services will talk to each other as well. Here comes the second need, it should be very easy to have different urls for different services. Vagrant Hostsupdater comes to my mind. Have you thought of integrating that?

Again outside of the scope of the skeleton. However if you need many instances running at the same time, one way would be to change the ip address for each Vagrant machine.

It's great that you have already integrated other necessary dependencies required like logging, but if I want to debug using php error logs, where do I access those?

The operating system / Apache default which is /etc/httpd/logs/ssl_error_log

from slim-api-skeleton.

Thanks for the info

from slim-api-skeleton.