DIVID Technology Riffraff & Whatnot

by Kevin Bassham, Web Interface Developer

Scrum is no silver bullet, but it works

Danube posted this on their blog, it’s got a bit of insight to clarify how scrum works for planning software projects.

http://blogs.danube.com/scrum-is-not-something-“it-does”

Feedburner is Back

Feedburner is now (again) handling our subscriptions.

Ruby Article Trackback

Check out this quick 10 Reasons to Learn Ruby article on h3rald.com. Might be good for those who aren’t sold on the whole idea of why everyone seems to love this language.

Webkit for Linux

If you like the webkit in google chrome, you might like midori on linux, it’s webkit, 100% acid3 (web standards compliant), and very slim. I fount it installed in Intrepid Ibex alongside Firefox.

Stand for Open

200808231811.jpg

Software with restrictive licensing is released to protect the Intellectual property of the organization who nurtured it out into the wild, and wouldn’t be competitive without that protection. I for one am a pragmatist, so this doesn’t give me a false sense of entitlement. I don’t want to rebel against commercial software, because some of it is great stuff. I do have a soft spot for purity as open architecture, and am a proponent of progressing open source.

Although there are countless advantages to using restricted software, let’s support our developer community first. Drive change in trend to further FSF community causes whenever practical. Advocate the use of open source projects in your own family of colleagues when the alternative shows no significant advantages.

This can be done in small amounts by leaning to the community for daily software choices in business and personal endeavors. When you rebuild a PC, mention Linux even if you don’t install it. When you build a new website, try an open framework. If you buy hardware, support the vendors that support us as open source developers. And make a concerted effort to contribute something back instead of only using open technology! Then it goes full circle.

Reasonable Success with Radiant CMS on Hostingrails

Radiant Setup Log

using gem of Radiant, version 0.6.4
(note: could also use SVN export/checkout instead, but haven’t had time to experiment with this)
gem install –include-dependencies radiant

radiant –database mysql . (inside ~/app)

*bugfix – if you need to to freeze:radiant (not on shared hosting), fix svn path in GEM_HOME/gems/radiant-0.6.4/lib/tasks/framework.rake
to find GEM_HOME run this:
gem environment | grep “INSTALLATION DIRECTORY”
correct this path:
“http://svn.radiantcms.org/radiant/”

*bugfix – add this to boot.rb:
require ‘rubygems/gem_runner’

freeze your application
not on shared hosting:
rake radiant:freeze:edge
ok for shared hosting:
rake radiant:freeze:gems

*bugfix – edit config/environment.rb:
add this for hostingrails server:
require ‘rubygems’
require ‘radiant’
uncomment
RAILS[ENV] ||= ‘production’
make load shards first:
config.extensions = [ :shards, :all ]

*bugfix – edit database.yml:
add your db info
add this to production
socket: /tmp/mysql.sock

rake production db:bootstrap
setup users as you wish

edit public/.htaccess
uncomment this:
RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
comment out this:
AddHandler fastcgi-script .fcgi

chmod 755 public/dispatch.fcgi

execute the server process:
./public/dispatch.fcgi

to restart server:
killall -9 dispatch.fcgi

to see immediate changes during development, change /config/environments/environment.rb to disallow caching

Add in any optional extensions to be migrated one at a time, and any stylesheets, images, etc.

rake db:migrate:extensions (for each extension)

Admin title can be changed in ‘config’ table of db

,