Jaret Pfluger

Well, I'm glad you proposed fieldNameTruncated and not me! :+1: I had thought about incorporating it originally but thought I'd make a mistake somewhere due to me being new to...

I cleaned up the files per your original comments and reran the npm test (which passed). Re. truncated field. Along the lines of the idea in your first paragraph. So...

Good point. Could be done that way. It's a larger federated project, so we used a subdomain to host common resources. I thought of different use case that might have...

I like your idea of `--base-path` - it is a better and more correct name than `--website`. The `--font-subdir` parameter is a good idea and I understand what you say...

With some retooling for my complex example, what might work is using a combination of `--base-path` and `--font-subdir` and `--output`. The assumption is that `font.css` is not automatically created inside...

Did you use this at line [95](https://github.com/jpfluger/examples/blob/master/ubuntu-14.04/sysvinit/node-app#L95) in the init.d template?

I had a similar need just now to list all map keys (your 2nd paragraph). Here's a [gist](https://gist.github.com/jpfluger/046354e64ff9eba1ebd7697adc2f8798) of what I came up with. It's comprised of 3 files, one...

For more info on pushing tags, see [here](https://git-scm.com/book/en/v2/Git-Basics-Tagging) and [here](https://stackoverflow.com/questions/5195859/how-do-you-push-a-tag-to-a-remote-repository-using-git). Here's a start... ``` git tag v0.1.0 git push origin v0.1.0 ``` The tag should automatically appear in github.

Yes! The downgrade worked! Thank you so much @Salicorne!!! :clap: :+1: :100: