I just read the article posted by Numerex titled “Updating Your FAST Application with the Latest Release (via patch file)”.

First, thanks for posting that - this is extremely helpful information.

Second, is there a published list of available patches anywhere (including their URLs)? I’d like to be able to see whats available and download them.

Finally, what’s the best way to find out what “version” or release number our application is currently on? Is that just the SVN build number (I’m assuming not, since we’re able to make our own modifications and check them in)?

Thanks in advance,
Scott L.

We just started introducing the patch format so there’s nothing else currently published. From here on out we’re planning on publishing them in the dev blog. You maybe be able to request this by sending an email to (JavaScript must be enabled to view this email address) but I’m not sure how difficult it will be to generate the patch file. Another option would be to download the project from GitHub and then do a diff on it with yours. Probably not the most elegant solution. Our plans are to publish new builds a few times a month and there should be a new one available next week.

Understood - thanks for the clarification.

I asked that question because I have seen a few posts on the forums here that refer to “upgrades” or “latest builds” or even features that have been developed but not actually released to all FAST clients.

For example, in this post: http://dev.numerex.com/forums/viewthread/118/

The poster describes that the latest build has updates to admin pages, etc. Are those updates something that Numerex developed? If so, were they pushed to all client SVN repositories automatically?

I’m just trying to avoid development efforts on our end that may overlap with something that Numerex is already done with or has in the works.

Thanks,
Scott

Scott,

Thanks for the note. Yes, the updates were developed by us as part of the core software. However, we do not automatically install updates to customer servers unless they are working with our professional services team. In the case that you’re doing your own development (as the poster you mentioned is) then you’ll have access to our latest build and patch files to do this yourself. Please let us know if you have any other questions.

Thanks,
Dennis

Thanks Dennis.

I guess the question we have is this: since we do our own development, can Numerex tell us what the differences are between the version we have and the “current version”?

Thanks,
Scott

I attempted to apply the 9502 patch using TortoiseSVN, but in every instance it gave me an error
that says ‘Patch seems outdated’ and that the lines of code do not match. I have only applied minor
customizations to our app.

We may be able to address both these issues with an article that talks through the process. Let me see if we can get something published tomorrow. Check the Dev Exchange and I’ll post an link here as well.

I have several questions about patch fast_tracking_9502.diff Numerex recently provided.

1) I managed to apply the patch to the most part of the project. But there were 5 files that have not been patched and patch command gave the following results on that files:

Four other files are db/schema.rb, config/database.yml, config/environments/test.rb, config/environments/development.rb. I had to do the modifications specified in .diff file manually to those files. But what do those errors mean?

2) After applying the patch and manual modifications I tried to call rake db:migrate. It failed with the following error:

I discovered the following lines were added to environment.db with the patch:

I tried to install those gems:

But error was still there. And rake db:migrate worked only after I commented those new lines in environment.db. What is the correct way to handle this issue?

3) After I started the server and tried to login to my local test account I got the following error in browser:

, where %PROJECT_PATH% is the path to the project on the local drive. device.rb:31 is the following:

But there is no GeofenceViolation model, it wasn’t added by the patch. So I added it manually, restarted server and it helped. So the question is - where is GeofenceViolation model?

You’re really getting into this! First off, thanks for your patience and detailed post information. Let me try to address your issues one by one:

1. Can you post your notifier.rb.rej file? You can either down it inline or as an attachment. I’d like to see what’s going on.

2. Generally to install gems you would run rake gems:install

3. Unfortunately this was added after the patch file was published. You did the right thing and just as a reference the contents of the file should look like:

class GeofenceViolation < ActiveRecord::Base
  belongs_to :device
  belongs_to :geofence
end

Sorry for any inconvenience.

Thanks for the reply!

1. Here is the notifier.rb.rej file contents (forum didn’t allowed me to attach the file and said: “The filetype you are attempting to upload is not allowed. Allowed Filetypes: image”):

2. Thanks for the tip, it helped! I’ve just started with Rails so don’t know much yet

3. Thanks.

I also applied the patch to our app. Unfortunately, I got lot of failures and rejects. I think our app is far behind the current version.
So I was wonder what is the best way to upgrade to the latest build?
Here is my though
1. Manually resolve these fail and rejects one by one.  There are might be more differences to resolve manually like db migrate, plugin….
2. Use the latest build as base, carry over the changes we made to the app. Then I figure out that the latest build is rails 2.3.2. Our app is still 2.1.0. This means the staging and production will require to upgrade to latest rails as well…

What’s the best choice? Any feedback is welcome!

Great questions. Sometimes we wish there was a magic button that you could click to have your changes easily merged with core. With that being said, if you haven’t made a whole lot of customizations then I would say option #2 is the way to go. If you’re still on Rails 2.1 then it would be easy to coordinate an upgrade with our support team to get you the latest version of the app. Your staging and production servers already have the latest versions of Rails. We manage this across all our VMs to keep them consistent. I would recommend running the latest version of the app on your local machine to become more familiar with the additions. You can download it here:

http://github.com/numerex/FAST_CORE_Tracking

I hope this helps.

Thanks for the reply. #2 is the approach that I am taking.

Great. Good luck and keep us posted. We want to find ways to make this process easier in the future and appreciate any feedback.

Just an update about our app upgrade progress. We took the latest release from github, migrate the customized changes we made to the new app. The first issue we ran into is the New_Relic plugin. After some digging, we upgraded the new_relic to the latest version, that fixed the issue. Why the latest build come with old version new_relic 2.3.4?  I don’t think it work with rails 2.3.2

Everything work fine except the admin/device. The error is
    app/models/device.rb:105:in `gateway_device’
  vendor/plugins/fast_admin/app/controllers/admin/devices_controller.rb:11:in `device_imei_or_link’

Any feedback is welcome!

Would you mind posting more of your error message so we can help troubleshoot? Thanks.