Photos will be uploaded here from time to time
I was testing Zimbra with several mail client. Everything worked fine (Thunderbird, Mac Mail, …) except outlook. Outlook always complained “None of the Authentication Methods Supported By This Client Are Supported By Your Server”.
I found several hints on the net about how to solve this but none of them helped.
After checking and rechecking the Account settings I noticed that encryption type for SMTP and IMAP where both set to “None” even if you tell outlook to use encryption. So here is what you have to do to get it working:
- In the account settings click on “More Settings …”
- On the Advanced Tab, change the encryption type from “none” to what ever works with your server, or just try “auto”
I really can’t understand why “none” is the default … but who understands Microsoft …
Seems like I have one of the oldest, if not the oldest, hard disk in the world in one of my servers
Didn’t know they had SATA 136 years ago.
No, that’s not me
Creating a executable file (.exe for windows for example) from a Ruby on Rails application isn’t something really new. There enough informations about that on the net, the best one can be found here.
Well, then why am I writing this blog? Well the manual from Erik Veenstra ist quite good, but what I didn’t find there anywhere was how to get the migrations done! I want to be able to give this .exe file to someone (or actually I was forced to do it this way) and they should be able to use the application, but when you keep updates in mind then you must have some way to also get migrations working.
I will be repeating some steps that are already mentioned in the “Distributing Rails Applications” tutorial.
First add this to the top of your environment.rb, this is a bit different then mentioned in the tutorial. Basically it should be working as mentioned in the tutorial, but in the last two days I was trying to solve this problem until late in the night and can’t really remember why I changed it
module Rails class Configuration def database_configuration conf = YAML::load(ERB.new(IO.read(database_configuration_file)).result) if defined?(TAR2RUBYSCRIPT) conf.each do |k, v| if v["adapter"] =~ /^sqlite3/ v["database"] = oldlocation(v["database"]) if v.include?("database") v["dbfile"] = oldlocation(v["dbfile"]) if v.include?("dbfile") end end else YAML::load(ERB.new(IO.read(database_configuration_file)).result) end end end end
Create a init.rn in the root of your application folder, you can remove the three “puts” lines, just added them for debug purposes.
at_exit do require "irb" require "drb/acl" require "sqlite3" end puts "Running as an RBA." if defined?(TAR2RUBYSCRIPT) puts "Runing from: " oldlocation puts "Runing in: " newlocation load "mig.rb" load "script/server"
As you can see there is a new “load” line which load mig.rb before starting the server. Here is where the magic happens.
Actually the mig.rb is nothing but a copy of the rake script with a extra line.
require 'rubygems' require 'rake' version = ">= 0" ARGV
Sightseeing tour trough Paris