23 · 01

Released CirruxCache 0.4.2

I have just released a new minor version of CirruxCache. This new version includes several bugfixes and third party library upgrades.

Here is the change list of the 0.4.2:
  • Admin panel: upgraded jquery, jquery-ui et jquery-form to the latest versions.
  • Store service: fixed file upload (which was not working anymore on appengine with billing mode enabled).
  • Some code cleanup
This update is not critical, I invite you to upgrade only if you are experiencing problems with the admin panel or the store service.

Thanks to Doug Tung who shared me an appengine account with billing mode enabled, that was really helpful for debugging.
26 · 10

CirruxCache 0.4.1 is out!

An easy way to use Google Appengine as a personal CDN! CirruxCache 0.4.1 is out, so let me show you a set of new cool features!

CirruxCache provides a software solution to dynamically cache HTTP objects on Google Appengine (using the Datastore and the Memcache services).

Since the last release, I received a lot of good comments and smart suggestions. Fortunately, Some of you increased the size of my todo-list and a bunch of nice ideas are still in the box.

Let’s take a look at this release:

  • Admin panel now includes a config helper (find here screenshots and documentation).
  • Object flushing has been fixed in the admin panel, give it a try!
  • The Cache service now includes a “Content Prefetching” feature. When it is enabled, HTML pages are interpreted. All associated content are loaded in the cache before the user request them. So it speeds up the first page loading. It is experimental for the moment, but it works (it is enabled on this blog!).
  • A new Image service enables you to delegate image transformation to CirruxCache. For example, you won’t need to upload images previews or thumbnail on your website anymore, let CirruxCache generate them and cache them on the fly! (All images on this page are generated this way).
  • Config has been simplified: you don’t need to edit the main “app.py” file. It is located in a file named “config.py”. On top of that, all internal services (admin, cron, store) are now included by default, you can forget them! (Install documentation page has been updated).
  • A lot of bugfixes which improved the caching mechanism.

I hope you will enjoy this new release, check it out on the download page.

I would like to share with you the Users page, I try to list some of you using CirruxCache. This pagedoes not have much success, please take a look!

Finally, I warmly encourage you to subscribe to the CirruxCache group, it is really cool to get help and to provide advices to other users.

Spread the word!

 

21 · 07

CirruxCache: Advanced configuration sample

That's it! This whole blog is cached and directly delivered by CirruxCache (only static files were cached before). My origin server is a tiny eeebox connected through my personal ISP. So this configuration is a good challenge to offload my tiny web server as much as possible. I think this is a good opportunity to show an example of a configuration which is a little bit more evolved. The point is, I cannot set the same cache TTL for the whole website, and actually, I want to cache several websites...
# URL mapping
urls = {}

base = (
'/_admin/(.*)', 'Admin',
'/_store/(.*)', 'Store',
'/_cron/(.*)', 'Cron'
)

urls['default'] = base + (
'(/debug/.*)', 'Debug',
'/(.*)', 'Root'
)

urls['www.shad.cc'] = base + (
'(/themes/.*)', 'Blog_Static',
'(/plugins/.*)', 'Blog_Static',
'(/admin/.*)', 'Blog_Forward',
'(/.*)', 'Blog_Page'
)

urls['www.zaphod.eu'] = base + (
'(/pub/.*)', 'Zaphod_Redirect',
'(/.*)', 'Zaphod'
)

# still supporting the old config

urls['cdn.shad.cc'] = base + (
'/blog(/.*)', 'Blog_Static',
'/(.*)', 'Root'
)

urls['cdn.zaphod.eu'] = base + (
'(/admin/.*)', 'Zaphod',
'/(.*)', 'Root'
)

# POP definition
# You can define and configure your Point Of Presence

class Blog_Static(cache.Service):
origin = 'http://orig.shad.cc'
forceTTL = 2592000 # 1 month
ignoreQueryString = True
forwardPost = False
allowFlushFrom = ['x.x.x.x']

class Blog_Page(cache.Service):
origin = 'http://orig.shad.cc'
forceTTL = 3600 # 1 hour
ignoreQueryString = True
forwardPost = True
allowFlushFrom = ['x.x.x.x']

class Blog_Forward(forward.Service):
origin = 'http://orig.shad.cc'

class Zaphod(cache.Service):
origin = 'http://orig.zaphod.eu'
forceTTL = 2592000 # 1 month
ignoreQueryString = True
forwardPost = False
allowFlushFrom = ['x.x.x.x']

class Zaphod_Redirect(redirect.Service):
origin = 'http://zaphod.eu'

# !POP
I think this configuration is enough readable to avoid any explanation. However, do not hesitate to leave any comments.
Finally, I created a google groups to centralize all help requests. So if you need help, go to http://groups.google.com/group/cirr... or send an email to cirruxcache 'at' googlegroups 'dot' com.
11 · 03

CirruxCache 0.2.1 is released

I have just released a new version (0.2.1) of CirruxCache. To remember:

CirruxCache provides a software solution to dynamically cache HTTP objects on Google Appengine (using the Datastore and the Memcache services).

This new version includes an interesting set of features:

  • allow object flushing from restricted IP
  • configure a PoP (Point of Presence) according to a virtual host
  • several behaviors (cache, redirect, forward)

In more details, the last feature is the ability to configure a point of presence to differ from a classical caching mechanism. For example, I may want to configure "/admin/*" on my website to be redirected on the origin without caching.

Of course, this release includes several bugfixes, especially a fix on the "Expires" HTTP header which improves the caching performances.

Do not hesitate to test this new version and to comment any bugs or any suggestions.

30 · 10

CirruxCache: speeds up your HTTP app using Google Appengine as a CDN

It is a great moment, for the first time since I have started to work at Zoomorama, I have just released as open-source an important part of our server platform.

I previously explained how to use Google AppEngine as a Content Delivery Network (CDN). CirruxCache project concretizes this idea. I released the first version based as the one we use in production.

Here is the features it currently supports:

  • honor Cache-Control
  • cache TTL override
  • several POP (Point Of Presence) configuration mapped on custom base-url
  • ignore query string
  • POST forwarding
  • expired entries garbage collection
  • extensibility


CirruxCache is not documented at the moment even if you would be able to use it after reading the comments in the app.py file. I'll document this app in the next few days, but if you need more documentation, don't hesitate to contact me.

The project website.

Pages