WP development on LAMP app vs. caching

[msbt]

Hi there! Quick question about the LAMP app: I'm using that to develop my WordPress sites, local template files get sent to the server after being updated and I would expect to see the changes immediately after a refresh (yes, also tried hard refresh and different browsers), but sometimes it takes up to a minute or maybe even longer until they are actually live. Is there some aggressive caching going on that could be disabled until the site is ready to be published? I also checked with the filemanager, the changes are on the server, but the rendered files are still the old ones.

Any suggestions on how to debug that?

[girish]

@msbt This is because of the opcache. If you disable it in php.ini, I think you will see the changes instantly.

I think:

[opcache]
opcache.enable=0

[jdaviescoates]

@msbt just out of interest, why are you using the LAMP app instead of just using the WordPress Developer app?

[msbt]

@jdaviescoates no particular reason, it just felt more right because only half of them will stay on a Cloudron environment, the rest will eventually migrate to some other provider and I wanted to keep it as vanilla as possible. It's also easier to change PHP versions to see if things are still working afterwards.

[girish]

@msbt This is because of the opcache. If you disable it in php.ini, I think you will see the changes instantly.

I think:

[opcache]
opcache.enable=0

[msbt]

thanks, I'll give it a go!

edit: already looking good, appreciate it!

[girish]

@msbt Cool, as a heads up, you probably want to enable it back when in "production" mode.

[msbt]

@girish thanks, I usually fire up a fresh one and use duplicator to migrate it to the live domain