Hi, I'm having trouble using the docker/sdk after having modified composer.json (I've installed middleware/process), since spryker will build the container using default autoload.php. Can anybody tell me the best way to use local composer.json in docker/sdk.

What exactly is the issue? Did you add middleware namespace to config

$config[KernelConstants::CORE_NAMESPACES]

The issue in fact is, that if I check out my working changes and do a docker/sdk up on another machine docker/sdk up will crash because it will not use the changed local composer.json but afaik an unchanged one from spryker repo.

hmm, this sounds strange. I might as a stupid question here, but does other machine use the same code? Did you commit also composer lock file?

i am also not 100% clear here 🤔

@wide-furniture-25595 Please, describe the flow of commands you do to up Spyker. Do you bootstrap with deploy.dev.yml file?

I bootstrap a deploy.stage.yml on the server, only difference to my dev.yml is endpoints, debug, and mount option (baked on stage). Locally I required spryker-middleware/process and developed a feature, when i deploy on server and bootstrap again and docker/sdk up, Spryker installation fails when generating propel models.

baked

means the codebase is backed into docker image, so you cannot expect file you changed on your host appears there. You can run docker/sdk up again and the changes will appear. It would take a few minutes. Or you can switch to

native

or

docker-sync

(depends on platform you use) to have possibility to see changes on-fly

I understand what baked does but I cannot rebuild th container without the above error occuring

What exactly error do you have?