ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Thin Server and Chiliproject trouble (changed the title bcuz I was asked nicely ) :)

Added by max zero at 2012-07-18 04:11 pm

For the past four days straight, I have been trying to install Chiliproject on
Windows 7 Ultimate, Ruby 1.9.3-p194 and MySQL Server 5.5
and it has been a fucking nightmare!!!

First, I ran into the RMagick problem, I can't bundle install the damn thing because the rmagick kept slapping my face exconf.rb exception. Honestly, that was my fault, because I was using the command prompt to set the variables and they disappear as soon as I close the command prompt.

Secondly, bundle exec rake db:migrate won't go thru. I copied over the libmysql.dll into Ruby\bin and still won't do it.


!!! The bundled mysql.rb driver has been removed from Rails 2.2. Please install
the mysql gem and try again: gem install mysql.
rake aborted!
cannot load such file -- mysql
Tasks: TOP => db:migrate => environment
(See full trace by running task with --trace)

I mean I have tried just about everything to get this running,


gem install mysql2
gem install mysql2 -- --with-mysql-lib=c:something\lib --with-mysql-include=c:something\include
gem install mysql2 --platform=ruby -- --with-mysql-dir=C:/mysql-connector-c-noinstall-6.0.2-win32

To no avail. :(

Then finally, I go like, ok let's get this running on thin.

And guess what? I get slapped in the face again. WHAT THE FUCKING HELL!!!!!?


Fetching: eventmachine-0.12.10.gem (100%)
Temporarily enhancing PATH to include DevKit...
Building native extensions. This could take a while...
ERROR: Error installing thin:
ERROR: Failed to build gem native extension.
C:/Ruby193/bin/ruby.exe extconf.rb
checking for rb_trap_immediate in ruby.h,rubysig.h... no
checking for rb_thread_blocking_region()... yes
checking for inotify_init() in sys/inotify.h... no
checking for __NR_inotify_init in sys/syscall.h... no
checking for writev() in sys/uio.h... no
checking for rb_thread_check_ints()... yes
checking for rb_time_new()... yes
checking for windows.h... yes
checking for winsock.h... yes
checking for main() in -lkernel32... yes
checking for main() in -lrpcrt4... yes
checking for main() in -lgdi32... yes
checking for main() in -lssl... no
creating Makefile
make
generating rubyeventmachine-i386-mingw32.def
compiling binder.cpp
cc1plus.exe: warning: command line option "-Wdeclaration-after-statement" is val
id for C/ObjC but not for C++
cc1plus.exe: warning: command line option "-Wimplicit-function-declaration" is v
alid for C/ObjC but not for C++
In file included from binder.cpp:20:0:
project.h:85:0: warning: "FD_SETSIZE" redefined
<command-line>:0:0: note: this is the location of the previous definition
In file included from project.h:137:0,
from binder.cpp:20:
binder.h:35:34: warning: type qualifiers ignored on function return type
In file included from project.h:138:0,
from binder.cpp:20:
em.h:91:47: warning: type qualifiers ignored on function return type
em.h:92:76: warning: type qualifiers ignored on function return type
em.h:93:56: warning: type qualifiers ignored on function return type
em.h:95:57: warning: type qualifiers ignored on function return type
em.h:96:60: warning: type qualifiers ignored on function return type
em.h:97:58: warning: type qualifiers ignored on function return type
em.h:98:55: warning: type qualifiers ignored on function return type
em.h:99:36: warning: type qualifiers ignored on function return type
em.h:101:47: warning: type qualifiers ignored on function return type
em.h:106:42: warning: type qualifiers ignored on function return type
em.h:123:45: warning: type qualifiers ignored on function return type
em.h:132:36: warning: type qualifiers ignored on function return type
In file included from project.h:145:0,
from binder.cpp:20:
eventmachine.h:45:61: warning: type qualifiers ignored on function return type
eventmachine.h:46:112: warning: type qualifiers ignored on function return type
eventmachine.h:47:69: warning: type qualifiers ignored on function return type
eventmachine.h:49:73: warning: type qualifiers ignored on function return type
eventmachine.h:62:75: warning: type qualifiers ignored on function return type
eventmachine.h:63:74: warning: type qualifiers ignored on function return type
eventmachine.h:64:77: warning: type qualifiers ignored on function return type
eventmachine.h:65:41: warning: type qualifiers ignored on function return type
In file included from project.h:145:0,
from binder.cpp:20:
eventmachine.h:99:60: warning: type qualifiers ignored on function return type
eventmachine.h:100:58: warning: type qualifiers ignored on function return type
eventmachine.h:102:60: warning: type qualifiers ignored on function return type
eventmachine.h:105:41: warning: type qualifiers ignored on function return type
compiling cmain.cpp
cc1plus.exe: warning: command line option "-Wdeclaration-after-statement" is val
id for C/ObjC but not for C++
cc1plus.exe: warning: command line option "-Wimplicit-function-declaration" is v
alid for C/ObjC but not for C++
In file included from cmain.cpp:20:0:
project.h:85:0: warning: "FD_SETSIZE" redefined
<command-line>:0:0: note: this is the location of the previous definition
In file included from project.h:137:0,
from cmain.cpp:20:
binder.h:35:34: warning: type qualifiers ignored on function return type
In file included from project.h:138:0,
from cmain.cpp:20:
em.h:91:47: warning: type qualifiers ignored on function return type
em.h:92:76: warning: type qualifiers ignored on function return type
em.h:93:56: warning: type qualifiers ignored on function return type
em.h:95:57: warning: type qualifiers ignored on function return type
em.h:96:60: warning: type qualifiers ignored on function return type
em.h:97:58: warning: type qualifiers ignored on function return type
em.h:98:55: warning: type qualifiers ignored on function return type
em.h:99:36: warning: type qualifiers ignored on function return type
em.h:101:47: warning: type qualifiers ignored on function return type
em.h:106:42: warning: type qualifiers ignored on function return type
em.h:123:45: warning: type qualifiers ignored on function return type
em.h:132:36: warning: type qualifiers ignored on function return type
In file included from project.h:145:0,
from cmain.cpp:20:
eventmachine.h:45:61: warning: type qualifiers ignored on function return type
eventmachine.h:46:112: warning: type qualifiers ignored on function return type
eventmachine.h:47:69: warning: type qualifiers ignored on function return type
eventmachine.h:49:73: warning: type qualifiers ignored on function return type
eventmachine.h:62:75: warning: type qualifiers ignored on function return type
eventmachine.h:63:74: warning: type qualifiers ignored on function return type
eventmachine.h:64:77: warning: type qualifiers ignored on function return type
eventmachine.h:65:41: warning: type qualifiers ignored on function return type
In file included from project.h:145:0,
from cmain.cpp:20:
eventmachine.h:99:60: warning: type qualifiers ignored on function return type
eventmachine.h:100:58: warning: type qualifiers ignored on function return type
eventmachine.h:102:60: warning: type qualifiers ignored on function return type
eventmachine.h:105:41: warning: type qualifiers ignored on function return type
cmain.cpp:98:71: warning: type qualifiers ignored on function return type
cmain.cpp:109:122: warning: type qualifiers ignored on function return type
cmain.cpp:119:79: warning: type qualifiers ignored on function return type
cmain.cpp:129:83: warning: type qualifiers ignored on function return type
cmain.cpp:260:85: warning: type qualifiers ignored on function return type
cmain.cpp:270:84: warning: type qualifiers ignored on function return type
cmain.cpp:280:88: warning: type qualifiers ignored on function return type
cmain.cpp:290:51: warning: type qualifiers ignored on function return type
cmain.cpp:300:70: warning: type qualifiers ignored on function return type
cmain.cpp:320:55: warning: type qualifiers ignored on function return type
cmain.cpp:546:70: warning: type qualifiers ignored on function return type
cmain.cpp:669:68: warning: type qualifiers ignored on function return type
cmain.cpp: In function 'int evma_send_file_data_to_connection(long unsigned int,
const char*)':
cmain.cpp:752:6: error: cannot convert 'stat*' to '_stati64*' for argument '2' t
o 'int _fstati64(int, _stati64*)'
make: *** [cmain.o] Error 1
Gem files will remain installed in C:/Ruby193/lib/ruby/gems/1.9.1/gems/eventmach
ine-0.12.10 for inspection.
Results logged to C:/Ruby193/lib/ruby/gems/1.9.1/gems/eventmachine-0.12.10/ext/g
em_make.out

