#chyrp

[48techblog]

Wordpress import for Chyrp

Chyrp is a lightweight blogging engine, written in PHP, working with SQLite and MySQL. It is possible to create different types of posts, e.g. Text, Video, Photo, Link and Quote. It looks like a good open-source alternative for Tumblr.

I currently try out Chyrp, thinking about to replace my private Wordpress blog. The recent Chyrp version includes an option to import content from the Wordpress-XML export file. But it didn't work for exports from Wordpress.com-Blogs and the default import creates only Text posts in Chyrp, regardless of the post type of the original Wordpress data. So I fixed it and added an additional chyrp module that enables the import of types posts. My Wordpress branch for Chyrp improves:

imports from wordpress.com is possible

tag import is fixed (only with enabled tag module)

category import was added (only with enabled category module)

import typed Wordpress posts (link, quote, video, image) to the right Chyrp feathers (link, quote, video, photo) if they are enabled

Unknown post types are still imported as text feather in Chryp, e.g. gallery posts in Wordpress. Currently it is not possible to import them as Photo posts in Chyrp because the photo feather only allows one image per post.

How to import content from Wordpress.com to Chyrp

Go to your Wordpress.com blog dashboard and navigate to the Tools/Export option. Download your data from there as XML and safe it.

In Chyrp you need to enable the module "Wordpress Post Types Importer" and the Link, Quote, Photo and Video feathers.

In Chyrp you go to Manage/Import and:

choose your Wordpress-XML export file as import data

fill in the URL prefix that was used in to link media (images) in the Wordpress posts. For WP.com it probably is: http://{{yourblogname}}.files.wordpress.com/

Wait for the success message.

Check Manage/Posts to control the import.

That's it.

[dnevnikeklektika]

Novi Chyrp, novi hosting, stari dnevnik

Ovaj vikend sam manje-više potrošio na udateovanje ovog sajta, nešto što odgađam već neko vreme. Razloga ima više, poput potrebe za upgradeom Chyrpa (što je posebna priča, više o tome dole), do uvrnute pojave otkazivanja određenih delova sajta, prebacivanja na drugi hosting(Media Temple) (iskoristitie referal link ukoliko vam treba dobar hosting) itd.

Chyrp — CMS za ljude koji vole da se cimaju

Kada je izašao, hvalio sam ovaj CMS na sva usta. Baš mi je bilo drago što se pojavila instalabilna tumblelogging[1] aplikacija koja nije kompletna katastrofa (alternativa je Gelato, 'nuff said), i ništa me nije sprečilo da počnem da je koristim uprkos nezrelosti softvera.

Problem međutim nije nezrelost softvera, problem je način na koji se softver održava. Autor Chyrpa insistira da se "prati korak" razvoja preko Gita, koga jako puno ljudi uopšte ne koristi, niti je čulo za isti, a kamoli da ima shell pristup svom serveru. Kroz nekoliko pređašnjih verzija (pa i ovoj poslednjoj "zvaničnoj 2.0") se provlače propusti koji su u najgorem slučaju 5min fixevi (tipa nedostaju ikonice jer putanje nisu dobre, itd), dok se obraća pažnja na neke stvari koje su potpuno trivijalne, poput mincanja fontova u navigaciji administracije. Apsurd.

No, da ne bude da samo pljujem, stvari su se sa ovom verzijom zaista popravile. Instalacija je laka i ovo je jedini put da nisam imao problema oko prebacivanja, upgradea i ostalih akcija oko prebacivanja. Ono što je ostao problem, odnosno boljka nezrelih sistema, je to da se i dalje menjaju stvari vezane za teme, tj. ono što se kod Chyrpa zave Twig templating engine Čim se pogleda ova stranica sa referencama, vidi se da se radi o nerdovskom izdrkavanju, a ne o dobrom rešenju za korisnike. Sva sreća pa je priroda sistema jednostavna, pa pravljenje tema nije teško, inače bi bio pakao navići se i koristiti Chyrp.

Na kraju…

Pored svega ovoga, odlučio sam da ostanem na Chyrpu, čak ću i dalje da ga preporučim ljudima koji traže tumblelog aplikaciju koju mogu da instaliraju na svoj server. Verujem da će sistem kad-tad da sazri, i to će onda biti jedna fina aplikacija, a do tada mogu da uživaju u nedostatku konkurencije. Hint.

1Tumblelogovi su blogovi koji diferenciraju tipove postova (tekst, citat, audio, video, fotografija, link, itd) i generalno su orijentisani na linkovanje, a ne na autorski sadržaj. Tumblr je koliko znam inicirao celu priču i trend ovog načina blogovanja.

[weekdayw4rrior-blog]

Back to the Beginning

Recently I've moved from Blogspot to here. This is a little back story of my "blogging life", which deserves to be told because right now I feel like I'm back to where I started. For the past four months, I've been in search for the perfect blogging platform. Now, I'm no "noob" when it comes to blogging and when it comes to the interwebs. I've been blogging, graphic and web designing since I was 12 (I even had my mom buy me a domain name for my 13th birthday) and since then I've always had this attachment to Wordpress. I remember the days when I was one of those girls who set up a website on a free host to create free resources such as Photoshop brushes, tutorials and little glitter graphics. Looking back at myself then, I honestly wish I didn't start out that way. It was amusing because I tried so hard to be like all these other sites and quite frankly, I wasn't getting far in terms of frequent visitors. Then, I discovered this content management platform called Cute PHP. A lot of the people in the community I had been a member in used it, so I thought "Okay, why the hell not?" I can't say that was the start of my blogging though. I mostly used it for "site updates" and the only times I actually felt the need to "blog" personally, was when I felt the need to rant. I believe the real start of my blogging was when I found Jemjabella.co.uk, through her famous Pants Awards, in which she critiques certain websites (like mine, at the time.) I don't know what exactly compelled me to take coding and aesthetics more seriously, but I'm pretty sure it had something to do with the fear of being slapped in the face with a Pants Award. Like I said, I tried hard to fit in. Soon, I learned of the security (or lack thereof) that came with Cute PHP and decided that perhaps it was time to actually switch to a much better platform. Wordpress was already incredibly popular at the time so I gave it a go. I brushed up on my PHP and started designing my own themes. I believe that that time held the proudest moments of my times as a blogger and designer, because I felt so 1337. I tested another blogging engine called Chyrp but unfortunately my domain's host didn't support PHP 5 at that time yet, which sucks because I paid them $9.00 a month. That ain't cool. Although, I suppose that was understandable because PHP 5 had only started to become supported during that time. After all that adventure and learning, I unfortunately stopped blogging and coding when I was around 14 or so, letting my domain die along with the identity I've made in a certain community of bloggers. The reason why I did so? I completely forget, but whatever it was, I shouldn't have let myself stop. Around a year ago, I decided to give blogging another shot. I didn't necessarily want to go back to designing yet however (I am now, but that's a different story.) I jumped from Tumblr to Livejournal to Tumblr and stayed there until I realized no one actually "blogs" text on Tumblr. I went to Jux, which mind you, is a pretty awesome site. Then I went to Blogger/Blogspot and I stuck to it for months. Honestly, it's not bad at all. In fact, it's a pretty good blogging engine. However, the customizability of the templates turned me off. It was very difficult, especially for someone who hadn't touched code in a long time, for me to comprehend the structure. I created an account here to compare Wordpress and Blogger. They both have their ups and downs but honestly, the whole time I was blogging on Blogger, I had an itch to move to WP. So here I am, back to where I started. I'm hoping I'll stick around long enough to upgrade and code my own theme, maybe even buy myself a domain.

