I envision my blog becoming a sort of centralized information-store for me, although I've not quite figured out how I'm going to handle sensitive information, such as addresses, phone numbers, etc.  There are three approaches I've thought about: (1) use a PHP password-protection scheme to protect certain pages, (2) encrypt the data (but that sort of defeats ease of access), and (3) obfuscate the data in some simple way that I can mentally decode it on the fly -- I dunno, transpose digits in phone numbers or shift them all by 1, for instance.  I'm posting this here for feedback, because the community always proves fruitful when you're wanting to do something without reinventing the wheel.

I suppose the obvious answer is: memorize the most critical data, or keep it on my person in a passworded PIM device.  I'm open to people shooting down this idea of putting semi-sensitive stuff on my blog in a semi-protected format.  Obviously, I'm not going to put any seriously sensitive stuff up, like financial info (credit card # anyone?)

Thanks wraith!  That does look like what I'm needing.  I'm only wanting a select few pages to be passworded.  Can I set up PMWiki in a subdirectory and just password-protect access to web-pages in that directory only?

I'll read more about PMWiki tonight.  Right now, I've got to leave for work.

Thanks for the info!

Thanks wraith!  That does look like what I'm needing.  I'm only wanting a select few pages to be passworded.  Can I set up PMWiki in a subdirectory and just password-protect access to web-pages in that directory only?

I'll read more about PMWiki tonight.  Right now, I've got to leave for work.

Thanks for the info!

You'll want to look at the topic on Passwords.  What I'd do is set up a WikiGroup, then password protect that.

                                       [attach]

Redmine is not terribly hard to install, provided you already have Ruby/Rails setup on your box. But it's not as nice and easy as your typical PHP script. I dearly love Redmine, but I do wish they'd focus on ease of maintenance/upgrade, and add a few additional niceties. One frustrating thing I came across recently for example is that the version of RoR that Cpanel installs is not compatible with Redmine currently.

It's like they came up with a 90% awesome system and now, despite development continuing at a good pace, little of interest (to me) is being added. Plugins continue to offer some interest though. There was even a time I considered basing an entire public personal website off of it! Mouser no doubt remembers that.

- Oshyan

Quote from: JavaJones on August 10, 2011, 08:47 PM

Redmine is not terribly hard to install, provided you already have Ruby/Rails setup on your box.

...but a Ruby setup is a big bowl of AAAAAAAAAARGH to setup. At least it's been no joy for me on gentoo and debian systems. Pickyness about versions, weird behavior, RoR connections to mysql timing out after N hours with no apparent fix, sluggish performance, et cetera.

If you manage to get it going, do yourself a favor - never upgrade anything. Ruby is famous for breaking backwards compatibility, even for relatively minor updates, and the various Gem authors have taken that habit to heart.

Boy I'm glad it's not just me!  

I've run into similar to what f0dder is describing at one time or another when evaluating RoR/Redmine. Last time out we wound up using a  prebuilt stack from TurnkeyLinux to get it to work reliably.

Sadly, I have to agree with everyone bemoaning the difficulty of setting up and *maintaining* RoR. My current solution has been to just use a RoR-oriented web host (which can also do PHP, etc. it's just that they take care of the harder part of doing RoR). So far I've had no major problems running Redmine and other RoR projects. But this is not an appropriate solution for many. RoR really needs to mature as a platform if it's going to continue to gain popularity, particularly outside the coder/web hacker scene.

- Oshyan