Honestly, what's the usefulness of a FUCKING Windows installation document that's not even updated for the newest version of ruby and mysql.

To be very honest, I enjoy using open source software and respect them. Because its takes a lot of effort to build software (I am a programmer, I know better). But if you really are going to make a software, at least make sure that it works on a clean machine that doesn't have all the dependencies before you start spitting out 6-month update schedules.

And just to be fair, the only reason I am so PISSED OFF is because I was to use it in my office and I wasted those 4 days just trying to get this SHIT to work.

Chiliproject....FUCK U.

Heading over to Redmine (with reluctance).


Replies (17)

RE: FUCK U Chiliproject - Added by Gabriel Mazetto at 2012-07-19 06:37 am

Don't use windows for rails. simple like that.

RE: FUCK U Chiliproject - Added by max zero at 2012-07-19 11:49 am

If you can help great!

If you can't, don't be a douche bag and tell me not to use it on windows.

"simple like that."

RE: FUCK U Chiliproject - Added by Gabriel Mazetto at 2012-07-20 03:01 am

you are not going to get support by acting like you did, so, better try using another O.S. os just don't use chiliproject.

RE: FUCK U Chiliproject - Added by max zero at 2012-07-20 07:44 am

Gabriel Mazetto wrote:

you are not going to get support by acting like you did, so, better try using another O.S. os just don't use chiliproject.

