Skip to content

Allow configuration for base path to request asset files. #6121

Closed

Description

@jaesung2061

Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [x] feature request

Versions.

@angular/cli: 1.0.1 .
node: 7.5.0 .
os: darwin x64

Repro steps.

My build target is in ./public/assets directory. The generated files (*.js, *.js.map, index.html) all go into that directory. When the files are generated the script tag urls are like so: http://example.com/file.js

Desired functionality.

I need the script tag urls to be http://example.com/assets/file.js. Notice the /assets/. This is because public is the web root and I'm serving index.html through my backend application. Therefore, when they hit http://example.com, index.html is served even though it's in http://example.com/assets/index.html. I apologize if this is confusing, please ask for clarification if needed.

Mention any other details that might be useful.

http://github.com/jaesung2061/anvel

I currently have it so that the index.php, .htaccess and other files are copied from the angular src directory. Because of #4293

Activity

  1. bviale commented on May 4, 2017

    @bviale

    I think it can be done through the "deployUrl" node of your .angular-cli.json config file.
    If you set

    "apps": [
        {
          ...
          "deployUrl": "/assets/",
          ...
        }
      ],
    

    it should do what you are looking for.
    Reference : https://github.com/angular/angular-cli/wiki/angular-cli

  2. jaesung2061 commented on May 5, 2017

    @jaesung2061
    Author

    @bviale thanks :)

  3. angular-automatic-lock-bot commented on Sep 7, 2019

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  4. locked and limited conversation to collaborators on Sep 7, 2019
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