Skip to main content

Installing Storytlr the lifestreaming platform

"Storytlr is an open source lifestreaming and micro blogging platform. You can use it for a single user or it can act as a host for many people all from the same installation."

I've been looking for something like Storytlr for a few months now or at least trying to do it with Drupal. While I love Drupal and FeedAPI I did not want to spend all that time building a lifestream website. So I've been playing around with Storytlr instead and found it very easy. Here is how I got it up and running on a Ubuntu EC2 server. You can also check out the official Storytlr install instructions.

Assumptions:
  • LAMP stack installed and running.
  • Domain setup for a directory.
  • MySQL database and user ready to go.
Lets get started!

Get the code:
wget http://storytlr.googlecode.com/files/storytlr-0.9.2.tgz
tar -xvzf storytlr-0.9.2.tgz
You can find out the latest stable release on Storytlr's downloads page.

Import the database:
Within protected/install is database.sql. Import this into your empty database.
mysql -u username -p -D databasename < database.sql
Make sure you replace username, and databasename with your specific choices, and enter the password when prompted.

Configure Storytlr:
in protected/config copy config.ini.sample to config.ini.

A few settings I've modified:

  • db.username
  • db.password
  • db.dbname
  • security.cookie
  • web.host
  • web.timezone - list of timezones.
  • app.from_email
  • app.admin_email
  • flickr.api_key - Only if you intend on importing Flickr photos. Get one here.
Folder permissions:
You have to make protected/logs, and protected/upload writeable.

chmod a+w protected/logs protected/upload



PHP Tidy:
I had to install the PHP Tidy package for several of the imports to work including RSS feeds.
sudo apt-get install php5-tidy


Login:
You can now login to your site using the default username:password of admin:storytlr. Make sure you change these.


Finishing:
Now you can pick your theme and start importing your social identity.

Update - Cron:
To get Cron running you have to execute the protected/tools/update.php script directly while specifying a username. This is what mine looks like to update every five minutes.
*/5 * * * * /usr/bin/php5 /home/www/storytlr/protected/tools/update.php admin


Since I'm a coder I also installed the GitHub plugin.

You can check out my lifestream here: http://stream.abrah.am. Link to your lifestream site in the comments.

UPDATE: Changed to a cleaner Cron command.

Comments

  1. I followed the official instructions, then ones here ( I did not have permissions set on the upload and logs directoreis) but mine still does not work.

    I get a 404 error and I found the following in my server error logs.

    [20-Jan-2010 21:39:34] PHP Notice: Zend_Loader::Zend_Loader::registerAutoload is deprecated as of 1.8.0 and will be removed with 2.0.0; use Zend_Loader_Autoloader instead in /home5/xxxx/public_html/live/protected/library/Zend/Loader.php on line 207

    I am on BlueHost which the official documentation claims works. This is all very frustrating.

    ReplyDelete
  2. Great instructions but i was wondering how to get the cron working correctly?

    mine is at cubicgarden.com

    ReplyDelete
  3. @Khurt: What do you mean by "I did not have permissions set on the upload and logs directoreis"? You where not able to change the permissions?

    ReplyDelete
  4. @cubicgarden: I added cron instructions to the post.

    ReplyDelete
  5. Thanks for putting these together! is the username fed to the cron the username for the Storytlr db or for the shell?

    ReplyDelete
  6. @Infiniteunity3D: the username that logs you into the web interface. "Admin" by default.

    ReplyDelete

Post a Comment

Popular posts from this blog

Sync is currently experiencing problems

Update : I now recommend you install Google Chrome  and  disable  the built in Browser as it supports encrypting all synced data. After picking up a gorgeous  Galaxy Nexus yesterday I was running into an issue where my browser data wasn't syncing to the phone. After a little Googling I found this is commonly caused by having all of my synced Chrome data encrypted instead of the default of only encrypting the passwords. These are the steps I went through to get my dat syncing again without losing any of it. The exact error I was getting was "Sync is currently experiencing problems. It will be back shortly." In Google Chrome open the personal stuff settings page by clicking this link or by opening the wrench menu, and click on "signed in with example@gmail.com".  Hit "disconnect your Google Account" to temporarily disable syncing from your browser. Visit the Google Dashboard and "Stop sync and delete data from Google". I waite

A month of Flutter: a look back

Originally published on bendyworks.com . This is it. 31 blog posts in 31 days. Writing  a month of flutter  has been a ton of work but also lots of fun and a good learning experience. I really appreciate how supportive and and positive everyone as been. Publishing experience For the series I've been posting on  bendyworks.com ,  DEV ,  my personal blog , and  Medium . After publishing to these sites, I would put the Bendyworks link on  Twitter ,  Reddit , and the  Flutter Study Group Slack . Posting to DEV was easy as they use Markdown just like the Bendworks blog. DEV also has built in support for a  series of posts  so it's easy to read the entire series. I did have to manually upload any embedded images. DEV also has a number of  liquid tags  for embedding things like GitHub issues that I didn't make as much use of as I should have. Blogger is rich text so it was easy to copy/paste the rendered posts. This would hotlink all the images though so I had to rem

A month of Flutter: the real hero animation

Originally published on bendyworks.com . For the last post before the month's wrap up tomorrow, I wanted to do something more fun: use a  hero animation between the home page list and the individual post page. When I first implemented the  Hero  animation it never worked going back from a  PostPage  to the  HomePage . The reason was that  HomePage  would get rerendered and that would  generate new fake posts . So I moved the fake data generation up a level to  MyApp  and pass it into  HomePage . This is more realistic as going to the  HomePage  shouldn't request the  Post s every time. HomePage ( title: 'Birb' , posts: _loadPosts ( context ), ) The  PostPage  implementation is a simple  StatelessWidget  that takes  Post  and renders a  PostItem . This will become more complex as things like comments and likes are implemented but works for now. class PostPage extends StatelessWidget { const PostPage ({ Key key , @required this