Its very surprising that you should say that Gabe.

https://www.chiliproject.org/boards/1/topics/1911

I posted the above and no one has responded in past 14 hours.

No offense but what does that tell you?

RE: FUCK U Chiliproject - Added by Felix Schäfer at 2012-07-20 10:16 am

max zero wrote:

I posted the above and no one has responded in past 14 hours.

No offense but what does that tell you?

Well, actually I don't see "FUCK U" as "no offense"…

I can tell you what it does tell me though: every contributor is here on his free time, if you expect some sort of guaranteed response time or whatever, well, I guess you'll be waiting for it for a long time. The other thing it tells me is: I know no one who will voluntarily answer someone as obnoxious as you have been in the first post of this thread.

Honestly, when I got the email to this thread, my first reaction was "what the actual fuck?" and I pondered editing the post and banning its author for him to cool down. I decided to sleep it over though and had decided on the next day to wait until the WE to have enough time to take a look at everything as the problem seems to be somewhat lengthy.

If you want a guaranteed response time and people that will happily help even when shouted and sworn at though, I'd recommend you to go and get something with paid support, you're not going to find it here and probably not in other Open Source projects either, Redmine included.

RE: FUCK U Chiliproject - Added by max zero at 2012-07-20 12:42 pm

Felix Schäfer wrote:

max zero wrote:

I posted the above and no one has responded in past 14 hours.

No offense but what does that tell you?

Well, actually I don't see "FUCK U" as "no offense"…

I can tell you what it does tell me though: every contributor is here on his free time, if you expect some sort of guaranteed response time or whatever, well, I guess you'll be waiting for it for a long time. The other thing it tells me is: I know no one who will voluntarily answer someone as obnoxious as you have been in the first post of this thread.

Dear Felix,
I think you have might have misunderstood my last line.
All I am trying to point out is that when I made my post title very offensive I received an immediate response but when I made my post title as simple as thin server, it was ignored. That's all I meant.

I started on the wrong foot here. Let's start over

My name is max, I am trying to run thin server on my system.And I received the following error:

c:\chiliproject>thin start
Using rails adapter
C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active_support/infl
ector.rb:3:in `<top (required)>': iconv will be deprecated in the future, use St
ring#encode instead.
NOTE: Gem.source_index is deprecated, use Specification. It will be removed on o
r after 2011-11-01.
Gem.source_index called from C:/Ruby193/lib/ruby/gems/1.9.1/gems/rails-2.3.14/li
b/rails/gem_dependency.rb:21.
!!! The bundled mysql.rb driver has been removed from Rails 2.2. Please install
the mysql gem and try again: gem install mysql.
C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active_support/depe
ndencies.rb:182:in `require': cannot load such file -- mysql (MissingSourceFile)
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/dependencies.rb:182:in `block in require'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/dependencies.rb:547:in `new_constants_in'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/dependencies.rb:182:in `require'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/core_ext/kernel/requires.rb:7:in `block in require_library_or_gem'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/core_ext/kernel/reporting.rb:11:in `silence_warnings'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/core_ext/kernel/requires.rb:5:in `require_library_or_gem'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_
record/connection_adapters/mysql_adapter.rb:61:in `mysql_connection'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_
record/connection_adapters/abstract/connection_pool.rb:223:in `new_connection'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_
record/connection_adapters/abstract/connection_pool.rb:245:in `checkout_new_conn
ection'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_
record/connection_adapters/abstract/connection_pool.rb:188:in `block (2 levels)
in checkout'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_
record/connection_adapters/abstract/connection_pool.rb:184:in `loop'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_
record/connection_adapters/abstract/connection_pool.rb:184:in `block in checkout
'
from C:/Ruby193/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_
record/connection_adapters/abstract/connection_pool.rb:183:in `checkout'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_
record/connection_adapters/abstract/connection_pool.rb:98:in `connection'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_
record/connection_adapters/abstract/connection_pool.rb:326:in `retrieve_connecti
on'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_
record/connection_adapters/abstract/connection_specification.rb:123:in `retrieve
_connection'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_
record/connection_adapters/abstract/connection_specification.rb:115:in `connecti
on'
from c:/chiliproject/vendor/plugins/awesome_nested_set/lib/awesome_neste
d_set.rb:218:in `quoted_left_column_name'
from c:/chiliproject/vendor/plugins/awesome_nested_set/lib/awesome_neste
d_set.rb:94:in `acts_as_nested_set'
from c:/chiliproject/app/models/issue.rb:33:in `<class:Issue>'
from c:/chiliproject/app/models/issue.rb:15:in `<top (required)>'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/dependencies.rb:406:in `load'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/dependencies.rb:406:in `block in load_file'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/dependencies.rb:547:in `new_constants_in'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/dependencies.rb:405:in `load_file'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/dependencies.rb:285:in `require_or_load'
from c:/chiliproject/vendor/plugins/engines/lib/engines/rails_extensions
/dependencies.rb:133:in `require_or_load_with_engine_additions'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/dependencies.rb:451:in `load_missing_constant'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/dependencies.rb:106:in `const_missing_with_dependencies'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/dependencies.rb:118:in `const_missing'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/inflector.rb:375:in `const_get'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/inflector.rb:375:in `block in constantize'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/inflector.rb:374:in `each'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/inflector.rb:374:in `constantize'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/core_ext/string/inflections.rb:162:in `constantize'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_
record/observer.rb:157:in `observed_class'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_
record/observer.rb:183:in `observed_classes'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_
record/observer.rb:166:in `initialize'
from C:/Ruby193/lib/ruby/1.9.1/singleton.rb:141:in `new'
from C:/Ruby193/lib/ruby/1.9.1/singleton.rb:141:in `block in instance'
from <internal:prelude>:10:in `synchronize'
from C:/Ruby193/lib/ruby/1.9.1/singleton.rb:139:in `instance'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_
record/observer.rb:38:in `block in instantiate_observers'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_
record/observer.rb:36:in `each'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activerecord-2.3.14/lib/active_
record/observer.rb:36:in `instantiate_observers'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/actionpack-2.3.14/lib/action_co
ntroller/dispatcher.rb:15:in `block in define_dispatcher_callbacks'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/callbacks.rb:182:in `call'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/callbacks.rb:182:in `evaluate_method'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/callbacks.rb:166:in `call'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/callbacks.rb:90:in `block in run'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/callbacks.rb:90:in `each'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/callbacks.rb:90:in `run'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/activesupport-2.3.14/lib/active
_support/callbacks.rb:276:in `run_callbacks'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/actionpack-2.3.14/lib/action_co
ntroller/dispatcher.rb:51:in `run_prepare_callbacks'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/rails-2.3.14/lib/initializer.rb
:631:in `prepare_dispatcher'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/rails-2.3.14/lib/initializer.rb
:185:in `process'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/rails-2.3.14/lib/initializer.rb
:113:in `run'
from c:/chiliproject/config/environment.rb:45:in `<top (required)>'
from C:/Ruby193/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:i
n `require'
from C:/Ruby193/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:i
n `require'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/thin-1.4.1/lib/rack/adapter/rai
ls.rb:37:in `load_application'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/thin-1.4.1/lib/rack/adapter/rai
ls.rb:23:in `initialize'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/thin-1.4.1/lib/rack/adapter/loa
der.rb:45:in `new'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/thin-1.4.1/lib/rack/adapter/loa
der.rb:45:in `for'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/thin-1.4.1/lib/thin/controllers
/controller.rb:169:in `load_adapter'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/thin-1.4.1/lib/thin/controllers
/controller.rb:73:in `start'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/thin-1.4.1/lib/thin/runner.rb:1
85:in `run_command'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/thin-1.4.1/lib/thin/runner.rb:1
51:in `run!'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/thin-1.4.1/bin/thin:6:in `<top
(required)>'
from C:/Ruby193/bin/thin:23:in `load'
from C:/Ruby193/bin/thin:23:in `<main>'

I also tried the other method but failed.

bundle exec thin -e production -p 3001 start

And I receive the following error:

C:/Ruby193/lib/ruby/gems/1.9.1/gems/bundler-1.1.5/lib/bundler/rubygems_integrati
on.rb:147:in `block in replace_gem': thin is not part of the bundle. Add it to G
emfile. (Gem::LoadError)
from C:/Ruby193/bin/thin:22:in `<main>'

