Added private and public whois, refactored to dir

This commit is contained in:
Andres Keskküla 2014-12-08 16:03:40 +02:00
parent 3c5563b9a9
commit 67519a46f4
7 changed files with 17 additions and 17 deletions

View file

@ -0,0 +1,3 @@
class WhoisDomain < WhoisPrivateServer
self.table_name = 'domains'
end

View file

@ -0,0 +1,4 @@
class WhoisPrivateServer < ActiveRecord::Base
self.abstract_class = true
establish_connection :"#{Rails.env}_private_whois"
end

View file

@ -0,0 +1,3 @@
class WhoisDomain < WhoisPublicServer
self.table_name = 'domains'
end

View file

@ -0,0 +1,4 @@
class WhoisPublicServer < ActiveRecord::Base
self.abstract_class = true
establish_connection :"#{Rails.env}_public_whois"
end

View file

@ -1,3 +0,0 @@
class WhoisDomain < WhoisServer
self.table_name = 'domains'
end

View file

@ -1,4 +0,0 @@
class WhoisServer < ActiveRecord::Base
self.abstract_class = true
establish_connection :"#{Rails.env}_whois"
end

View file

@ -6,17 +6,10 @@ that disables whois (effects should fully be loaded after restarting the app)
What whois_enabled=false does is that the whois callback does not get included.
Delayed jobs migration and everything else will still be installed tho.
If you wish to use the whois module, tho, you need a whois database looking something like this
Basic whois logic - we save whois data to 2 separate databases - whois private and public.
Those two databases are streamed to appropriate whois servers.
```ruby
create_table :domains do |t|
t.string :name
t.text :body
t.timestamps
end
```
NB! Migration with rake tasks is available in whois app repo.
NB! Migration with rake tasks for whois part of the code is available in whois app repo.
For development, delayed_job queue can be handled by rake task
`rake jobs:work` or if you wish to be fancy you can use a daemon with `bin/delayed_job start`