Radiant Development Environment Question

[Eric Sipple]

I'm trying to get the current/edge Radiant working so I can begin contributing to the effort, but I'm getting an error when using the "radiant <project>" command. The error is the following: 

/Users/saalon/Development/radiant/bin/radiant:7:in `require': cannot load such file -- ruby_version_check (LoadError)

Any idea what might be the cause of this? It looks like all of the radiant gem dependencies are properly installed (including Railties, which is where I think ruby_version_check comes from).

I hunted around the wiki to see if there's any documentation on getting a developer environment set up and couldn't find it, but if I missed something that addresses this, feel free to point me in that direction.

Thanks!

Eric

[Jim Gay]

First of all: <3 <3 <3
Thanks for helping, Eric.

Secondly, you should work through pulling the code from github and
then bundle install, and run "rake".
Don't try to generate a new radiant project, just try to get the specs
running from the code.

The plan is to move radiant to a proper engine, so the "radiant
project_name" command *might* just go away.
Currently you make a radiant project, in the future we want to make a
rails project and add radiant to it.

> --
> --
> Radiant CMS Dev Mailing List
> Post: radiant...@googlegroups.com
> Unsubscribe: radiantcms-de...@googlegroups.com
> Group Site: http://groups.google.com/group/radiantcms-dev/
> ---
> You received this message because you are subscribed to the Google Groups
> "Radiant CMS: Dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to radiantcms-de...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>



--
Write intention revealing code #=> http://www.clean-ruby.com

Jim Gay
Saturn Flyer LLC
571-403-0338

[Eric Sipple]

Thank you for the help, Jim!

I've got this all running in an rvm environment with ruby 1.9.3-p374, so I hope the environment is correct for the master branch. I've forked the repo, cloned it and bundle-installed all of the gems, but when I try to run rake (or rake spec), I'm getting the following error:

/Users/saalon/.rvm/gems/ruby-1.9.3-p374@radiant-dev/gems/activesupport-3.2.11/lib/active_support/dependencies.rb:317:in `rescue in depend_on': No such file to load -- radiant/config/definition (LoadError)

Is there any setup I need to do beyond bundle install that's causing this failure?

Eric

[Eric Sipple]

Also, I'm taking notes on any steps I need to take to get a development environment for Radiant working, so once everything is set I can get it to you for the wiki. Best way I can make good on any help given as I get to know the process.

[Benny Degezelle]

Nope.. I messed that up apparently.

Odd because 'I was sure the specs ran fine after that change' (™)
I just pushed a commit that stops requiring the config definition, the specs should really run now.

Thanks from me too for chiming in, any help or feedback is very welcome!

Benny

Op donderdag 1 augustus 2013 16:17:29 UTC+2 schreef Eric Sipple:

[Eric Sipple]

Benny,

Thank you! Looks like I'm set up and ready to go.

So, my big question from here is: What's the best way for me to go about helping? Is the plan to get failing specs passing, or something else? Let me know how I can be of best assistance. As my company uses Radiant and would love to get onto rails 3, they've agreed to let me put some on the clock time into working on Radiant, so between builds of our site I'll be taking on whatever I can. Just want to make sure I'm putting the time in where it's most useful.

Thanks again!

Eric

[Benny Degezelle]

The 2 main issues I see at the moment are

1/ dataset: still fails (undefined method 'users' etc.), which makes for the biggest part of failing specs I believe.

It seems dataset is not used much (if at all) on other rails projects besides radiant, so we will have to patch this ourselves.

Jim already pushed some changes (see github.com/radiant/dataset), but I still can't get it to work. Part of me would like to drop dataset altogether and use something some other spec fixtures plugin like factory_girl or whatnot. Annoyance with this is that many extensions also depend on dataset (and esp. the datasets that come with radiant) for their specs.

2/ the extension mechanism fails to detect extensions at the moment. Whether they are in the Gemfile or in vendor/extensions (a functionality I'd like to keep) doesn't make a difference.

Both have been discussed before on this list, but without a clear conclusion, other than that we would like to make it as easy as possible to update old extensions to 2.0 compatible ones. Extensions should be railties or engines just like Radiant itself, AFAICT we cannot get there ánd be 100% backwards compatible with older extensions. Actually I think that's not such a bad thing, as we could then ask developers to flag extensions as 2.0-ready in the extension registry (ext.radiantcms.org) when they are being updated..

Other than that I think most of the syntax updates etc. for rails 3 are done.

Furthermore, at least the authentication system should be pulled from core and put into an extension, same goes for layouts. 

Jim? your thoughts?

Op vrijdag 2 augustus 2013 17:46:22 UTC+2 schreef Eric Sipple:

[Jim Gay]

So sorry for the delayed reply. I've been finishing up a project and
have neglected this list for a bit.

My current goal is to get Radiant tests running on Rails 3 (or
preferably 4 now).

Currently we use dataset which is a fantastic project but it hooks
into rspec and cucumber in places that I don't fully understand. I'm
currently going to focus on fixing that since rewriting all of the
specs to use a new library isn't terribly attractive to me.

I encourage activity on this list and on the github issues for any
part of this.
And yes, I'd like to pull out authentication and the layouts from the
core into extensions so that you can bring your own.

As far as backward compatibility goes, I'd be happy to contribute to
projects that need to be upgraded. It's likely to be a straightforward
process of just swapping things out, but we don't know that yet until
we get the specs running.

Thanks for the newfound activity! I'll be working on it with you.

-Jim

[Jan Hoffmann]

Hey Eric,

Did you post your guide somewhere? I also would like to contribute and think I will face the same issues you had.

Thanks

Jan