[mgrilec]

Raspberry Pi usable web server

Everyone wants to use their rpi for hosting their blogs or whatever, installing the typical LAMP. In my experience the rpi is too slow for Apache, MySQL and Wordpress, so I wanted to setup a CPU and memory light stack. It needs to have clean URL's, and load in a reasonable time. I eventually dropped it because of my connection's terrible upload.

The speed setup I wanted:

raspbian - the current recommended OS

lighttpd - because nginx is impossible to configure

sqlite3 - less memory usage and more speed then mysql

chyrp - wordpress is just too heavy

Resources I used:

http://www.lowendbox.com/blog/wordpress-cheap-vps-lowendscript/ Here you'll find a script and a discussion about setting up a low memory VPS for hosting wordpress blogs. Gave me a decent start.

http://www.lowendbox.com/blog/yes-you-can-run-18-static-sites-on-a-64mb-link-1-vps/ Another lowendbox post about sqeezing the last drop of memory from a VPS. This is an interesting setup using lighttpd and mysql for a memory-light solution while I needed something more CPU friendly.

http://www.raspberrypi.org/phpBB3/viewtopic.php?f=26&t=9566 A nice step-by-step tutorial on setting up a LLMP (Linux, Lighttpd, MySQL and PHP) server on the rpi. Still, MySQL is too much.

http://cc.davisremmel.com/2012/02/24/how-to-transform-a-stock-pogoplug-into-a-lean-mean-lighttpd-chryp-sqlite-postfix-serving-machine/ This is the real deal. Lighttpd with chyrp running on a pogoplug which is a box similar to the rpi. Working OK, but has some unneeded stuff like a lua script supported url rewrite.

http://chyrp.net/discuss/topic/running-chyrp-with-sqlite-and-lighttpd-from-a-pogoplug/ Here's the discussion about the above but with a suggestion to lose the lua script and the mod_magnet dependency. The site is down, but google cache has it.

That's all you need. Start by installing lighttpd, enabling FastCGI, caching and compression. I tweaked the setup a bit more by installing php5-xcache which brought the page load times from 5s to 2s.

I also ran into several problems such as:

lighttpd service won't stop; the configuration from one of the sites above didn't have a pid file in the config so you'd have to kill -9 the lighttpd  process.

pages loaded from the cache didn't correctly handle php zlib compression (receiving warnings and errors about using zlib), so I just turned it off, never finding out why

few quirks caused by spelling in the config files or something similar

[softaculousampps-blog]

Script Updates :

1) Chyrp -> 2.1.2 2) XMB -> 1.9.11.13 3) Form Tools -> 2.2.1 4) FrontAccounting -> 2.3.10

[tokolo-blog-blog]

!