Mohit, Bjørn,

Thank you both for your help.

Bjørn Michelsen wrote:

[snip]
You need the OpenSSL interface for Ruby. To install it, open up a
terminal and do:

sudo aptitude install libopenssl-ruby1.8

--
Sincerely,
Bjorn Michelsen


It didn't resolve the problem, strangely enough:

===
[EMAIL PROTECTED]:~/Ruby-work/radiant-test$ sudo aptitude install
libopenssl-ruby1.8
[sudo] password for tomc:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Initializing package states... Done
Writing extended state information... Done
Building tag database... Done
The following packages are unused and will be REMOVED:
  dcraw liboil0.3 libsoup2.4-1
The following NEW packages will be installed:
  libopenssl-ruby1.8
0 packages upgraded, 1 newly installed, 3 to remove and 0 not upgraded.
Need to get 0B/108kB of archives. After unpacking 803kB will be freed.
Do you want to continue? [Y/n/?] y
Writing extended state information... Done
(Reading database ... 102290 files and directories currently installed.)
Removing dcraw ...
Removing liboil0.3 ...
Removing libsoup2.4-1 ...
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Selecting previously deselected package libopenssl-ruby1.8.
(Reading database ... 102254 files and directories currently installed.)
Unpacking libopenssl-ruby1.8 (from
.../libopenssl-ruby1.8_1.8.6.111-2ubuntu1.1_i386.deb) ...
Setting up libopenssl-ruby1.8 (1.8.6.111-2ubuntu1.1) ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Writing extended state information... Done
Building tag database... Done
[EMAIL PROTECTED]:~/Ruby-work/radiant-test$ rake production db:bootstrap
(in /home/tomc/Ruby-work/radiant-test)
rake aborted!
no such file to load -- openssl

(See full trace by running task with --trace)
[EMAIL PROTECTED]:~/Ruby-work/radiant-test$
===

Mohit Sindhwani wrote:

[snip]
Just to confirm:
1. You've installed Radiant
2. You've done something like
 > radiant test-radiant
 > cd test-radiant
 > ..... set up the database in config/database.yml ?

Yes to all but the last.

Project creation was accomplished with this:
$radiant --database=sqlite3 radiant-test

My current config/database.yml file is this:

===
# SQLite version 3.x
#   gem install sqlite3-ruby
development:
  adapter: sqlite3
  database: db/development.sqlite3.db

# Warning: The database defined as 'test' will be erased and
# re-generated from your development database when you run 'rake'.
# Do not set this db to the same as development or production.
test:
  adapter: sqlite3
  database: db/test.sqlite3.db

production:
  adapter: sqlite3
  database: db/production.sqlite3.db
===

This seems to be exactly what is listed at
http://wiki.radiantcms.org/Installation ("Configure Radiant for Your
Database")

In that section, I read "If you are using MySQL or PostgreSQL you will
need to create a database for each environment that you wish to run
Radiant under. If you are using Sqlite the databases will be created by
Radiant when they are needed."

So, my initial concern that I needed to create a database (or several)
seemed to be unwarranted. I set it aside. Was that an error?

At http://wiki.radiantcms.org/Database_Configuration I see nothing
indicating I need to do anything but run the bootstrap rake task which
in fact is the very next task listed at
http://wiki.radiantcms.org/Installation - so I did. And...that brings me
to my present problem!


What version of Rails are you using?
Which version of Radiant?

From a fresh "gem list -l":

uh...uh...hmm. Rails? Needs Rails, does it?  Wellllllll. I seem not to
have that on board. :)

OK, if I were a Radiant God, I would see that all those things Radiant
needs would get installed, with Radiant, if they were not on board at
the time of installation. But...if I were such a being, I'd probably
also know why this isn't especially a good idea, as must be the case,
since that's not what happened. But...I will confess that I did think
that that was what would happen. I was wrong. Ignorance takes us into
many dark holes.

I installed Rake...but then...I got the same result as before:

===
$ rake production db:bootstrap
(in /home/tomc/Ruby-work/radiant-test)
rake aborted!
no such file to load -- openssl

(See full trace by running task with --trace)
$
===

In 3-4 tries (have lost count) this has been the precise result I've
gotten each time. Curious.

So...my environment:

OS: Kuibuntu Linux 8.04.1 "Hardy"
Ruby: 1.8.6
Rubygems: 1.2.0
Rails: 2.1.0
Radiant: 0.6.9

I hope you have some more ideas (and am sure you do). I'd be most
interested to hear it.

t.

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Tom Cloyd, MS MA, LMHC - Private practice Psychotherapist
Bellingham, Washington, U.S.A: (360) 920-1226
<< [EMAIL PROTECTED] >> (email)
<< TomCloyd.com >> (website & psychotherapy weblog)
<< sleightmind.wordpress.com >> (mental health issues weblog)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

_______________________________________________
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Reply via email to