Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • C create-react-app
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,547
    • Issues 1,547
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 417
    • Merge requests 417
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Meta
  • create-react-app
  • Issues
  • #4050
Closed
Open
Issue created Feb 21, 2018 by Administrator@rootContributor

Make the SSL certificate and key configurable for localhost

Created by: jackpetraitis

I want to be able to provide self-signed certs and keys to my app during localhost development. These files need to be passed to the webpack-dev-server that runs behind the scenes when I do the "npm start" script from this package.

There are many ways to sign your own SSL certificate, and I know webpack-dev-server has the ability to run https over its own self-signed certificate.

However, this doesn't meet my request. I also know that the webpack-dev-server can take in key and cert file locations as arguments, and that is what my issue is targeting. I think we should add the ability to configure certificate and key file locations. This will make any development requiring SSL on localhost more straightforward.

How could we go about doing that?

I think there are two options:

  • Make them optional command-line arguments for the "npm start" script, configurable in package.json
  • Make the keys and certs follow a common naming convention or possibly use a certain folder structure
Assignee
Assign to
Time tracking