3 ms·
Getting started with Laravel on Mac required me to fire up Docker desktop which I don't particularly care for but I proceeded because I like to try out new thin
by subsaharancoder 5y ago
Getting started with Laravel on Mac required me to fire up Docker desktop which I don't particularly care for but I proceeded because I like to try out new things, so I followed the documentation https://laravel.com/docs/9.x#your-first-laravel-project https://laravel.com/docs/9.x#your-first-laravel-project:
- Fired up Docker desktop
- ran curl -s "https://laravel.build/example-app https://laravel.build/example-app" | bash and "cd example-app"
- typed "./vendor/bin/sail up" and got an error "no such file or directory: ./vendor/bin/sail"
- Deleted the example-app and ran curl -s "https://laravel.build/example-app https://laravel.build/example-app" | bash and "cd example-app"
- typed "./vendor/bin/sail up" and got another error "no configuration file provided: not found"
By this time my MBP fan sounds like an Airbus A380 getting ready to takeoff and I'm already frustrated with the framework, not sure what I'm missing!!
- throwaway829 5y agoThe docs push you in the docker direction, but they also have Laravel Valet which "is a development environment for macOS minimalists": https://laravel.com/docs/9.x/valet https://laravel.com/docs/9.x/valet A lot of Laravel devs use Valet instead of Docker.