i have 2 port open on textdrive.
i have 2 configuration for the same server
ServerName corporateblogging.shoob.net
ProxyPass / http://shoob.net:2508/
ProxyPassReverse / http://shoob.net:2508/
an the standard configuration of the same subdomain created through webmin
Virtual Server Handles all requests to the address 70.84.216.2 on port
80. Server Name corporateblogging.shoob.net Map to URL
http://shoob.net:2508/
Virtual Server Handles all requests to the address 70.84.216.2 on port
80.Server Name corporateblogging.shoob.net
Document Root /home/shoobnet/domains/corporateblogging.shoob.net/web/public
when i launch instiki on textrive trough the command line with:
--command--
ruby /home/myhome/instiki/instiki.rb --daemon --port 2508 --storage
/home/myhome/instiki/storage/ -b 70.84.216.2
--command--
or shoob.net instead of 70.84.216.2
sometimes it work, sometimes not but event when it worked i ''ve an
rails
error when trying to submiting the first form create_system.
the rails error is just rails error because i''m on production. so a
added at the beginning in config/environments/production.rb
--production.rb--
begin
RAILS_DEFAULT_LOGGER =
Logger.new("#{RAILS_ROOT}/log/#{RAILS_ENV}.log")
rescue StandardError
RAILS_DEFAULT_LOGGER = Logger.new(STDERR)
RAILS_DEFAULT_LOGGER.level = Logger::WARN
RAILS_DEFAULT_LOGGER.warn(
"Rails Error: Unable to access log file. Please ensure that
log/#{RAILS_ENV}.log exist
s and is chmod 0666. " +
"The log level has been raised to WARN and the output directed to
STDERR until the pro
blem is fixed."
)
end
[ActiveRecord, ActionController, ActionMailer].each { |mod|
mod::Base.logger ||= RAILS_DEF
AULT_LOGGER }
RAILS_DEFAULT_LOGGER.level = Logger::WARN
.....
--production.rb--
is anybody get an idea of what to do, because i''ve already spend one
day
trying various alternative but always having this problem
Best regards
Lamotte Denis
Denis Lamotte wrote:> when i launch instiki on textrive trough the command line with: > --command-- > ruby /home/myhome/instiki/instiki.rb --daemon --port 2508 --storage > /home/myhome/instiki/storage/ -b 70.84.216.2 > --command-- > or shoob.net instead of 70.84.216.2 > > sometimes it work, sometimes not but event when it worked i ''ve an > rails error when trying to submiting the first form create_system.Looks like --daemon option is broken now. Having thought about it for a while, I''m fairly confident that all these problems are caused by starting the Madeleine thread before the fork. If anybody knows how to pass some initialization block to WEBRick (to be executed after the fork), please tell me or send me a patch. I haven''t figured it out so far. Madeleine thread in this line: ApplicationController.wiki = WikiService.instance Otherwise, the only solution I see at the moment is to copy/paste the forking code from WEBRick::Daemon#start into script/server, right after options parsing. Ugly, but would do the trick also. By the way, another good topic for a patch (along the same lines of "how do I run Instiki in a production environment") is some option(s) to control logging. Something like --log ''/path/to/log'' and maybe also --access_log ''/path/to/access_log'' for people who want access.log to be separated from all the Rails logging. May be also some option(s) to limit the verboseness of the Rails log (by default it''s quite talkative). -- Best regards, Alexey Verkhovsky Ruby Forum: http://ruby-forum.org (moderator) RForum: http://rforum.andreas-s.net (co-author) Instiki: http://instiki.org (maintainer)