These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
 

Any Ruby Guru's out there?
Author
Previous Topic Next Topic
Nemesis
Hyperion Engineering Inc
#1 - 2013-04-02 17:16:02 UTC
Hello all,

I'll keep this short.

I have a small bespoke Eve Online Ruby application that is used by my corporation

I have a VPS to set it up on, and i even have all the source files. However, Can i get the darn thing to work with my limited Ruby experience? not a chance.

I have an Ubuntu server and i believe i have all the required dependencies installed, however i've hit a 'stuck point' and need some help.

Happy to pay in Isk for the 'right person' to help me out and get this up and running. I have up to 350 mill to spend getting some help.

If the costs would come to more than that, we can discuss, please drop me a mail :)
AzAkiR NaLDa
Council of Exiles
Brave Collective
#2 - 2013-04-02 17:33:48 UTC
What is the exact problem you are getting?

Lone Star Warrior
Peter Powers
Terrorists of Dimensions
HORSE-KILLERS
#3 - 2013-04-03 15:25:04 UTC
if you actually post your question, people might be able to help you without you losing your iskies to some scammer =)

3rdPartyEve.net - your catalogue for 3rd party applications
Nemesis
Hyperion Engineering Inc
#4 - 2013-04-03 16:16:40 UTC
Well, i've basically just setup a VPS with Ubuntu, I Think i've got Ruby on Rails installed on it, and i have extracted the files that were on a previously fully functional site to a /var/www/ directory.

I can browse to this directory via IE, however it doesn't actually appear to load any pages.

This is where my experience with Ruby ends, as i've got no idea whether i need to configure some settings within the Ruby files, or what i'm missing!
Lorellei Blackmoon
Blackmoon Cartel
#5 - 2013-04-03 17:51:40 UTC
So, what you mean is that if you access the site through the browser it displays de directory listing but no page is executed, it that right?

If that is the case, it seems to me that your ruby application is not running. As far as I know (and it goes for all frameworks), they must be started so they can begin serving requests. You can check on how to start the rails server in here: http://guides.rubyonrails.org/getting_started.html
Or, as the forementioned documentation states, enter the command:
$ rails server

Hope this helps. ;-)
Nemesis
Hyperion Engineering Inc
#6 - 2013-04-03 18:14:19 UTC
If only it was that simple :)

Bit of back story.

On Saturday i was sent an application, and asked whether i could host. Normally, not a problem, I dont code myself, but i can usually muddle together and make something work.

I started With a base debian box, and frankly, found the whole process of getting ROR installed a pain, I was getting version and dependancy errors all over the place.

I did some reading for 2 days, and got to the stage where i started an Ubuntu box, managed to get Rails installed (I think) and was getting to the stage where i was initiating the app, but started getting 'Bundle' errors, which i seemed to resolve, then it moved on to Execjs errors, which again, i think i managed to resolve,

however having tried to run the command you specified, the error seemed to have reverted back to the same problem as yesterday, bundle update errors.


I have fixed this with the following :

bundle update

However then recieved the error regarding execjs again :
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/execjs-1.4.0/lib/execjs/runtimes.rb:51: in `autodetect': Could not find a JavaScript runtime. (ExecJS::RuntimeUnavailable)

I appear to have resolved this with : sudo apt-get install nodejs

However once again it appears to be rails that starts throwing errors at me again :

/config/initializers/active_admin.rb:1:in `': uninitialized constant ActiveAdmin (NameError)
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-3.2.13/lib/rails/engine.rb:588:in `block (2 levels) in '
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-3.2.13/lib/rails/engine.rb:587:in `each'
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-3.2.13/lib/rails/engine.rb:587:in `block in '
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-3.2.13/lib/rails/initializable.rb:30:in `instance_exec'
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-3.2.13/lib/rails/initializable.rb:30:in `run'
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-3.2.13/lib/rails/initializable.rb:55:in `block in run_initializers'
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-3.2.13/lib/rails/initializable.rb:54:in `each'
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-3.2.13/lib/rails/initializable.rb:54:in `run_initializers'
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-3.2.13/lib/rails/application.rb:136:in `initialize!'
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-3.2.13/lib/rails/railtie/configurable.rb:30:in `method_missing'
from /var/www/posmon/config/environment.rb:5:in `'
from /var/www/posmon/config.ru:3:in `require'
from /var/www/posmon/config.ru:3:in `block in '
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.5/lib/rack/builder.rb:51:in `instance_eval'
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.5/lib/rack/builder.rb:51:in `initialize'
from /var/www/posmon/config.ru:in `new'
from /var/www/posmon/config.ru:in `'
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.5/lib/rack/builder.rb:40:in `eval'
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.5/lib/rack/builder.rb:40:in `parse_file'
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.5/lib/rack/server.rb:200:in `app'
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-3.2.13/lib/rails/commands/server.rb:46:in `app'
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.5/lib/rack/server.rb:304:in `wrapped_app'
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/rack-1.4.5/lib/rack/server.rb:254:in `start'
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-3.2.13/lib/rails/commands/server.rb:70:in `start'
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-3.2.13/lib/rails/commands.rb:55:in `block in '
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-3.2.13/lib/rails/commands.rb:50:in `tap'
from /usr/local/rvm/gems/ruby-1.9.3-p392/gems/railties-3.2.13/lib/rails/commands.rb:50:in `'
from script/rails:6:in `require'
from script/rails:6:in `'

Hence the reason for offering to pay someone that knows more about Ruby than i do to resolve.

I'll be honest, it's not that i haven't tried my best for the last 4 days to resolve, it's just that i now lack the patience and would rather contract out the resolution :)
Gheent
Starshadow Corporation
#7 - 2013-04-03 18:25:51 UTC
Do you know what version of Ruby the original program was written for? There are significant differences between Ruby 1.8 and Ruby 1.9 that could be involved with the issues you're seeing.