|
FreeBSD Ports and Packages Installation and upgrading of ports and packages on FreeBSD. |
|
Thread Tools | Display Modes |
|
|||
Advice on setting up blogging on a FBSD server
I will soon be setting up a new FBSD server at home, for my personal web page. This is a low-traffic website that is mostly just for me to play around with; the main thing it hosts is my own blog which attracts a pretty small crowd - maybe a few dozen hits a day. I'm not specifically looking to increase my web traffic at this point, either.
However, I am looking for something that might be a little easier to manage. Currently its all flat files, which of course become a PITA after a while. My current system is just running Apache22, with no real connection to a database. I would like to set up the new webserver to be a PHP/MySQL configuration, and I am looking through the ports collection for a blogging program. Since I'm setting up a new system, I figure setting up it up properly from the beginning should be a priority. Of course, I know I could just as well do all my blogging through a commercial (or free) effort on some other web server. With my very low total traffic volume that wouldn't be a bad option, but I'd like to try running it from home anyways. Any recommendations? I checked freshports.org and found a few potential candidates - "bblog", "blogsum", "cblog", "nanoblogger", "nibbleblog", and others. Any particular insights from our experts on which ones work better? My first priority in making a choice would likely be ease of use. Second would be security, third would be how it renders as a web site by default (appearance). Flexibility probably wouldn't be of enormous importance, since 99.999% of my blog will be text or simple images. |
|
|||
I have not any experience with it, but http://www.freshports.org/www/wordpress/ seems to be rather popular.
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
|||
Jason Dixon is a semi-popular name in the BSD community (..for his humorous conference talks), he wrote blogsum.. which you listed, but it doesn't use MySQL or PHP.
For popular blogging software like wordpress, you'll need to keep it updated.. as security vulnerabilities appear more often than naught. I can't give you my recommendation, as I do not blog. |
|
|||
FreeBSD News uses Wordpress
Wordpress is IMHO the best platform for blogging. It's simple and easy to use, easy to maintain and has 1000s of plugins to make it even better.
I use it for my FreeBSD News site: http://freebsdnews.net (sorry I'm not allowed to create a hyperlink for this address. Last edited by vermaden; 25th January 2011 at 09:53 AM. Reason: You are now ;) |
|
|||
Quote:
Quote:
Quote:
So basically what I'm aiming for with the blog software is easier maintenance - I should mention also I'd like it to be something that my wife could use as well if she'd want - as well as a more consistent (and easier to change across-the-site) appearance. While I'm sure I could probably do something clever with Perl or PHP to improve on some of this, I'm about to start building a new home server anyways and I think that adopting a more common piece of software for it would be advantageous. |
|
|||
Quote:
Each blog entry is a separate file with a name like 'blog2011-01-24_2210.txt' The write some tiny scripts and/or Makefiles rules to generate a page with HTML links to each entry. You also could have 'make' collect all entries for Janary 2011 in one file, those of Feb 2011 in another.
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
||||
WordPress
I recommend WordPress and, since you want blogs for other family members, I also recommend a Multisite installation. With Multisite, you can create a WordPress.com-like system.
Maintenance: If you choose WordPress, either simple or Multisite, please consider using suPHP as it will allow you to update the blog, plugins and its themes more easily (automatically).
__________________
A daemon in need is a daemon indeed. |
|
|||
I just hacked a sample Makefile which shows how easy it is to append a file or blog entry to a main file without editing the main file
Actually it allows you to create a file out of small building blocks. You only have to deal with the building blocks. Code:
# Makefile to create a blog #Jan 25 22:12 2011-01-25_2209.txt #Jan 25 22:12 2011-01-22_2245.txt #Jan 25 22:13 2011-01-01_1400.txt #Jan 25 22:15 2011-02-01_1623.txt #Jan 25 22:16 2011-02-04_1256.txt YEAR = 2011 JAN != ls ${YEAR}-01* FEB != ls ${YEAR}-02* # maybe better to use a year dir with a subdir for each month # JAN != ls ${YEAR}/01/*txt # but then the Makefile has to be adjusted all: Blog${YEAR}-01.txt Blog${YEAR}-02.txt test: @echo ${YEAR} ${JAN} @echo ${YEAR} ${FEB} Blog${YEAR}-01.txt: ${JAN} cat ${.ALLSRC} > ${.TARGET} Blog${YEAR}-02.txt: ${FEB} cat ${.ALLSRC} > ${.TARGET} clean: rm Blog${YEAR}-??.txt Code:
$ make test 2011 2011-01-01_1400.txt 2011-01-22_2245.txt 2011-01-25_2209.txt 2011 2011-02-01_1623.txt 2011-02-04_1256.txt Code:
Blog${YEAR}-01.txt: ${JAN} cat ${.ALLSRC} > ${.TARGET} The dependencies are the source files defined by the JAN variable 2011-01-01_1400.txt, 2011-01-22_2245.txt and 2011-01-25_2209.txt. If the target 'Blog2011-01.txt' does not exist it will be created. If one of it's dependent files is edited and has a newer time stamp than the target, the target will be recreated. After adding a new blog entry file, the target will again be recreated. Invoking make without any arguments will create or recreate if necessary, the all target, which is the first and thus default target: Code:
$ make cat 2011-01-01_1400.txt 2011-01-22_2245.txt 2011-01-25_2209.txt > Blog2011-01.txt cat 2011-02-01_1623.txt 2011-02-04_1256.txt > Blog2011-02.txt Code:
$ make Let us now create a new blog entry and run make Code:
$ vi 2011-02-05_0812.txt $ make cat 2011-02-01_1623.txt 2011-02-04_1256.txt 2011-02-05_0812.txt > Blog2011-02.txt To experiment, you can download the attachment and extract with: Code:
$ tar xvzf pmBlog.tgz pmBlog pmBlog/2011-01-01_1400.txt pmBlog/2011-01-22_2245.txt pmBlog/2011-01-25_2209.txt pmBlog/2011-02-01_1623.txt pmBlog/2011-02-04_1256.txt pmBlog/2011-02-05_0812.txt pmBlog/Makefile
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Setting up static IP fails + some XEN advice needed. | maxleonca | NetBSD General | 0 | 17th June 2010 04:54 PM |
Advice needed: File server for VPN - samba, NFS? | sim | FreeBSD General | 11 | 4th November 2008 10:48 PM |
Setting up a multi-card serial server | dk_netsvil | General software and network | 14 | 4th October 2008 01:00 PM |
FBSD emulating pdc w/ AD, exchange and print server? | cgc2 | FreeBSD General | 9 | 16th July 2008 04:14 PM |
setting up a proxy server in OpenBSD 4.3 | jrake | OpenBSD General | 1 | 14th May 2008 06:43 PM |