Letractively / rubycas-server

Automatically exported from code.google.com/p/rubycas-server
GNU Lesser General Public License v2.1
0 stars 0 forks source link

Using passenger standalone to run the app #112

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
I'm trying to deploy your rubycas server using passenger standalone (I will use 
apache with mod_proxy in production to provide ssl support and access from 
browsers and real applications). I did this to run the app

$ CONFIG_FILE=/path/to/config/config.yml passenger start -p 4443 -a 127.0.0.1
=============== Phusion Passenger Standalone web server started ===============
PID file: /Users/fabio/Desktop/work/rubycas-server/tmp/pids/passenger.4443.pid
Log file: /Users/fabio/Desktop/work/rubycas-server/log/passenger.4443.log
Environment: development
Accessible via: http://127.0.0.1:4443/

You can stop Phusion Passenger Standalone by pressing Ctrl-C.
===============================================================================
Cannot execute 
'/Users/fabio/.passenger/standalone/3.0.7-x86_64-ruby1.9.2-macosx-10.6/support/h
elper-scripts/prespawn http://127.0.0.1:4443': Permission denied (13)

It seems to work normally, but I receive a warning as you can see in the last 
line of the output. Should I worry about that? Is this configuration safe in a 
production environment?

What version of RubyCAS-Server are you using? How is it installed (rubygem,
manual install)? How are you running it (webrick, mongrel, passenger,
etc.)?

I checked out it from git, I plan to deploy the rubygem version in production.

If relevant, please paste your RubyCAS-Server config.yml file here.

database:
  adapter: sqlite3
  database: db/casserver.sqlite3
  reconnect: true
authenticator:
    class: CASServer::Authenticators::Google
theme: simple
organization: Foo
infoline: Powered by CAS
default_locale: en
log:
  file: /tmp/casserver.log
  level: INFO

Original issue reported on code.google.com by f.napole...@gmail.com on 17 May 2011 at 1:36

GoogleCodeExporter commented 8 years ago
The warning seems to be related to passenger 3.0.7 
http://blog.phusion.nl/2011/04/14/phusion-passenger-3-0-7-released/, so forget 
about it.

Anyway, my question still stands, is it safe to run your application with 
passenger standalone? Is this the right way?

Thanks.

Original comment by f.napole...@gmail.com on 17 May 2011 at 1:46

GoogleCodeExporter commented 8 years ago
I've never tried it with passenger standalone. All of our deployments are using 
passenger + apache.

Original comment by matt.zuk...@gmail.com on 17 May 2011 at 2:18

GoogleCodeExporter commented 8 years ago

Original comment by matt.zuk...@gmail.com on 17 May 2011 at 2:19

GoogleCodeExporter commented 8 years ago
Ok, thanks for the answer. I'll try and let you know.

Original comment by f.napole...@gmail.com on 17 May 2011 at 2:22