Forum: Radiant CMS Hello! What did I overlook? Newb.

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Mason Galindo (Guest)
on 2007-06-10 09:56
(Received via mailing list)
Hello everyone,

I'm very new to Ruby, Rails, and Radiant and recently attempted a
fresh install of Radiant 0.6.1 on a VPS I have running CentOS-4. I
didn't receive any error messages during any of the installations but
am unsure how to make the application run. I'm very eager to begin
learning and using Radiant and will attempt to provide you with as
much relevant information as possible. Excuse the length of the
following. It is an output from running the gem list command. The
following gems are installed. Am I missing anything? Everything
should be current.

Please note that this is my first time installing Ruby, Rails, Gems,
basically anything related to RoR or Radiant.

========================================================================
=======
*** LOCAL GEMS ***

actionmailer (1.3.3)
     Service layer for easy email delivery and testing.

actionpack (1.13.3)
     Web-flow and rendering framework putting the VC in MVC.

actionwebservice (1.2.3)
     Web service support for Action Pack.

activerecord (1.15.3)
     Implements the ActiveRecord pattern for ORM.

activesupport (1.4.2)
     Support and utility classes used by the Rails framework.

capistrano (1.4.1)
     Capistrano is a framework and utility for executing commands in
     parallel on multiple remote machines, via SSH. The primary goal is
     to simplify and automate the deployment of web applications.

cgi_multipart_eof_fix (2.1)
     Fix an exploitable bug in CGI multipart parsing which affects Ruby
     <= 1.8.5 when multipart boundary attribute contains a non-halting
     regular expression string.

daemons (1.0.6)
     A toolkit to create and control daemons in different ways

fastthread (1.0)
     Optimized replacement for thread.rb primitives

fcgi (0.8.7)
     FastCGI library for Ruby.

gem_plugin (0.2.2)
     A plugin system based only on rubygems that uses dependencies only

gettext (1.9.0)
     Ruby-GetText-Package is a libary and tools to localize messages.

mongrel (1.0.1)
     A small fast HTTP library and server that runs Rails, Camping,
Nitro
     and Iowa apps.

mongrel_cluster (0.2.1)
     Mongrel plugin that provides commands and Capistrano tasks for
     managing multiple Mongrel processes.

mysql (2.7)
     MySQL/Ruby provides the same functions for Ruby programs that the
     MySQL C API provides for C programs.

needle (1.3.0)
     Needle is a Dependency Injection/Inversion of Control container for
     Ruby. It supports both type-2 (setter) and type-3 (constructor)
     injection. It takes advantage of the dynamic nature of Ruby to
     provide a rich and flexible approach to injecting dependencies.

net-sftp (1.1.0)
     Net::SFTP is a pure-Ruby implementation of the SFTP client
protocol.

net-ssh (1.1.1)
     Net::SSH is a pure-Ruby implementation of the SSH2 client protocol.

radiant (0.6.1)
     A no-fluff content management system designed for small teams.

rails (1.2.3)
     Web-application framework with template engine, control-flow layer,
     and ORM.

rake (0.7.3)
     Ruby based make-like utility.

sources (0.0.1)
     This package provides download sources for remote gem installation

unicode (0.1)
     Unicode normalization library.
========================================================================
=======

After successfully installing Radiant, I ran the following command
script/server -e production from the root Radiant directory. I'm
assuming this starts Radiant on the server? This was the response:

=> Booting Mongrel (use 'script/server webrick' to force WEBrick)
=> Rails application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
** Starting Mongrel listening at 0.0.0.0:3000
** Starting Rails with production environment...
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready.  TERM => stop.  USR2 => restart.  INT => stop (no
restart).
** Rails signals registered.  HUP => reload (without restart).  It
might not work well.
** Mongrel available at 0.0.0.0:3000
** Use CTRL-C to stop.

So far so good, right?

I then attempted to access Radiant on the server via the URL that I
unpacked the Radiant application files to. I assumed that these files
had to be located into a web accessible directory so I placed them
in /home/user/public_html/cms. When I try to access this directory in
my web browser, I simply receive a default directory listing
displaying the contents of the directory. No Radiant login screen.

