I am guessing it may be server-related then.
Yeah, I know what you mean. Windows; seconds (Under Instant Rails) - my
home Fedora server. All goes fine. Get onto DreamHost, try to do it
'vanilla', no luck. Try to follow all the sites out there; no luck. Part
of the problem is that the shebang
1. Did you install Radiant from source or use the gem?
Source
2. If you installed Radiant using the gem, did you use the --unpack
flag
with the radiant command?
No.
3. Would you mind if we dropped support for upgrading unpacked Radiant
applications (apps installed using the
On 1/15/07, John W. Long [EMAIL PROTECTED] wrote:
The pole:
1. Did you install Radiant from source or use the gem?
Source.
2. If you installed Radiant using the gem, did you use the --unpack flag
with the radiant command?
n/a
3. Would you mind if we dropped support for upgrading
John W. Long wrote:
1. Did you install Radiant from source or use the gem?
gem
2. If you installed Radiant using the gem, did you use the --unpack flag
with the radiant command?
no
3. Would you mind if we dropped support for upgrading unpacked Radiant
applications (apps installed
Quoting John W. Long [EMAIL PROTECTED]:
The pole:
1. Did you install Radiant from source or use the gem?
source
2. If you installed Radiant using the gem, did you use the --unpack flag
with the radiant command?
3. Would you mind if we dropped support for upgrading unpacked
1. Source
2.
3. I'm all for more updates.
BJ Clark
On 1/15/07, Todd McGrath [EMAIL PROTECTED] wrote:
Quoting John W. Long [EMAIL PROTECTED]:
The pole:
1. Did you install Radiant from source or use the gem?
source
2. If you installed Radiant using the gem, did you use the --unpack
John W. Long schrieb:
The pole:
1. Did you install Radiant from source or use the gem?
Gem.
2. If you installed Radiant using the gem, did you use the --unpack flag
with the radiant command?
No. Didn't even know that this flag exists :-/
3. Would you mind if we dropped support
Here is how did.
I start Radiant with mongrel server at port 3000 with prefix /radiant
mongrel_rails start -p 3001 --prefix=/radiant
I then config my apache at port 80 to route all request x.x.x.x/radiant
to the mongrel server.
extract from apache httpd.conf file
ProxyPass /radiant
1. Did you install Radiant from source or use the gem?
Gem
2. If you installed Radiant using the gem, did you use the --unpack flag
with the radiant command?
Yes -- Dreamhost's ruby server ATM on 2 servers (Confirmed now) does not
respond well to custom-installed gems. I had to
Ditto Giovanni.
On 1/15/07, Giovanni Intini [EMAIL PROTECTED] wrote:
Source / No / No
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:
Heh - I just realised that I had the folder sorted by subject rather
than date and was replying to an old post.
That's probably the approach I would've used in radiant 0.5.2, but the
extensions mechanism in mental has curbed just about every temptation I
have to touch the core.
-Original
Okay. Got the fix started. Here's the problem (Again) -- It nags that
bluecloth does not exist. I've dropped bluecloth.rb in RAILS_ROOT, no
avail. vendor/, nope. vendor/plugins/, nope again. GEM_PATH, nope again.
Can't access GEM_HOME. I've ran out of ideas. radiant and radius is
seen, as is
Andrew,
Are you running on production mode?
On 1/16/07, Andrew Klein [EMAIL PROTECTED] wrote:
Okay. Got the fix started. Here's the problem (Again) -- It nags that
bluecloth does not exist. I've dropped bluecloth.rb in RAILS_ROOT, no
avail. vendor/, nope. vendor/plugins/, nope again.
Andrew,
I *HIGHLY* suggest you install from source. Will make your life much easier.
On 1/15/07, Ruben D. Orduz [EMAIL PROTECTED] wrote:
Andrew,
Are you running on production mode?
On 1/16/07, Andrew Klein [EMAIL PROTECTED] wrote:
Okay. Got the fix started. Here's the problem (Again) --
Yes I am. Had to check myself to make sure. :)
This DreamHost thing is whoppin' my butt. I got radiant --unpack working
fine with a buncha small changes, but without --unpack, it refuses to
run. The error is as such:
/usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:18:in
`require__':
On 1/16/07, Andrew Klein [EMAIL PROTECTED] wrote:
Okay. Got the fix started. Here's the problem (Again) -- It nags that
bluecloth does not exist. I've dropped bluecloth.rb in RAILS_ROOT, no
avail. vendor/, nope. vendor/plugins/, nope again. GEM_PATH, nope again.
Can't access GEM_HOME. I've ran
On 1/16/07, Michael Jones [EMAIL PROTECTED] wrote:
Hi-
I just updated my mental branch, when I tried to start the server I got:
I guess is something related with Rails Edge and a broken revision?
To be on the save side check out revision #227. Please let me know if
this does or doesn't fix the error you got...
On 1/15/07, Michael Jones [EMAIL PROTECTED] wrote:
Hi-
I just updated my mental branch, when I tried to start the server I got:
= Booting WEBrick...
This could sound stupid: tried RAILS_ROOT/lib ?
They are added at the beginning of environment loading...
Tried that too. No avail.
Maybe adjusting your .htaccess file instead?
SetEnv GEM_HOME /usr/lib/ruby/gems/1.8
SetEnv GEM_PATH /usr/lib/ruby/gems/1.8:/home/bladedthoth/.gems
Maybe
To be on the save side check out revision #227. Please let me know if
this does or doesn't fix the error you got...
I ran: rake rails:freeze:edge REVISION=227 sucessfully.
And now get:
ruby script/server
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:18:in
`require__': no such
On 1/16/07, Michael Jones [EMAIL PROTECTED] wrote:
To be on the save side check out revision #227. Please let me know if
this does or doesn't fix the error you got...
I ran: rake rails:freeze:edge REVISION=227 sucessfully.
Oh no, you shouldn't do that!
You're sticking to revision 227 of
In the standard tags module there is alot of useful code however it's
not encapsulated in classes so I can't really build my custom tags
upon the existing tags.
I would really like access to children:each and just pass it an
options hash or something. Am I missing some code somewhere? Is there
22 matches
Mail list logo
