I recently had to help someone who was having trouble setting up a Known site on their Reclaim hosting account. I hit a few gotchas along the way, so I’m jotting them down here with hopes that it helps others.

Installing Known

I live in the console, so after setting up the domain and location via cpanel, I logged in and installed the Known source:

cd ~/mydomain.com;
git https://github.com/idno/known.git . ;
composer install

Resolving 500 error

When visiting the domain, I was confronted with a 500 error.

Digging in the logs, it looked like I was falling foul of some security setting, and the files were being created with group write. So, we need to reset those.

find . -type f | xargs -i{} chmod 644 {}

While we’re at it you’ll want to make your uploads directory writable by the web server.

Set up your database and configure Known

Create a database, database user and password via cpanel.

Because I also was hitting a weird redirect error, I opted to configure known by hand.

Create a file in ~/mydomain.com/configuration/ called config.ini

If this file, put the following information:

database = 'MySQL'
dbname = 'yourdatabase'
dbpass = 'yourpassword'
dbuser = 'yourdbuser'
dbhost = 'localhost'

filesystem = 'local'
uploadpath = '/path/to/mydomain.com/Uploads/'

Make sure you remember the trailing ‘/’ on the upload path.

Hope this helps!

Well, the clocks have gone back, and the nights are drawing in. If you’re anything like me, this means you just want to find somewhere warm to curl up in until spring.

But before you do, I would just like to point you to the fact that Known 1.0 is finally out of the door!

It’s been a long journey to get to this point, but I’m delighted to finally get to a point where we can draw a line in the sand.

Crack open the beverage of your choice, and go download Known 1.0 now!

Just a quick update…

In the run up to the Known 1.0 release, I’ve made a small tweak to the back end caching objects. Essentially, they functionally work the same, but are implemented using symfony cache components.

Further down the line I’m thinking about replacing our cache entirely with symfony in order to allow for easier caching back ends, not to mention the far superior “cache contract” interface.

This is a low level thing, but useful if you’re a plugin developer to know what is coming down the pipe!