Re: [Radiant] Is anybody using Radiant on Dreamhost?

[Paul Noden]

Up until recently I was using radiant on DreamHost for years, It was only
possible using a virtual private server with extra resources assigned. Love
the host but not sure I would personally go there again with radiant. I
only run a very basic and non critical RoR app on DreamHost shared hosting
plan.
On 31 Aug 2015 14:03, "Anton Aylward"  wrote:

> Dreamhost have very limited support for Ruby  but otherwise an
> excellent service plan.
> They seem to be more geared toward PHP.
>
> Is anyone here using Radiant on Dreamhost?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Radiant CMS" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to radiantcms+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Radiant CMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to radiantcms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Radiant] Passenger 3 Rack problem

[Paul Noden]

On Sep 30, 2011 8:25 AM, William Ross w...@spanner.org wrote:
 I haven't noticed any issues with nginx and Passenger 3 either locally or
in production. Has anything else changed?

Nothing on the application side just a straight swap to nginx and passenger
3 and then it can't find rake/cache.

Paul

Re: [Radiant] dreamhost broke my radiant install

[Paul Noden]

On Sep 11, 2011 7:55 PM, WizarDave Akins wizard...@gmail.com wrote:
 Anyone else on dreamhost using radiant?
 If so, is your site working?

Working fine, you're using a vps? Frozen radiant and your gems?

Paul

Re: [Radiant] Exclude extensions with :all present

[Paul Noden]

On 25 July 2011 09:32, Shanison lxsh...@gmail.com wrote:
 So is there a workaround for this for Radiant 0.9.1? It would be very
 troublesome if I need to specify every single extensions to load.

0.91 doesn't have the benefit of the new feature
config.ignore_extensions however you can probably patch this in, am
uncertain if anyone else has done this already. You can find the
commit at 
https://github.com/radiant/radiant/commit/6f66516f2346e2739d93b5065a0ebbf2cee5d318

So you are left with a coin toss between patching this in and
specifying your extensions, would imagine the latter is probably
easier when put into context with the alternative?

Paul

Re: [Radiant] Error upgrading from 0.9.1 to bleeding edge

[Paul Noden]

Hi Jeffrey,

