joseph-d

I think that using `chmod` is only going to provide a temporary fix. As soon as the service running in the docker container writes a new log file, it's going...

I can confirm a similar thing happening when you try to run `php please stache:clear` or other stache commands, the error is as follows: ``` Call to undefined method Statamic\Auth\Eloquent\User::initialPath()...

You need to add the new name to your application's .env file under a new `APP_SERVICE` key like this: ``` APP_SERVICE=my-app-localhost ``` After that, you'll be able to run things...

I noticed this too, it happens if you run the add command twice and then you end up with something like, `ports { }` in your yaml. If you just...

Well, basically, the `fleet:add` script takes away whatever is in the first position of the list of ports. I guess this is because in the default Laravel docker stub (https://github.com/laravel/sail/blob/1.x/stubs/docker-compose.stub)...

Agreed, it would probably be better if the logic identified the specific binding to remove rather than just assuming that the first one has to go, regardless of what it...

I'm not sure if it's even supposed to work with a docker config that has been modified to this extent. Looking at the `FleetAddCommand.php` it would seem as though it...

I agree that it definitely seems a bit redundant / cumbersome to install fleet in every project. But beyond that, it's also a bit of a shame (from my perspective...

Sounds like something got messed up when the yaml was re-written. If you can post the relevant section (ports) from the docker-compose.yaml then we should be able to figure it...