Note that there are some explanatory texts on larger screens.

plurals
  1. POTorqueBox deployment not honoring context?
    primarykey
    data
    text
    <p>I am trying out TorqueBox and having issues with my deployment descriptor. I'm using 2.0-beta2 with jruby-1.6.5. When I deploy to using the <code>torquebox deploy</code> command, the application gets deployed within the application server; however, it is always at the root context (/) instead of the context I am specifying within my config. Here is my config/torquebox.rb:</p> <pre><code>TorqueBox.configure do |cfg| cfg.environment do RACK_ENV "qa" end cfg.web do |web| web.host "localhost" web.context "/my_application" end cfg.ruby do |ruby| ruby.version "1.9" end end </code></pre> <p>I tried it with and without having the host defined as well, and nothing changed. Its interesting because I know that its reading my config as I see the following within the run log: </p> <blockquote> <p>14:53:00,497 INFO [org.torquebox.core] (MSC service thread 1-2) evaling: "/Users/ejlevin1/Documents/Workspace/my_application/config/torquebox.rb"</p> </blockquote> <p>However, I feel like the line within the log a few lines down is showing it isn't honoring my context:</p> <blockquote> <p>14:53:01,499 INFO [org.torquebox.core.runtime] (Thread-95) Creating ruby runtime (ruby_version: RUBY1_9, compile_mode: JIT, app: my_application, context: web)</p> </blockquote> <p>Does anyone know what I am doing wrong? I tried deploying 2 applications to see if the server only honored this in the case of multiple applications running; however, that just gave me an error that seemed to be because they were both mounting off of root (/). </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload