View Original Text

Hide Table of Contents

About this site

I have a respectable collection of Classic Home Computers (and some plain old ones, that I keep as tokens of better times) that I'm very found of.

Worst, I know how to use them.

Even worst, I know how they work internally.

And worst as possible, there're people around the World that thinks this is interesting! :-)

This site is a way to get everything together.

A lot of content will be in PT_BR, as there's a lot of brazilians on the user's group I attend. Gradual migration to English are currently work in progress, but a lot of mixed content is unavoidable.

Some mechanism for dual language content is something that I'm reseraching, a propotype is already implemented on my Porfolio - unfortunatelly not applicable on the "Content Management System" I'm using here.

Technical details

Infra

The site is hosted on a t2.micro appliance from AWS that is shared with a lot of other sites of mine.

A complete description can be found here.

Content Management

Since this site is essentially static content being updated now and then, there's no need of a full blown CMS (Content Management System).

However, creating content directly on HTML/CSS is unfeasible - I'm not a front-end developer, I don't want to deal with this mess (and I hate Javascript, by the way!).

A simple, effective (but granted, limited) solution was adopted: MarkDown. Howeveer, using a dev-side generator is cumbersome - I want to checkout the content from my CMS (Code Management System) right into the server directories and that's it.

So render_markdown was adopted to the task, with NGINX proxying into it by UWSGI and caching the results to prevent server load.

Adittionally, and since the content is versioned while the Deliverables are not, the Deliverables (disk images, videos and other downloadable files) are kept in a separated file system. Again, NGINX was instrumented to seamlessly tie the static content, dynamic content and deliverables file systems - so I have full freedom to move them around the file system (or even machines) without affecting the content at all.

Again, a full discussion is (will =P) available in the Sandbox.