Skip to content

livereload configuration #1303

Description

@aggro80

With lite-server I could configure the server to serve specific path and use https with the following 'bs-config.js' configuration file that simulated the real server quite nicely:

var modRewrite  = require('connect-modrewrite');

module.exports = {
  "port": 3000,
  "server": { "baseDir": "./" },
  "https": true,
  "startPath": '/base/web/static/',
  "middleware": [
               modRewrite([
                   '^/base/web/static/foo(.*)$ https://localhost:3000/index.html [P]',
                   '^/base/web/static/(.*)$ https://localhost:3000/$1 [P]'
               ])
          ]
};

It seems that livereload that is used by the angular-cli can only change the port, and even that has to be done from the command line when server is started.

Is there a reason why angular-cli can't use lite-server by default and thus make it possible for more advanced configurations? If that is not possible, is it possible to add documentation about how use lite-server instead of livereload?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions