Answers.Body: <p>I can't think of a way to do this.</p>
  
  <p>Problem #1: the URLs generated for control panel resources are based on the Craft install's Site URL (whether that's defined in Settings->General or via the <a href="https://craftcms.com/docs/config-settings#siteUrl" rel="nofollow">config setting</a> and that is taken into account when creating <em>all</em> links in Craft, not just for control panel resources requests.</p>
  
  <p>Problem #2: in Craft 2, all control panel resources are actually served through PHP, not the web server.  I suspect even if you found a way around #1, this would cause separate issues.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-08-29T21:55:38.230Z
Answers.Text: Thank you. I came to the same conclusion and hoped someone with more experience on the platform might know a workaround. Thanks again for your help!
Answers.UserDisplayName: Chris
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-08-29T21:42:27.060Z
Answers.LastActivityDate: 2016-08-29T21:42:27.060Z
Answers.UserDisplayName: Brad Bell
Body: <p>I'm attempting to get the Control Panel assets to load from a CDN instead of locally from Craft.</p>
  
  <p>Going through the config options <a href="https://craftcms.com/docs/config-settings" rel="nofollow">here</a> and <a href="https://craftcms.com/docs/multi-environment-configs" rel="nofollow">here</a> I can't seem to find a way to change the asset URL.</p>
  
  <p>Is there any way to change the asset url (in this case for control panel)?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-08-29T21:32:18.897Z
Comments.Text: Are you trying to get proper Assets (https://craftcms.com/docs/assets) to be served from a CDN (and therefore would be served from both the control panel and front-end of the site) or are you actually trying to get the CSS/JS/Images that Craft uses to style the control panel to be served form a CDN?
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-08-29T21:34:54.147Z
Comments.Text: Thanks for the clarification question - I'm attempting to get the assets (JS, CSS, etc) for the Control Panel to be served from CDN.
Comments.UserDisplayName: Chris
Tags: <assets><control-panel>
Title: Changing the asset url for the Control Panel
ThreadText: # Changing the asset url for the Control Panel
  
  (Asked by: username_0 on 2016-08-29)
  
  I'm attempting to get the Control Panel assets to load from a CDN instead of locally from Craft.
  
  Going through the config options [here](https://craftcms.com/docs/config-settings) and [here](https://craftcms.com/docs/multi-environment-configs) I can't seem to find a way to change the asset URL.
  
  Is there any way to change the asset url (in this case for control panel)?
  
  **Tags:** assets, control-panel
  
  > **Comments:**
  > **username_1**: Are you trying to get proper Assets (https://craftcms.com/docs/assets) to be served from a CDN (and therefore would be served from both the control panel and front-end of the site) or are you actually trying to get the CSS/JS/Images that Craft uses to style the control panel to be served form a CDN?  
  > **username_0**: Thanks for the clarification question - I'm attempting to get the assets (JS, CSS, etc) for the Control Panel to be served from CDN.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-08-29. Score: 2 | Accepted answer
  
  I can't think of a way to do this.
  
  Problem #1: the URLs generated for control panel resources are based on the Craft install's Site URL (whether that's defined in Settings->General or via the [config setting](https://craftcms.com/docs/config-settings#siteUrl) and that is taken into account when creating *all* links in Craft, not just for control panel resources requests.
  
  Problem #2: in Craft 2, all control panel resources are actually served through PHP, not the web server. I suspect even if you found a way around #1, this would cause separate issues.
  
  > **Comments:**
  > **username_0**: Thank you. I came to the same conclusion and hoped someone with more experience on the platform might know a workaround. Thanks again for your help!  
  
  ---
  
  