Add configurable static path #875

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
4 participants
@jakevdp

jakevdp commented May 5, 2013

This PR adds a few lines which let the user configure the static output directory, using a new STATIC_OUT_DIR setting.

@avaris

This comment has been minimized.

Show comment
Hide comment
@avaris

avaris May 5, 2013

Member

#795 will address this issue.

Member

avaris commented May 5, 2013

#795 will address this issue.

@jakevdp

This comment has been minimized.

Show comment
Hide comment
@jakevdp

jakevdp May 5, 2013

@avaris - good to know. What is the status of that PR? It seems not to have much action in over a month.

Being able to specify the static path is very important to me: I'm migrating my blog from octopress, and I want to keep links to my downloads consistent (mostly ipython notebooks which are referenced from the nbviewer front page and other places).

I guess I can keep using my own modified branch of pelican until that PR is merged, and then switch the way the paths are referenced.

jakevdp commented May 5, 2013

@avaris - good to know. What is the status of that PR? It seems not to have much action in over a month.

Being able to specify the static path is very important to me: I'm migrating my blog from octopress, and I want to keep links to my downloads consistent (mostly ipython notebooks which are referenced from the nbviewer front page and other places).

I guess I can keep using my own modified branch of pelican until that PR is merged, and then switch the way the paths are referenced.

@justinmayer

This comment has been minimized.

Show comment
Hide comment
@justinmayer

justinmayer May 5, 2013

Member

That PR was on hold so we could ship 3.2 first. The only reason it wasn't merged immediately afterward was that some folk requested it be split up a bit further into smaller, more-digestable chunks. The PR's author, @wking, is occupied until the end of the month, so the fruits of his labor won't land until then.

Also, not sure exactly what you're trying to do, but STATIC_PATHS might be worth a look.

Member

justinmayer commented May 5, 2013

That PR was on hold so we could ship 3.2 first. The only reason it wasn't merged immediately afterward was that some folk requested it be split up a bit further into smaller, more-digestable chunks. The PR's author, @wking, is occupied until the end of the month, so the fruits of his labor won't land until then.

Also, not sure exactly what you're trying to do, but STATIC_PATHS might be worth a look.

@jakevdp

This comment has been minimized.

Show comment
Hide comment
@jakevdp

jakevdp May 5, 2013

The problem is that all directories listed in STATIC_PATHS are saved to a URL within the (hard-coded) 'static' subdirectory. This PR gives the user the option to modify that hard-coded value. I don't see any way to have static paths which don't include /static/ in the URL, short of modifying the source code.

jakevdp commented May 5, 2013

The problem is that all directories listed in STATIC_PATHS are saved to a URL within the (hard-coded) 'static' subdirectory. This PR gives the user the option to modify that hard-coded value. I don't see any way to have static paths which don't include /static/ in the URL, short of modifying the source code.

@wking

This comment has been minimized.

Show comment
Hide comment
@wking

wking May 5, 2013

Contributor

This is my understanding as well. Sorry about the delay in the refactoring, after the 28th I'll have time again ;)

Contributor

wking commented May 5, 2013

This is my understanding as well. Sorry about the delay in the refactoring, after the 28th I'll have time again ;)

@justinmayer

This comment has been minimized.

Show comment
Hide comment
@justinmayer

justinmayer Jun 16, 2013

Member

Now that EXTRA_PATH_METADATA has landed and the hard-coded /static/ prefix has been removed, you should now be able copy files to any arbitrary path.

Member

justinmayer commented Jun 16, 2013

Now that EXTRA_PATH_METADATA has landed and the hard-coded /static/ prefix has been removed, you should now be able copy files to any arbitrary path.

@rgommers rgommers referenced this pull request in numfocus/numfocus.org Nov 10, 2013

Closed

pelican 3.3 breaks images #55

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