Topics

User Functions

Events

There are no upcoming events

What's New

Stories

No new stories

Comments last 2 weeks


Trackbacks last 2 weeks

No new trackback comments

Links last 2 weeks

No recent new links

NEW FILES last 14 days

No new files

Welcome to Geeklog Thursday, June 20 2013 @ 07:13 AM EDT

> >

Installation Documentation

Geeklog
  • Monday, August 05 2002 @ 10:39 AM EDT
  • Contributed by:
  • Views:
    3,461
I think this issue needs a little clarification...
I attempted an upgrade from GL v1.3.5 to v1.3.5sr2.
The installation doc gives fairly explicit instructions, but has no mention of upgrading the DB (or not upgrading) from this recent version.
So I checked on IRC, and nobody was absolutely positive there.
The installation script had no choice for v1.3.5, so I picked the closest v1.3.4
That didn't work.
So I started back up from my backups.
But my point is, maybe this should be more clearly defined in the install docs.
If you guys need someone to "dummy-proof" your install docs, I'd be glad to help. While the existing docs do the job, I think they could be dumbed down a bit for the average user...
All in all though, I'm continually impressed with the whole GL community and everyone's willingness to provide support and new software.

The following comments are owned by whomever posted them. This site is not responsible for what they say.

  • Installation Documentation
  • Authored by:Dirk on Monday, August 05 2002 @ 11:42 AM EDT
Obviously I wasn\'t around when you asked that on IRC ;-)

So just to make this clear: There is no database upgrade needed when going from 1.3.5 to 1.3.5sr2.

We concentrated on getting the installation instructions right for 1.3.5sr2 (mainly because the old instructions where not detailed enough and sometimes we were just swamped with request for help). I guess the part about upgrading didn\'t receive too much attention then ...

Any suggestions on how to improve the documentation are welcome (and actual portions of text would be even more welcome). We\'ll try and further improve the documentation for the next version. For example, it will for sure include instructions on where to find the admin password, since that is currently the most-asked question on IRC ...

bye, Dirk
  • Installation Documentation
  • Authored by:T1Pimp on Wednesday, August 28 2002 @ 02:46 PM EDT
If you need someone to dummy proof install documentation on the Windows side of things I\'d be happy to help. I found installing GL kind of a pain because most documentation was written with a *nix user in mind. There were a few things that I only figured out after trial and error like the fact that I had to point the IIS root to the public_html directory. Ya ya... I know it\'s PAINFULLY obvious to me now, but it didn\'t explicitly say so in the docs. Since I am completly new to PHP and such I had no idea what I was doing wrong when I tried to initially set it up.
  • Installation Documentation
  • Authored by:Dirk on Thursday, August 29 2002 @ 01:07 PM EDT
Do your complaints apply to the installation instructions for Geeklog 1.3.6rc1 as well? Then please feel free to send them in.

I agree that the instructions are a bit unix centric but then again this is the most used platform out there ... Users running Apache on Windows didn\'t seem to have too many problems with the instructions either. So I guess we need to make some improvements for IIS users?

bye, Dirk
  • Installation Documentation
  • Authored by:Jason on Tuesday, September 03 2002 @ 06:27 PM EDT
Just a quick note, I\'m working on geting 1.3.6 to run on IIS and MSSQL. :) I\'m about 90% the way there. I\'ll make my notes available when done. So far the only hage changes are to the DB schema and the addition of the mssql module.

-Jason

Post a Comment

Your Name
Create Account
Allowed HTML Tags:
 

Security code
This question is for testing whether you are a human visitor and to prevent automated spam submissions.

What code is in the image?
Enter the bolded text, case sensitive!
Important Stuff
  • Please try to keep posts on topic.
  • Try to reply to other people comments instead of starting new threads.
  • Read other people's messages before posting your own to avoid simply duplicating what has already been said.
  • Use a clear subject that describes what your message is about.
  • Your email address will NOT be made public.