It’s been a while since I’ve managed to do a release of Rails-CMDB. This is mainly because I got stuck working parts of the test suite and I’ve been doing things that have kept me away from a computer.
However over the last few days I’ve managed to get an import integration story working, which seems to be working. I’ve also taken the chance to migrate to Ruby on Rails 1.2.5, but there are some DEPRECATION warnings still to dealt with.
Behind the cut is the changelog. Continue reading
Following the comment from Graeme Mathieson on my last post on Rails-CMDB about the the Rails way for naming of columns within Models. I’m planning on doing the following column rename for the next release of Rails-CMDB:
rename_column :assets, :delivery_date, :delivered_on
rename_column :assets, :removal_date, :removed_on
rename_column :locations, :start_date, :started_on
rename_column :locations, :end_date, :ended_on
rename_column :purchase_orders, :order_date, :ordered_on
rename_column :vendors, :last_order_date, :stopped_ordering_on
So the question for the Rails coders out there – does this seem correct ? There’s also a single table who’s primary field is not called name, so I guess to do it in the Rails way it should be changed as well.
I’ve also created about 90 unit test stubs and now just comes the hard part of coding the tests 😉
Well it’s been a month since the first release of Rails-CMDB and it’s now time for another release. This is the rather large list of changes:
- Added some unit tests for PurchaseOrder.
- Added Export to CSV.
- Added Import from CSV.
- An asset can have many hardware items.
- The Asset name does not need to be a number.
- Catch trying to show a device that does not exist.
- Add order_date column to PurchaseOrder Model.
- Rename order_date column in Asset to delivery_date.
- Correct typo’s in CreateNetworks which prevented loading of the schema.
- Rename the database’s used to match the application name.
- Added some simple doc’s on getting the system up and running.
- Change to using host: 127.0.0.1 in database.yml instead of sockets.
The source code can be found here. Not sure what is going to be in the next version, however I expect it’ll not be ready for release until mid to late September.
This is the first ever release (0.1) of Rails-CMDB, the Ruby on Rails project I’ve been working on since the end of last month. It’s best described as little rough round the edges and the under laying DB schema may change with no upgrade path. However it’s possible to enter (and change) all of information via the interface and also view all details for a device on a single page.
The source code can be found here on my main web site, I’ll try to do a second release within the next few weeks when I get an idea of what’s needed next (I’m currently thinking it’ll need to be import or export via an Excel speed sheet or a CSV file).
Update: It’s been pointed out the me that I did not say what this software is, you can find a lot more details ITIL defines as a configuration management database (cmdb) in this post from last month.
Last night I went to ScotRUG mainly to meet mathie, but also to find out what all the fuss is about and so far I like what I’ve heard. It being like Python (without the whitespace) is a good thing as Python has been my programming language of choice for many years.
While thinking about starting this blog I was looking at PHP, trying to get my head round it as a programing language (which is a title I don’t think it really deserves). From the few hours that I spent tying to code a simple application, the vile and loathing for PHP has come back in force.
So today I’m going to try and find my first Ruby on Rails book as I generally want to learn more about Agile Development methods and Rudy on Rails. There’s that itch forming to write something while learning Ruby on Rails, which should be interesting as I’ve never written a web application before. Also my new book on CSS can be put to good use.
Update: I’ve now got 2 Ruby on Rails books, read the first few chapters of Agile Web Development with Rails and so far it sounds like a very nice framework, next is getting an environment set up and the staple hello world!