HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
280north
cappuccino
Objective-J2008–2011
280north / cappuccino

cappuccino

MOVED TO https://github.com/cappuccino/cappuccino

9Distinct people
13Mentions
0Explicit recommenders
45GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

MOVED TO https://github.com/cappuccino/cappuccino

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:56:33 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year13 dated mentions

Observed mentions: 2008-09-04 18:06:45 UTC to 2011-07-18 19:20:22 UTC.

02462008-01-01 00:00:00 UTC to 2009-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20082009-01-01 00:00:00 UTC to 2010-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20092010-01-01 00:00:00 UTC to 2011-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2011

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20082008-01-01 00:00:00 UTC2009-01-01 00:00:00 UTC303
20092009-01-01 00:00:00 UTC2010-01-01 00:00:00 UTC000
20102010-01-01 00:00:00 UTC2011-01-01 00:00:00 UTC404
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC615

What Hacker News says

3 sources
Deploying a long-running JavaScript application, like 280 Slides (and most Cappuccino apps), on one hand can be trivial (just copy the client resources to your webserver!), but also can be an interesting challenge. Namely keeping clients running an old version of the client-side code using the corresponding version of the server-side app. When you add in something like Gears for offline access it gets even tougher. There was a good presentation at Google IO that covered all these issues: http://sites.google.com/site/io/taking-large-scale-applicati... We wrote a little custom code (we call it "bake") for deploying Cappuccino applications: "bake": http://github.com/280north/cappuccino/tree/master/Tools/bake... sample "bakefile": http://github.com/280north/cappuccino/tree/master/Tools/bake... It pulls your code from git (but could easily do
Read the rest
local files, scp, rsync, svn, etc), runs an optional build command (like "ant"), copies source paths to destination paths in a deployment directory, gzips the deployment directory, scp's the code to your server(s), ungzips it, and does a little magic... Each version is placed in it's entirety in a uniquely named (unix timestamp) subdirectory. We could just redirect from "/" to "/1221268756/" (for example) but that's incredibly ugly, so we use the little known HTML <base> tag to trick it. The index.html file in "/" is identical to the one in "/1221268756/" except it has a <base> tag which tells the app all URLs are relative to "/1221268756/" instead of the default containing directory ("/"). And it actually seems to work really well. The big advantage of this is you can set your cache expire date arbitrarily far in the future, and your entire app will be cached until you change index.html to point to a new <base>. 280 Slides, which is ~2.6MB uncompressed, loads on my computer in about 1.5 seconds if it's cached. The only problem with this approach is when you deploy, all clients will have to re-download every resource, even ones that don't change. A more granular system would be ideal, but significantly more complex. I looked at Capistrano briefly but decided against it for some reason I can't remember. Perhaps that would have been better, but c'est la vie...
In Ask HN: how to push to a live site?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.