Jake Liddell wrote:
I'm new to Rails and Radiant, and as such I think many of my problems can be
put down to me not understanding fully the architecture of either Radiant or
Rails apps in general. But given there are probably plenty of other people
in my boat, I think I'll have a bash at
Hi all,
Sorry, this is a bit of a beginner question I'm afraid, but I'm following
the Textdrive instructions to install my 'application', and hitting some
problems.
I'm following the instructions on textdrive for installing a rails
application, as several people on this list suggested - I've
Given that they don't have the radiant gem installed, I'd suggest
simply checking out the SVN copy of radiant onto your local machine
and then upping that to your server.
On 8/23/06, Jake Liddell [EMAIL PROTECTED] wrote:
Hi all,
Sorry, this is a bit of a beginner question I'm afraid, but I'm
1) Get RadiantCMS from one of the released gems, or just like I did
instead, check it out from the subversion repository. I preferred the
subversion method.
2) Get TextDrive to assign you a port, make sure lighttpd is listening
at that port and you can access it manually via
Done :-)
http://dev.radiantcms.org:9007/radiant/wiki/HowToTextDrive
-- G.
On 8/23/06, John W. Long [EMAIL PROTECTED] wrote:
Guido Sohne wrote:
1) Get RadiantCMS from one of the released gems, or just like I did
instead, check it out from the subversion repository. I preferred the
Bug filed on Radiant Trac:
Radiant wiki content on Trac should instead be in Radiant
http://dev.radiantcms.org:9007/radiant/ticket/307
-- G.
On 8/23/06, Guido Sohne [EMAIL PROTECTED] wrote:
Done :-)
http://dev.radiantcms.org:9007/radiant/wiki/HowToTextDrive
-- G.
where Radiant is installed?
Cheers,
Jake.
-Original Message-
From: Guido Sohne [mailto:[EMAIL PROTECTED]
Sent: 23 August 2006 17:16
To: [EMAIL PROTECTED]; radiant@lists.radiantcms.org
Subject: Re: [Radiant] Problems setting up radiant on textdrive
1) Get RadiantCMS from one of the released
You can put it anywhere that you want. You will have to set the
server.document-root, and the binpath inside the fastcgi.server
section as per your needs. If you want this to be accessible from
secondary domains, the
$HTTP[host] =~ sohne\.net
line could be changed to something like
Guido Sohne wrote:
Radiant wiki content on Trac should instead be in Radiant
http://dev.radiantcms.org/radiant/ticket/307
Radiant is not a wiki. Anonymous users can't contribute content like
they can on the Trac wiki. Trac is the right tool for the job to manage
a development Web site.
On 8/23/06, John W. Long [EMAIL PROTECTED] wrote:
Guido Sohne wrote:
Radiant wiki content on Trac should instead be in Radiant
http://dev.radiantcms.org/radiant/ticket/307
Radiant is not a wiki. Anonymous users can't contribute content like
they can on the Trac wiki. Trac is the right tool
Guido Sohne wrote:
On 8/23/06, John W. Long [EMAIL PROTECTED] wrote:
Radiant is not a wiki. Anonymous users can't contribute content like
they can on the Trac wiki. Trac is the right tool for the job to manage
a development Web site.
That's probably another bug :-)
Or a feature. ;-)
If
On Aug 23, 2006, at 11:54 AM, Guido Sohne wrote:
How do blog comments fit into this?
Right now the RadiantCMS weblog seems to be relying on HaloScan
http://www.haloscan.com/ to handle comments. HaloScan works with
static sites perfectly well; Hobix users often use it instead of
Hobix's
Wait until I'm back from vacation, I'm working ona comments behavior. ;)
Sean Cribbs
seancribbs.com
On 8/23/06, Guido Sohne [EMAIL PROTECTED] wrote:
On 8/23/06, John W. Long [EMAIL PROTECTED] wrote: Guido Sohne wrote:
Radiant wiki content on Trac should instead be in Radiant
13 matches
Mail list logo
