I suppose I found a solution (yours solution): Access site from local network with Bud - #5 by schilke-ts
Sorry for this duplication.
For those looking for the same issue, I paste our updated bud.config.js
/**
* @typedef {import('@roots/bud').Bud} bud
*
* @param {bud} app
*/
const bs = require('browser-sync-webpack-plugin')
module.exports = async (app) => {
app
/**
* Application entrypoints
*
* Paths are relative to your resources directory
*/
.entry({
app: ['@scripts/app', '@styles/app'],
editor: ['@scripts/editor', '@styles/editor'],
})
/**
* These files should be processed as part of the build
* even if they are not explicitly imported in application assets.
*/
.assets('images')
/**
* These files will trigger a full page reload
* when modified.
*/
.watch('index.php' ,'resources/views/**/*', 'app/**/*')
/**
* Target URL to be proxied by the dev server.
*
* This should be the URL you use to visit your local development server.
*/
.proxy(app.env.get('WP_HOME'))
.use({
name: 'browser-sync-webpack-plugin',
make: () => new bs({proxy: app.env.get('WP_HOME')}),
})
/**
* Development URL to be used in the browser.
*/
.serve( {
host: app.env.get('ENC_DEVELOPMENT_DOMAIN'),
cert: app.env.get('ENC_DEVELOPMENT_SSL_CRT'),
key: app.env.get('ENC_DEVELOPMENT_SSL_KEY'),
});
};