Flatpress - Flat file CMS/Blogging Platform

[binil]

Flatpress is a script which uses only txt files to store data. No database is used. I have using it on my personal blog for quite some time. I have found it to be very good for my use.

http://flatpress.org/home/

Advatages as per my view:
- very easy to backup and restore - just backup the entire site using ftp - also very easy to restore to a new server - just ftp the files to the new server.
- should be very good in a shared hosting environment - as it doesn't use any database, I have found that it works very well even in very bad hosting environment.

Disadvantages as per my view:
- Single user only. can't have more than one user - so not suitable for working with multiple people.
- A very small community - flatpress has a very small community - so you don't see very high number of themes and plugins - never the less, the small community is pretty active.
- Inode limit could create problems - since most shared hosting has an inode limit, this could create a problem with flatpress easily - since each post,page,comment etc is stored as a txt file, and there are directories in which these txt files are stored, this will create a huge number of inodes..

 

[Hazem]

Based on my own experience , I do not recommend this at all , this is one of the most spam vulnerable scripts I've ever seen in my life :undecided:
I am afraid I can't give you a link to my old flat press but I got like 70 gb bandwidth / mo. of spam comments there before I killed it.

 

[binil]

Every blog or cms with user feedback (commenting) is susceptible to spam.

Flatpress has a quickspam option and akismet plugin built in it - configure quickspam and enable this akismet plugin. You need to have WordPress.com API Key for akismet to work. I don't have much of any issues with my personal blog running flatpress.

 

[Genesis]

Akismet is the one plugin I never install. Just too aggressive to my taste. There are many better ones out there that are much less intrusive.

 

[smalpierre]

When your content grows, your site slows ... that's the downside of a flat file system. You don't even have to have the best database design, as long as it's halfway decent it will outperform the flat file. Unless it's super tiny ...

 

[silenceangel]

still better to use sql database i think,. ist not recomended :\

 

[riddict]

I don't think a file for database is not a good option. When You have a lot of blog entry, the site will become so much slower as it tends to read the whole file and then explode it.

 

[binil]

I don't think a file for database is not a good option. When You have a lot of blog entry, the site will become so much slower as it tends to read the whole file and then explode it.

Flatpress does not use a single file like sqlite, instead it stores each blog post as a seperate text file.

 

[strokerace]

I don't think a file for database is not a good option. When You have a lot of blog entry, the site will become so much slower as it tends to read the whole file and then explode it.

Flatpress does not use a single file like sqlite, instead it stores each blog post as a seperate text file.

Sqlite doesn't use a file. It stores them as data in the sql database as text. Its also a bad idea to store it as a text file as it causes clutter in the file system. So your file structure will increase with each new entry. It now causes to issues. 1, there is more data stored as you have to store an entry for that blog in the database and 2, if you delete a file, it will still show up as the entry would still be in the database with no file attached to it. Where storing it in the database structure, when you delete, it deletes all record of it.

 

[binil]

I haven't faced any issues when deleting any entries from the admin panel in flatpress. I have felt that loading of pages is pretty fast even when there are a good amount of entries in the blog.