-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using HTTPS with localhost #2
Comments
How did enable/create SSL certificates for localhost? I'm trying to do it in MAMP and it says you can't add SSL certificates to localhost. |
@dayneh88 No idea on that front, I'm using Devilbox as my local environment, but I found this: https://really-simple-ssl.com/knowledge-base/how-to-install-an-ssl-certificate-on-mamp/ I hope it helps. :) |
Fantastic! Thanks so much for your help. You haven't had any luck getting @font-face to work with this boilerplate by any chance have you? |
@dayneh88 I haven't had any problems using @font-face, however, I haven't used this boilerplate in a while. 😅 |
I'm having massive issues! Are you able to shed any light on this: #4 I'd forever be in your eternal debt if you could help me out. I'm wracking my brain with this haha. |
Hey there, I found a small issue when trying to enable the configuration for https proxying on BrowserSync.
It seems to me that even if you add the https section into the project configuration in
webpack.config.js
the build procedure just ignores it and uses the default SSL certificates bundled with BrowserSync since in most instances you are using custom SSL certificates, this can lead to localhost giving you an insecure connection warning.I found that the fix is pretty easy, by just adding the https configuration to the
config.base.js
under thebrowserSyncOptions
constant. Here are my edits:In
webpack.config.js
:In
config.base.js
:Probably you may have a more elegant solution in case it's not passed as a parameter. 😅
The text was updated successfully, but these errors were encountered: