Results logged to /var/www/discourse/vendor/bundle/ruby/2.0.0/extensions/x86_64-linux/2.0.0-static/eventmachine-126.96.36.199/gem_Using excon 0.45.4 Using exifr 1.2.4 Using fabrication 2.9.8 Using fakeweb 1.3.0 Using multipart-post 2.0.0 Using fast_blank 1.0.0 Installing fast_stack 0.2.0 with native extensions Gem:: Ext:: Build Error: ERROR: Failed to build gem native extension.
Hi, I just got a message on my new discourse forum to upgrade to the latest version.
It's an extremely popular framework - the project has over 11,000 stars on Github, and it's one of the top 100 most popular projects on the site.
However, we've had a very poor experience with it, and with Waterline, the ORM that runs underneath it.
Fetching gem metadata from https://rubygems.org/ Fetching version metadata from https://rubygems.org/ Fetching dependency metadata from https://rubygems.org/ Using rake 10.5.0 Using i18n 0.7.0 Using json 1.8.3 Using minitest 5.8.4 Using thread_safe 0.3.5 Using builder 3.2.2 Using erubis 2.7.0 Installing mini_portile2 2.1.0 Installing pkg-config 1.1.7 Using rack 1.6.4 Using mime-types 2.99.1 Using arel 6.0.3 Using jmespath 1.1.3 Using babel-source 5.8.34 Using execjs 2.6.0 Using ember-source 1.12.2 Using byebug 8.2.1 Using certified 1.0.0 Using coderay 1.1.0 Using concurrent-ruby 1.0.2 Using connection_pool 2.2.0 Using crass 1.0.2 Using daemons 1.2.3 Using diff-lcs 1.2.5 Using thor 0.19.1 Using discourse_fastimage 2.0.0 Using docile 1.1.5 Using unf_ext 0.0.7.1 Using email_reply_trimmer 0.1.3 Installing eventmachine 188.8.131.52 with native extensions Gem:: Ext:: Build Error: ERROR: Failed to build gem native extension.
current directory: /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/eventmachine-184.108.40.206/ext /usr/local/bin/ruby -r ./siteconf20160522-8243-1yibai4Cannot allocate memory - /usr/local/bin/ruby -r ./siteconf20160522-8243-1yibai42&1 Gem files will remain installed in /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/eventmachine-220.127.116.11 for inspection.
These issues are going to be Postgres oriented, because that's the database we use.
Some of these have since been fixed, but almost all of them (apart from the data corruption issues) have bit us at one point or another.* I appreciate the hard work put in by the Sails/Waterline team and contributors, and it seems like they're really interested in fixing a lot of the issues above.
You can find an example configuration for Cent OS, given that unix ODBC and freetds packages have been installed.
The Shyp API currently runs on top of the Sails JS framework.
You can configure Mongoose IM appropriately by using the following command (assuming you're in the top-level directory of the checked out repository): You also need Free TDS (an ODBC driver for MSSQL) installed in your system.