On 1 July 2011 00:36, jsman jeffrey.s...@gmail.com wrote:

 Today I tried to follow the instructions on
 http://radiantcms.org/download/
 to upgrade to the bleeding edge (1.0.0.rc2) in an existing 0.9.1
 project.

 On the rake db:migrate step I got the following output:

 $ rake --trace db:migrate
 (in /home/user/site)
 ** Invoke db:migrate (first_time)
 ** Invoke environment (first_time)
 ** Execute environment
 rake aborted!
 no such file to load -- rack/cache
 /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:29:in
 `gem_original_require'

 ...

 Is this method no longer supported or are extra steps needed?


In case you haven't hit upon the solution, you should try rake gems:install
which should install all the required gems, such as an updated version of
rack-cache.

Hope that helps,

Paul Noden

Re: [Radiant] How can I have a foolproof backup?

[Paul Noden]

Would it be beneficial to have a dreamhost-radiant best practices
discussion? Do you use virtual or private servers? What are your findings in
terms of resourcing/load etc.

I've found the current default passenger configuration is much more radiant
friendly than the radiant wiki suggests (one server's settings may not apply
more generally however), the only modification I had to make to my
environment.rb - once all the gems were installed (a user gems directory was
enabled for me by default) - was adding config.gem rack, :version =
'1.1.0' to the top of the config block since I currently have radiant::
cache disabled... Looking into fragment cache.

Looking forward to hearing your experiences, perhaps one day radiant could
become a dreamhost one-click or scripted install (I've found that memory
usage currently runs a little high for the limitations on a standard plan),
but there is a healthy niche for it since developer/design teams quite like
dreamhost...

Paul

Re: [Radiant] Page Reordering

[Paul Noden]

On 20 June 2011 15:40, Bob Sleys bsl...@gmail.com wrote:

 Does radiant-reorder-extension work with radiant 1.0.0.rc? Reordering the
 pages to make it easy to automatically create properly sorted menus


Only problem is menus? Have you thought about r:navigation/ tags in a
layout/snippet which will allow you to configure the menu order?

Paul

Re: [Radiant] Lost some Radiant rake tasks in 1.0.0 RC2

[Paul Noden]

Hi Jim / Wes,

 On 6/1/11 9:18 PM, Jim Gay wrote:
 Paul, I'm not sure I understand, but I missed your offer for
 debugging: I accept!

Jim - Am very happy to help however I can - I want to get involved in
Radiant, probably have most to contribute to extension development but happy
to pitch in when I gain familiarity. Priority for me is shipping a project
on 1.0.0 (having trouble with the reader extensions, if I can get some help
off list to check my configurations before I go reporting a non-issue on
github I'd certainly appreciate it! I have need for a few days of a radiant
freelancer asap! )

On 2 June 2011 05:12, Wes Gamble we...@att.net wrote:
 Paul saw missing rake tasks when upgrading from 0.9.1 to 1.0.0 RC1.

Spot on. Rake tasks were missing such as radiant:update which made
completing the upgrade impossible to complete.

*Speculation: Wes - do you have a vendor/radiant? Tried removing this with
any change in results?*

A diff of the results of 'rake -T radiant' on my 0.91/1.0.0 RC1
semi-migrated project and the 1.0.0 RC1 gem (ignoring extensions - for
reference fckeditor and vapor were installed in the project) show the
project missing the following details:

DEPRECATION WARNING: Rake tasks in vendor/plugins/dataset/tasks are
deprecated. Use lib/tasks instead. (called from
/Library/Ruby/Gems/1.8/gems/radiant-1.0.0.rc1/vendor/rails/railties/lib/tasks/rails.rb:10)
rake radiant:clobber_package  # Remove
package products

rake radiant:import:prototype:assets  # Import
images, javascripts, and styles from prototype
rake radiant:import:prototype:images  # Import
images from prototype
rake radiant:import:prototype:javascripts # Import
javascripts from prototype

rake radiant:package  # Build all
the packages
rake radiant:release  # Publish the
release files to RubyForge.
rake radiant:repackage# Force a
rebuild of the package files

This may provides more detail to Wes' bug report (the last three items
should appear after radiant:import:prototype:stylesheets)
*
*The lack of radiant:update in both task listings, which was necessary to
complete the migration, is what caused me to finally do a new project using
rc1 and reintroduce the extensions which I was able to migrate to RC2
successfully.*

Speculation: I assume that radiant:update should only be 'available' when in
scope of radiant projects as it's present in my RC2 project but not in the
RC2 gem. Any other tasks with similar 'scoped availabilities' will obviously
not show as missing... Could this be partly to blame, do the above tasks
have 'scoped availabilities' where the test for 'scoped within a radiant
project' is broken?*

Hope that helps rather than confuses the issue,

Paul

[Radiant] Re: Radiant 1.0.0rc1 no rakefile or gemfile

[Paul Noden]

On May 24, 1:06 pm, Tom Brooke tom.bro...@gmail.com wrote:
 I should post an issue - it was with a new instance with Ruby1.9.2 (rvm)
 using radiant -d mysql newapp then cd to newapp and couldnt do rake tasks. I
 looked in the directory and didnt see rakefile or gemfile - maybe I need to
 do a bundle install

I was having the same issue in doing an upgrade of Radiant 0.9.1 to
1.0.0.rc1 the first step after installing radiant failed with rake
unable to locate task radiant:update (also missing radiant:freeze..
e.t.c.)

Probably need to do some core updates to my mac development box as was
running it on ruby 1.8.7 (rails 2.3.5), welcome suggested milestones
for 1.0.0.rc1?

In regards to Jim's Question on May 24, 5:08 am:
 Are you looking for those files to appear in your radiant instance or
 are they not appearing in your gem directory?

Can see them in the gem directory, but not in the radiant instance. A
Rakefile would be necessary in the instance directory in order to be
able to run rake. I copied Rakefile and this didn't resolve the issue,
would be willing to debug/trial fixes with guidance as I can be
available for this all week.

Kind Regards,

Paul Noden