Can you please help? :(

RE: FUCK U Chiliproject - Added by Gabriel Mazetto at 2012-07-20 09:57 pm

Ruby 1.9.3 doesn't work with Rails 2.3.14, try with a lower version (i think 1.9.2 will work, but better with 1.8.7, until the project migrates to Rails 3.0.x)

You will also need to install mysql2 gem file. I assume you already fixed the compilation issue on the first topic

RE: FUCK U Chiliproject - Added by max zero at 2012-07-21 08:27 am

I fixed the compilation issue but due to some stupidity on my part I had to delete all the files and data (including the database).

So now I can't get past

bundle exec rake db:migrate

I can't remember how I did it the last time.

At any rate, tried to run the above with 1.8. No success :(

I have mysql2 0.2.18 and 0.3

Still, unable get it up 'n' running.

EDIT:

It seems that if I don't load the command

bundle exec rake generate_session_store

and directly run the following commands

set RAILS_ENV=production
bundle exec rake db:migrate

and also place the libmysql.dll in Ruby\bin

NOTE: used the libmysql.dll from mysql connector-c 6.0.2

The script runs fine. :)

But I can't get the Thin server running,

bundle exec thin -e production -p 3001 start

or

bundle exec thin start

Error:

C:/Ruby187/lib/ruby/gems/1.8/gems/bundler-1.1.5/lib/bundler/rubygems_integration
.rb:147:in `gem': thin is not part of the bundle. Add it to Gemfile. (Gem::LoadE
rror)
from C:/Ruby187/bin/thin:22

Command:

thin start

Error:

Using rails adapter
NOTE: Gem.source_index is deprecated, use Specification. It will be removed on o
r after 2011-11-01.
Gem.source_index called from C:/Ruby187/lib/ruby/gems/1.8/gems/rails-2.3.14/lib/
rails/gem_dependency.rb:21.
C:/Ruby187/lib/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/connecti
on_adapters/abstract/connection_specification.rb:62:in `establish_connection': d
evelopment database is not configured (ActiveRecord::AdapterNotSpecified)
from C:/Ruby187/lib/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_re
cord/connection_adapters/abstract/connection_specification.rb:55:in `establish_c
onnection'
from C:/Ruby187/lib/ruby/gems/1.8/gems/rails-2.3.14/lib/initializer.rb:4
38:in `initialize_database'
from C:/Ruby187/lib/ruby/gems/1.8/gems/rails-2.3.14/lib/initializer.rb:1
41:in `process'
from C:/Ruby187/lib/ruby/gems/1.8/gems/rails-2.3.14/lib/initializer.rb:1
13:in `send'
from C:/Ruby187/lib/ruby/gems/1.8/gems/rails-2.3.14/lib/initializer.rb:1
13:in `run'
from c:/chiliproject/config/environment.rb:45
from C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in
`gem_original_require'
from C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in
`require'
from C:/Ruby187/lib/ruby/gems/1.8/gems/thin-1.4.1/lib/rack/adapter/rails
.rb:37:in `load_application'
from C:/Ruby187/lib/ruby/gems/1.8/gems/thin-1.4.1/lib/rack/adapter/rails
.rb:23:in `initialize'
from C:/Ruby187/lib/ruby/gems/1.8/gems/thin-1.4.1/lib/rack/adapter/loade
r.rb:45:in `new'
from C:/Ruby187/lib/ruby/gems/1.8/gems/thin-1.4.1/lib/rack/adapter/loade
r.rb:45:in `for'
from C:/Ruby187/lib/ruby/gems/1.8/gems/thin-1.4.1/lib/thin/controllers/c
ontroller.rb:169:in `load_adapter'
from C:/Ruby187/lib/ruby/gems/1.8/gems/thin-1.4.1/lib/thin/controllers/c
ontroller.rb:73:in `start'
from C:/Ruby187/lib/ruby/gems/1.8/gems/thin-1.4.1/lib/thin/runner.rb:185
:in `send'
from C:/Ruby187/lib/ruby/gems/1.8/gems/thin-1.4.1/lib/thin/runner.rb:185
:in `run_command'
from C:/Ruby187/lib/ruby/gems/1.8/gems/thin-1.4.1/lib/thin/runner.rb:151
:in `run!'
from C:/Ruby187/lib/ruby/gems/1.8/gems/thin-1.4.1/bin/thin:6
from C:/Ruby187/bin/thin:23:in `load'
from C:/Ruby187/bin/thin:23

Since I am having so much trouble with Thin, is it possible to deploy chiliproject on WAMP server, if yes then HOW (please)?
And also, I want to modify the front page to require a user login before anything is displayed, which files should I tinker with?
And before I forget, in order to program chiliproject do I need to know Ruby and Ruby on Rails

RE: FUCK U Chiliproject - Added by Chili Fan at 2012-07-24 12:27 am

Please Edit your Topic Title have Respect! be polite, "Thin Server and Chiliproject trouble" could be an option

I am on almost the same road, which you can read here
https://www.chiliproject.org/boards/1/topics/1420?r=1763#message-1763
this means use chiliproject, sqlite, running as a windows service or server like tomcat.
Recently i readed this one from other Board Member which can be helpfull
https://www.chiliproject.org/boards/1/topics/1212?r=1861#message-1861
I readed you get ChiliProject running by using WEBrick but failing to use Warble and to use Thin Server as i understand,
Using Warble is other part, first it would be great if Thin Server or any other Server could be used for ChiliProject which i still struggle too to setup, I will give ThinServer a retry on my existing running ChiliProject WEBrick setup see i can make progress to setup a production server

RE: Thin Server and Chiliproject trouble (changed the title bcuz I was asked nicely ) :) - Added by max zero at 2012-07-25 10:42 am

I still dont understand what the hell is going on. Yesterday I was running CP on WEBrick, no issues.

Today, I don't know what the hell happened and I can't get CP started. To make matters worse I decided to reinstall Ruby,Devkit and CP, and now I am stuck at

bundle exec rake db:migrate

Installation Steps:

1. Install Ruby ( 1.9.3, tried 1.8.7 too with no luck), Unzip Devkit, Unzip chiliproject( rename to Project Manager).
2. Open Prompt, set to Directory "C:\Ruby\Devkit". Issued the following commands:

        a. ruby dk.rb init - OK
        b. ruby dk.rb install - OK
        c. gem update --system - OK
        d. gem install bundler - OK
        e. exit - OK

Note : All commands appended with 'OK' designate full completion without any errors

3. Open Prompt, set to Directory "C:\Project Manager". Issued the following commands:

        a. bundle install --without=test development - OK

- The installer informed to add "libmysql.dll" to "Ruby\bin"
- Since I am using MySQL 5.5 - 64bit, I used the Connector-C 64bit dll.

        b. exit - OK

4. Open Prompt, issued the following command:

        a. mysql --user=**** --pass=****
        b. create database projectmgr character set utf8; - OK
        c. create user 'admin'@'localhost' identified by 'admin'; - OK
        d. grant all privileges on projectmgr.* to 'admin'@'localhost'; -OK
        e. exit

5. Open config folder, copy database.yml.example, paste and rename to database.yml. Modified as follows:

         production:
                 adapter: mysql2
                 database: projectmgr
                 host: localhost
                 port: 3306
                 username: admin
                 password: admin
                 encoding: utf8

6. Open Prompt, set Directory to "C:\Project Manager". Issued the following commands:

        a. set RAILS_ENV=production - OK
        b. bundle exec rake db:migrate - ERROR!!!

Note: Previously, I was able to run db:migrate without using:

bundle exec rake generate_session_store (I ran that command as well to but still no success)

ERROR:

       rake aborted!
       Please install the mysql2 adapter: `gem install activerecord-mysql2-adapter` 
       (193: %1 is not a valid Win32 application.
       - C:/Ruby193/lib/ruby/gems/1.9.1/gems/mysql2-0.2.18-x86-mingw32/lib/mysql2/1.9/mysql2.so)

I already have mysql2 (0.2.18) and (0.3.11).

PLEASE do not ask/tell me to use Linux (or its derivative) because I can only deploy CP on a Windows Server.

RE: Thin Server and Chiliproject trouble (changed the title bcuz I was asked nicely ) :) - Added by paul young at 2012-07-25 12:05 pm

Just to add that me too, I had lots of troubles installing Chiliproject on windows XP from scratch.
I rigoursly followed step by step the instructions but I bumped to many problems as described above: rmagick(never solved), different gems not installing, I end up installing them one by one. I spent hours and hours of research on google and found some of the necessary information on redmine website(!): e.g. replacing mysql dll

I got sticked to it because I really want to make this work, but i'm sure many just gave up at the installation step.

I'm not here to complain since I know it's opensource that this is for free and I should not have too much expectations.
But I think it would really help Chiliproject to get more users if 100% working installations guides are provided, I would really consider it a priority among some other tasks.

that said, thanks to the chiliproject team to give us a such useful tool!

RE: Thin Server and Chiliproject trouble (changed the title bcuz I was asked nicely ) :) - Added by max zero at 2012-07-25 01:56 pm

paul young wrote:

Just to add that me too, I had lots of troubles installing Chiliproject on windows XP from scratch.
I rigoursly followed step by step the instructions but I bumped to many problems as described above: rmagick(never solved), different gems not installing, I end up installing them one by one. I spent hours and hours of research on google and found some of the necessary information on redmine website(!): e.g. replacing mysql dll

I got sticked to it because I really want to make this work, but i'm sure many just gave up at the installation step.

I'm not here to complain since I know it's opensource that this is for free and I should not have too much expectations.
But I think it would really help Chiliproject to get more users if 100% working installations guides are provided, I would really consider it a priority among some other tasks.

that said, thanks to the chiliproject team to give us a such useful tool!

Hey Paul,
Try these installations steps, they worked for me before but now they don't. But that doesn't necessarily mean they won't work for you.

Installation Steps For WINDOWS:

1. Install Ruby 1.8.7 to default (C:\Ruby187) http://rubyforge.org/frs/download.php/76277/rubyinstaller-1.8.7-p370.exe

, Unzip the DevKit to (C:\Ruby\DevKit) https://github.com/downloads/oneclick/rubyinstaller/DevKit-tdm-32-4.5.2-20111229-1559-sfx.exe

, Unzip ChiliProject to (C:\chiliproject) https://www.chiliproject.org/projects/chiliproject/files

2. Install RMagick, only the 32bit version works with ChiliProject
http://www.imagemagick.org/download/binaries/ImageMagick-6.7.8-6-Q16-windows-dll.exe

2a. Go to this link for gem dependencies
https://www.chiliproject.org/projects/chiliproject/wiki/Installation_on_Windows#Prepare-RMagick-gem-dependencies

3. Open Prompt, set to Directory "C:\Ruby\Devkit". Issue the following commands:

        > ruby dk.rb init
        > ruby dk.rb install
        > gem update --system
        > gem install bundler
        > exit

4. Right Click on My Computer->Properties->(TAB) Advanced->(BUTTON) Environment Variables

- In the System Variables section click on New and provide the following info:
Variable Name: CPATH
Variable Value: C:\Program Files\ImageMagick-6.7.8-Q16\include

(WARNING: Your path might be different from this)

- Then create another System Variable, with the following info:
Variable Name: LIBRARY_PATH
Variable Value: C:\Program Files\ImageMagick-6.7.8-Q16\lib

(WARNING: Your path might be different from this)

5. Install MySQL, if your WinXP is 32bit then get 32bit Version, if 64bit then get 64bit version.

And DO NOT UNDER ANY CIRCUMSTANCES FORGET TO LAUNCH "MySQL Instance Configuration" - You'll thank me later.

6. Now go to http://dev.mysql.com/downloads/connector/c/
And download the zip file for the bit version you have installed.

-From the zip file, go to lib folder and extract libmysql.dll to C:\Ruby187\bin

Note: there are two versions of each bit version, one standard and one for Visual Studio 2005. I don't think it matters much but try the standard version first, hopefully it won't fail. But if it does, try the VS2005 version.

Cross Your Fingers

7. Open Prompt, set to Directory "C:\chilicroject". Issue the following command:

        > bundle install --without=test development
        > exit

If you did everything right, all the gems would be installed. And you would receive the notification of putting the libmysql.dll in Ruby\bin which was done previously.

8. Open Prompt, issued the following command:

        > mysql --user=root --pass=****
        mysql> create database chiliproject character set utf8;
        mysql> create user 'chiliproject'@'localhost' identified by 'chili'; 

                           Note: You can set any password you like, just don't forget it. Please :)

        mysql> grant all privileges on chiliproject.* to 'chiliproject'@'localhost';
        mysql> exit
        > exit

9. Open chiliproject/config folder, copy database.yml.example, paste and rename to database.yml. Modified as follows:

         production:
                 adapter: mysql2
                 database: chiliproject
                 host: localhost
                 port: 3306
                 username: chiliproject
                 password: chili
                 encoding: utf8

Note: No quotes are needed in this file.

Moment of Truth

10. Open Prompt, set Directory to "C:\chiliproject". Issue the following commands:

        > set RAILS_ENV=production
        > bundle exec rake db:migrate

Note: I skipped a step on purpose

      bundle exec rake generate_session_store 

This line is to be after set RAILS_ENV=production

- If everything went well, then you should see the script building the database.

- If it DIDN'T work then go to step 10. And include the skipped line after the set command.

- If including the skipped line in step 10, still doesn't do it. Then Welcome to the Club (Club Stuck on db:migrate) and it sucks.

11. Then issue the following command on the same Prompt:

        bundle exec rake redmine:load_default_data

12. Then issue the following command to check the website on WEBRick


        bundle exec ruby script/server -e production

13. Go to http://localhost:3000 to check.

if it works, CONGRATULATIONS.

else...

RE: Thin Server and Chiliproject trouble (changed the title bcuz I was asked nicely ) :) - Added by Chili Fan at 2012-07-25 02:12 pm

Max zero these are my steps so far https://www.chiliproject.org/boards/1/topics/1420?r=1942#message-1942
which works instantly here, to get sqlite based chiliproject, give it a try and let know if it works, next try mysql or keep at sqlite

RE: Thin Server and Chiliproject trouble (changed the title bcuz I was asked nicely ) :) - Added by Gabriel Mazetto at 2012-07-25 03:27 pm

max zero wrote:

I still dont understand what the hell is going on. Yesterday I was running CP on WEBrick, no issues.

Today, I don't know what the hell happened and I can't get CP started. To make matters worse I decided to reinstall Ruby,Devkit and CP, and now I am stuck at

bundle exec rake db:migrate

Installation Steps:

1. Install Ruby ( 1.9.3, tried 1.8.7 too with no luck), Unzip Devkit, Unzip chiliproject( rename to Project Manager).
2. Open Prompt, set to Directory "C:RubyDevkit". Issued the following commands:
[...]

Note : All commands appended with 'OK' designate full completion without any errors

3. Open Prompt, set to Directory "C:Project Manager". Issued the following commands:
[...]
- The installer informed to add "libmysql.dll" to "Rubyin"
- Since I am using MySQL 5.5 - 64bit, I used the Connector-C 64bit dll.

[...]

4. Open Prompt, issued the following command:
[...]

5. Open config folder, copy database.yml.example, paste and rename to database.yml. Modified as follows:
[...]

6. Open Prompt, set Directory to "C:Project Manager". Issued the following commands:

[...]

Note: Previously, I was able to run db:migrate without using:

bundle exec rake generate_session_store (I ran that command as well to but still no success)

ERROR:

[...]

I already have mysql2 (0.2.18) and (0.3.11).

PLEASE do not ask/tell me to use Linux (or its derivative) because I can only deploy CP on a Windows Server.

i dont use or have tried to use rails on windows yet (and probably never will) so I cant give you any specific instructions to your platform, but mysql2 is a commin trouble library, and it have really specific versions for specific rails versions.

You should try to google for how to install mysql2 and which version to use, for rails 2.3.14 on windows. This may help you progress on your installation.

Dont forget to update instructions on our wiki, as doing so, you will help any other one who decide to go for the windows path.

I understand that you may not have an option about the OS, but I should warn you that windows is not a first grade citizen on rails world and will perform worst, will lack support, etc.

For personal growth, I recommend that in your free time, you start learning Linux and see how easier is to use rails with it

RE: FUCK U Chiliproject - Added by Felix Schäfer at 2012-07-26 09:16 pm

max zero wrote:

I think you have might have misunderstood my last line.
All I am trying to point out is that when I made my post title very offensive I received an immediate response but when I made my post title as simple as thin server, it was ignored. That's all I meant.

Yeah, you got exasperated responses that didn't really help you. If you just want answers, here's probably not the best place to post, if you want help, you'll have to accept that everyone's here on their free time, i.e. that you won't necessarily get answers in an hour or two, and that there's only a few people if any who use windows, so we're all making suppositions here, it's not based on knowledge.

For the record, I don't like obnoxious people, I equally don't like people trying to get attention by being provocative.

Now, back to reading the rest of this thread.

RE: FUCK U Chiliproject - Added by Felix Schäfer at 2012-07-26 09:25 pm

Gabriel Mazetto wrote:

Ruby 1.9.3 doesn't work with Rails 2.3.14, try with a lower version (i think 1.9.2 will work, but better with 1.8.7, until the project migrates to Rails 3.0.x)

Yes and no. Rails 2.3 on its own doesn't support ruby 1.9.3, we've added the necessary workarounds to make ChiliProject work on ruby 1.9.3 though and will try to support 1.9.3 if it doesn't get too complicated. When encountering problems on ruby 1.9.3 though, downgrading to 1.9.2 to make sure the problem isn't related to ruby 1.9.3 is a good first step.

You will also need to install mysql2 gem file. I assume you already fixed the compilation issue on the first topic

The mysql gem doesn't support ruby 1.9 indeed, the mysql2 gem is needed on ruby 1.9 systems with MySQL. Actually the Gemfile in ChiliProject won't install the mysql gem on 1.9 under any circumstance.

RE: Thin Server and Chiliproject trouble (changed the title bcuz I was asked nicely ) :) - Added by Felix Schäfer at 2012-07-26 09:35 pm

paul young wrote:

I rigoursly followed step by step the instructions but I bumped to many problems as described above

The "problem" is that the windows instructions are community-contributed, i.e. we haven't tried them and don't have the time to do so. If you see things that can be improved or some notes you deem important, feel free to add them to make it easier for the next person using it to install ChiliProject.

(1-17/17)