cliss/camel

"Camel" is a blogging platform written in Node.js. It is designed to be fast, simple, and lean.

camel's Issues

Alter `tweetLatestPost()` to Start with 280 Characters Instead of 140

Just a simple fix needed here 😄

Markdown doesn't support footnotes

Camel uses the Markdown parser marked in order to convert from Markdown to HTML. Marked doesn't presently support footnotes, as shown in this issue and this pull request.

Posts with trailing +s not showing up in listings

Posts with trailing +, such as emoji++.md, do not show up in year listings.

In software world, Camel means the "Apache Camel" to every experienced engineer, maybe you want to choose another project name.

In software world, Camel means the "Apache Camel" to every experienced engineer, maybe you want to choose another project name.

Multiple declarations of `externalFilenameForFile()`

Hi, in camel.js, it looks like the function externalFilenameForFile() is declared twice, first with a single parameter (file), and then again with two parameters (file and request).

Function overloading like this isn't allowed in JS. Instead, the second function declaration just clobbers the first one. Thus, all calls to externalFilenameForFile() go straight to the two-argument version. (In fact, if the functions were declared in the opposite order, the single-argument version would end up calling itself over and over.)

RSS Caching Can Return Different Hostnames

If a request comes in after the RSS cache has expired on an unexpected hostname, it can seed that hostname in the cache and return it with requests to the preferred hostname. This appears to only affect the RSS feed because it is returning fully qualified URLs.

Example:

camel on  master
➜ curl http://linode.liss.test/rss | grep linode
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1706    0  1706    0     0   171k      0 --:--:-- --:--:-- --:--:--  416k
]]></description><link>http://www.vt.edu/</link><guid isPermaLink="false">http://linode.liss.test/2015/2/6/sample-link-post</guid><dc:creator><![CDATA[Your Name]]></dc:creator><pubDate>Fri, 06 Feb 2015 22:00:00 GMT</pubDate></item><item><title><![CDATA[Test Post]]></title><description><![CDATA[<p>This is a <em>test post</em> entitled “Test Post”.</p>
]]></description><link>http://linode.liss.test/2014/5/1/sample-post</link><guid isPermaLink="false">http://linode.liss.test/2014/5/1/sample-post</guid><dc:creator><![CDATA[Your Name]]></dc:creator><pubDate>Fri, 02 May 2014 02:50:00 GMT</pubDate></item></channel></rss>

camel on  master
➜ curl http://www.liss.test/rss | grep linode
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1706    0  1706    0     0   161k      0 --:--:-- --:--:-- --:--:--  333k
]]></description><link>http://www.vt.edu/</link><guid isPermaLink="false">http://linode.liss.test/2015/2/6/sample-link-post</guid><dc:creator><![CDATA[Your Name]]></dc:creator><pubDate>Fri, 06 Feb 2015 22:00:00 GMT</pubDate></item><item><title><![CDATA[Test Post]]></title><description><![CDATA[<p>This is a <em>test post</em> entitled “Test Post”.</p>
]]></description><link>http://linode.liss.test/2014/5/1/sample-post</link><guid isPermaLink="false">http://linode.liss.test/2014/5/1/sample-post</guid><dc:creator><![CDATA[Your Name]]></dc:creator><pubDate>Fri, 02 May 2014 02:50:00 GMT</pubDate></item></channel></rss>

This can result in feed readers picking up all feed items as new because the GUIDs change. (Origin: https://fosstodon.org/@drdrang/109905798081310673)

Improve homepage URLs

Rather than having the homepage use query strings for pages, why not a new route?

For example, instead of '/?p=3', why not '/page/3'?

allPostsSortedAndGrouped() isn't cached

Since allPostsSortedAndGrouped() will probably be used in several places (including, for example, the year listing), it too should probably be cached.

Too-long title causes auto-tweet to fail & Camel to die

If a post is created with a really long title, Twitter will balk at the auto-tweet because it's too long, and that will take Camel down due to this line.

The auto-tweeter should be changed to:

• Consider how long a link is once shortened by Twitter
• Consider how long the suffix is (right now, \n\n)
• Automatically truncate long titles if they're over the computed maximum length.

Adding Tags to Camel

Truly, less is more.

I assume this is why Camel is the way it is—fast [first], simple, and relatively straight-forward.

I dig that.

I wouldn't want it any other way.

And yet.

Tags

Yes, those.

I know what you're thinking (you're thinking, "Eh").

I can understand.

Because less is more.

But here's the thing:

Camel needs could use tags. Tags are useful and helpful when used like this, not necessarily like this. Tags don't have to be associated with their oft-icky implementation.

Roger Stringer's fork has tags, but his is based on his own custom variables that make cribbing to your "Standard Camel" fork somewhat non-trivial.

---

Basic support would entail:

1. Basic metadata support for "Tags" (or "Keywords"—whatever you want to call it), be that via the traditional metadataMarker—@@—or via the newest metadata format in 1.5.3, e.g., Tags:
2. Support for /tags and /tags/tag slugs

Using jscs as standard for the project.

Hi @cliss,

What are your thoughts on using jscs as standard to lint and format all js files in Camel Js?

Have a look at this nice little write up about it's capabilities when you have time.

https://medium.com/@addyosmani/auto-formatting-javascript-code-style-fe0f98a923b8

Auto-tweeting broken

Automatic tweeting is broken. The code is getting as far as this line, but no tweets are actually showing up.

`npm start` fails under Homebrew

Not sure if this is a real issue, or I may have missed a step configuring something, but while node ./camel.js starts a local server on port 5000, npm start implodes.