Override lima.yml for better performance

[Mikilio]

Summary

The decision to make the lima config not configurable is bad UX. The vm commands always overwrite the config upon changing, and I can't make my configs portable.

Use case:
My client has a rather bulky wpml x woocommerce site and without virtiofs I can't work on it at all. It would be such a simple line change, but it gets overwritten all the time. The config should just be copied from the trellis folder.

The reason why I'm not pushing for virtiofs is because lima does not deem it stable.

Additional context

No response

[swalkinshaw]

Your use case makes sense but it's not as easy as just copying the config file from trellis to lima dir. The CLI regenerates the config every time you run vm start which preserve the CLI as the source of truth which we kind of need for updates.

#449 is related here as it changed the behaviour, though even before it wouldn't have solved your case.

For your specific needs we could just offer a mount type config option but obviously we can't do that for every attribute. Mount type would make sense though.

Does this mean you're using it on Linux and want to use this experiental virtiofs? https://lima-vm.io/docs/config/mount/#virtiofs

[Mikilio]

Does this mean you're using it on Linux and want to use this experiental virtiofs? https://lima-vm.io/docs/config/mount/#virtiofs

Yes, in fact I am doing this and in the case of WPML the difference is huge.

I am a new user of trellis, so I am open to correction when it comes to how I use the tools and I won't make any statement about how this is best achieved.

Just looking at the code it seemed feasible to me to simply overwrite lima.yml only once after VM creation and that would be it. The files that get regenerated even after the first vm start wouldn't get affected afaik. That is why I thought I'd be a simple but valuable addition.