Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

adding CNAME in 'src' results in CNAMEundefined in 'out' #584

Closed
0xgeert opened this issue Aug 6, 2013 · 3 comments
Closed

adding CNAME in 'src' results in CNAMEundefined in 'out' #584

0xgeert opened this issue Aug 6, 2013 · 3 comments

Comments

@0xgeert
Copy link

0xgeert commented Aug 6, 2013

Just new to Docpad (looks great) so I might be missing something, but I added a CNAME file into the 'src/files'-dir to control access for a custom domain on github.

On generation (docpad generate) is expected a file CNAME to be generated in 'out' Instad it's called CNAMEundefined.

If I had to guess, I'd say this is due to a generator trying to guess the content-type but fails. If so, a way to define in docpad.coffee to let certain files untouched seems appropriate. Looking at http://docpad.org/docs/config this doesn't seem to exist. How would I go about this?

Thanks,
Geert-Jan
@chase
Copy link
Contributor

chase commented Aug 6, 2013

This should not be occurring, honestly. This seems to be a bit of a regression from early versions, I'll look into it if @balupton does not get to it before me.

I assume the issue has to do with the file not having an extension, as you stated.

@chase
Copy link
Contributor

chase commented Aug 6, 2013

Alright, I found the issue. I'll be pushing a new version soon.

@chase chase mentioned this issue Aug 6, 2013
Closed
@0xgeert
Copy link
Author

0xgeert commented Aug 6, 2013

Sorry for the late reply. Came in on other mail. Thanks for the quick fix!

chase added a commit that referenced this issue Aug 10, 2013
@chase
v6.48.1. Bugfix. Improvement.
4e53b21 
- v6.48.1 August 9, 2013
	- Fixed [issue #584](#584)
		- Now the output filename of a file without an extension will remain unchanged
	- Added a test for the aforementioned issue
@chase chase closed this as completed Aug 10, 2013
@balupton balupton mentioned this issue Aug 14, 2013
Closed
balupton pushed a commit that referenced this issue Oct 23, 2013
@chase
v6.48.1. Bugfix. Improvement.
367fc75 
- v6.48.1 August 9, 2013
	- Fixed [issue #584](#584)
		- Now the output filename of a file without an extension will remain unchanged
	- Added a test for the aforementioned issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

v6.48.1. Bugfix. Improvement.
2 participants
@chase @0xgeert