Bobcares

Laravel Mix Browsersync Docker

PDF Header PDF Footer

Learn how to use Laravel Mix & Browsersync Docker. Our Laravel Support team is here to help you with your questions and concerns.

Laravel Mix Browsersync Docker

Did you know integrating tools like Browsersync with Laravel Mix improves the developer experience?

Laravel Mix Browsersync Docker

Today, we are going to take a look at how to use Browsersync in the Dockerized Laravel Mix environment.

How to Set Up Browsersync in Laravel Mix

To enable Browsersync support in Laravel Mix, we have to call the `mix.browserSync()` command. We can pass either a string or an object to this method. The proxy represents the domain name for proxying output from the webpack Dev Server through Browsersync.


mix.browserSync('my-domain.test');
// Or using Browsersync settings:
mix.browserSync({
proxy: 'my-domain.test'
});

Then, start the development server by running:

npm run watch

Docker Compose Configuration

To make npm commands available in a Docker container, we can use the Docker Compose configuration. Ensure that the container exposes Browsersync’s default port (3000) and its UI (3001):

npm:
image: node:14-alpine
container_name: my-app-npm
volumes:
- .:/var/www/html
working_dir: /var/www/html
entrypoint: [ 'npm' ]
networks:
- default
ports:
- 3000:3000
- 3001:3001

Laravel Mix Configuration

In the Laravel Mix configuration, add Browsersync settings within the `mix.browserSync()` method:


mix.browserSync({
host: 'localhost',
proxy: 'my-app-api',
port: 3000,
open: false,
});

Now restart the application to expose the new ports:

docker-compose down
docker-compose up -d

We can use the following command to run npm with service ports:

docker-compose run --rm --service-ports npm run watch

Alternatively, with aliases:

dc up -d
dcr --service-ports npm run watch

Laravel Mix Hot-Reloading in Sail with Browsersync

For Sail users, port 3000 has to be exposed. Then run these commands:

sail artisan sail:publish
sail down
sail up -d
sail npm install
sail npm run watch-poll

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts demonstrated how to use Laravel Mix & Browsersync Docker.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Docker Support

Spend time on your business, not on your servers.

Managing a server is time consuming. Whether you are an expert or a newbie, that is time you could use to focus on your product or service. Leave your server management to us, and use that time to focus on the growth and success of your business.

TALK TO US Or click here to learn more.

Speed issues driving customers away?
We’ve got your back!

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF