EnkiBlog Google Group

Continuous Integration

2008-10-23T05:42:10Z

[link]
Just a bit of extra transparency
At least for the time being this is a vote in favour of keeping stuff in
vendor/
I'll chat with the Relevance guys and see what they think about config.gems
Xavier

Re: Vendoring

2008-10-22T21:45:40Z

I vote unvendor the gems. I haven't had much experience with vendor'd
gems, but I know there are still issues and I agree config.gem does
the job just fine.

Vendoring

2008-10-09T15:45:07Z

Given config.gem now works pretty well, and the rake tasks to install
those gems, is there any reason why we shouldn't unvendor pretty much
everything?
Advantages:
- Less code!
- Smaller clone
- Easier to keep everything up to date
Disadvantages:
- Slightly slower to get started?

Changes! Rails 2.1, no more YAML, collapsed migrations

2008-09-19T02:44:33Z

Hello,
- YAML API support has been removed since no one was using it
- Rails has been upgraded from 2.0.2(?) to 2.1, with the necessary rspec
upgrade (now we get timestamp migrations yay)
- I collapsed all the migrations to 9. No new migrations have been added
for ages, so this shouldn't affect many people, but if you do have a

Re: about enki

2008-09-03T21:38:05Z

hmm, looks like request.raw_post is nil. I've just committed a fix (add
.to_s) otherwise just change line 17 to:
unless session[:logged_in]
You don't need the extra check unless you're using the API, which I hope
you're not because I'm ripping it out soon :)
Xav
PS. CCed to list

Re: error at render :yaml

2008-08-28T01:37:16Z

Is anyone using this YAML stuff?
I was going to be but never got around to finishing my blog-from-VIM thing.
I'm thinking it best to pull it out for now (which will help upgrade
enki to rails 2.1), then do the API properly later - AtomPub is likely
the best option.
Thoughts?

Re: error at render :yaml

2008-08-21T07:04:59Z

hmm, there is one for json and xml, but I can't see yaml on rails-doc.org
I won't have a chance to investigate for a few days

error at render :yaml

2008-08-19T17:41:59Z

In app/controllers/admin/posts_co ntroller.rb

I think render method has not :yaml.
Is this code correct ?

format.yaml {
render :yaml => Post.find(:all,
:select => 'id, title',
:order => 'created_at DESC'
).to_yaml
}

Re: Can't login to admin

2008-07-18T08:33:56Z

Thanks for the reply. I tried your suggestion. No syntax errors. Just
the expected output.

Re: Can't login to admin

2008-07-15T03:16:57Z

hmm, interesting one.
This error is sometimes caused by syntax errors.
Try running:
ruby app/controllers/admin/dashboar d_controller.rb
Expected output is:
app/controllers/admin/dashboar d_controller.rb:1: uninitialized
constant Admin (NameError)
(and not a syntax error)
- Xavier

Can't login to admin

2008-07-10T07:22:27Z

OK, I figured out how to get Enki to run via fastcgi, but now I'm
crashing out on this error after logging in through OpenID:

A LoadError occurred in application#show:

Expected /home/disorde/enki/app/control lers/admin/
dashboard_controller.rb to define Admin::DashboardController
[RAILS_ROOT]/vendor/rails/acti vesupport/lib/active_support/

Re: Enki and Apache+fastcgi?

2008-05-14T07:15:47Z

AFAIK there's nothing specific to enki that requires nginx/mongrel
But I haven't used apache+fastcgi for ages
And mod_rails is out now and seems to be the better option
Though I guess you're on a shared host and don't have a choice?
Can you get a blank rails app running?
Any debugging info you can share to help us help you?

Enki and Apache+fastcgi?

2008-05-14T07:08:19Z

Just curious to know if using Apache+fastcgi is feasible, and if so,
what changes I'd have to make to the base code? I can't get it to run
out of the box, but I may just being something extremely wrong.

Re: Cosmetic README

2008-04-15T04:16:14Z

README.textile is ugly, but hopefully that can change soon:

[link]

On Apr 15, 10:54 am, "Chris Lloyd" <christopher.ll...@gmail.com>
wrote:

[PATCH] Cosmetic README

2008-04-15T00:54:52Z

Hi,
Just a quick patch, made the README nicely formatted on GitHub.
Cheers,
Chris