Also, because this is my first time installing RoR and a Rails
application, I also need to know how to set it up so Radiant starts
automatically so I don't have to initiate it manually. So, is the
reason I'm seeing a directory listing rather than a Radiant page
because Radiant isn't actually running on the server?

Thanks for reading. I apologize for lengthy message and hope I
provided a sufficient amount of information.

Best,
Mason
Mohit S. (Guest)
on 2007-06-10 10:19
(Received via mailing list)
Hi Mason,

Here's what you need to do to get it all working together:
1. Install as per the instructions on the website - you seem to already
have the gem installed
http://dev.radiantcms.org/radiant/wiki/Installation

2. Create an application using the 'radiant' command
Let's assume that you created the application in: /usr/local/radiant (or
something)

3. Edit database properties and create database in MySQL (or whichever
one you're using)

4. Run the instructions for bootstrapping the database

5. Then, start the server in the root directory of the application
[/usr/local/radiant]script/server -e production
This starts the server on port 3000.

Thereafter, the site should be up on http://localhost:3000/

Hope this helps.  Once you get past this hurdle and want to start to
look at creating pages based on an empty website, you can refer to the
'Hello World' article on my blog:
http://notepad.onghu.com/2007/5/26/hello-world-usi...

Mohit.

Mason Galindo wrote:
> should be current.
>
*** snip ***
Mason Galindo (Guest)
on 2007-06-10 10:43
(Received via mailing list)
Hi Mohit,

Thanks for your response. Perhaps I wasn't clear in my first message
but I've already completed all of the steps you outlined. Ruby is
installed, all gems are installed (I'm assuming anyway. I posted the
installed gems list so you could verify this), the radiant command
has been run: radiant --database mysql /home/tspadmin/cms and was
successful. The database properties have been edited. Database has
been bootstrapped. Command script/server -e production has been run
successfully. Now, I'm wondering how I access the admin login page.

Also, why would the site be accessible via localhost? I'm not
installing this on my personal computer but rather onto a web server.

Thanks,
Mason
Mohit S. (Guest)
on 2007-06-10 10:47
(Received via mailing list)
Mason Galindo wrote:
>
> Also, why would the site be accessible via localhost? I'm not
> installing this on my personal computer but rather onto a web server.
>
Hi Mason,

I wrote those out so that you could just double check.

As for localhost, my mistake - I had overlooked the point that you
mentioned it's on a VPS.  If everything's been run and is fine, the site
should be on http://your-vps-address:3000/  The reason for this is that
running script/server will start Mongrel to serve applications/ web
pages on port 3000.

Hope this helps.
Cheers
Mohit.
Mohit S. (Guest)
on 2007-06-10 11:07
(Received via mailing list)
Mason Galindo wrote:
> Mason
>

Mason,

Definitely, your radiant site is installed in a wrong directory.  It
should not be running from a publicly accessible directory (that way
someone can read your password, application, etc.)

I'm trying to see what else may be wrong.  You're sure that
script/server is running right now?

Perhaps, you can take a look at some of the other deployment guides at:
http://dev.radiantcms.org/radiant/wiki/HowTos

I think you may need help from someone else on this forum :-|
Cheers
Mohit.
Mason Galindo (Guest)
on 2007-06-10 11:16
(Received via mailing list)
Hi Mohit,

Thanks for pointing that out. Now I'm not sure what I should do. I've
renamed the 'cms' directory to make it temporarily inaccessible.
Maybe I should move it to a different location on the server? Where
would you recommend?

Now I'm stumped. Thanks for your help. If you're unsure of how to
proceed, I can wait for someone help to pop in and give me a hand.

Best,
Mason
Mohit S. (Guest)
on 2007-06-10 11:24
(Received via mailing list)
Mason Galindo wrote:
> Best,
> Mason
>

I think someone else should help you out.  On the other hand, take a
look at the guides for deploying Radiant to a any of the other hosts.
Perhaps, that would help you looking in the right direction.

Cheers
Mohit.
Mason Galindo (Guest)
on 2007-06-10 11:42
(Received via mailing list)
Mohit,

Thanks for your help. Nice meeting you. Enjoy the rest of your weekend!

Best,
Mason
This topic is locked and can not be replied to.