I think of my own script blogger in my spare time [spare time] [blogger]
Q: Well, I have nothing better to do until I get a job, I think I might as well learn something new and do something productive with it .
Anyways, I thought of writing my own blog software / script / regardless of how I .
The visualize:
1. Log into the item page
2. my entry for the current type day
3. Save the blogger will it
Then:
1. Update main page with the latest entry
2. Cut the main entry and storage for x number of days (eg, keep the main page to have more than 10 days after entry)
3. Update the backup page that all entries (archives them) that Ive done to today.
Ive never really used for bloggers, so I would not know how it actually works. But I think the general idea?
Anyways, here are my questions:
1. Should I change / updates directly to HTML pages?
2. If so, this means that I must make my HTML pages writable . Is not that dangerous?
3. If not, I should remain as separate items in the database entry, or text files?
4. Which should be easier, written as a CGI script or PHP script?
Im sorry Im not a great writer, so if the above are confusing, let me know. But the basic idea should probably be: How can I go on my own blogger writing for my site?
yes is reinvent the wheel . but practice makes perfect,)
Thanks much. -)
Re:Originally posted by: guy
hmmm…
so the best thing is to store the data in mysql database?
but wouldn't that put the load on the server if everytime someone wants to read my entry, they have to make a request to the database and retrieve data, etc?
but if that means less stress compared to modifying text files, maybe that's an option…
well, i'll give it a start somehow.
thanks -)
a flat-file will be weak if you're going to have many posts. sql will be better.
-Case
Re:okay, i'll have it checked out soon.
thanks all ^_^
Re:undeadly.org has a nice C based cgi for posting news. Maybe that would be something to work off of.
EDIT: Link to source. (http://undeadly.org/deadly-src.tar.gz)
Re:hmmm…
so the best thing is to store the data in mysql database?
but wouldn't that put the load on the server if everytime someone wants to read my entry, they have to make a request to the database and retrieve data, etc?
but if that means less stress compared to modifying text files, maybe that's an option…
well, i'll give it a start somehow.
thanks -)
Re:php with a mysql backend is probably going to be the easiest for you.
using a text file as your database will flat out be a pain in the butt, guaranteed. It can be done, but not well. Plus, as your blog grows, the web server will spend more and more time and cpu processing power just opening and parsing your text file.
Re:php script would be easiest.
the blogger i wrote for my site is a php that writes to 2 text files. 1 text file for the main page and the 2nd text file to store a stripped down version of the posts (replaces images with just links..etc.) for my archived page. i chose flat-file as a personal preference, but sql would've been easier.
-Case
Re:I would store the entries to a database or a text file. The main page will then query the database or include the text file to display the blog entries.
Related posts
Tags: blogger, spare time