You need to create a new app first (rails new)
then follow the installation instruction.

CE is supposed to be used as an Engine.


On Monday, March 10, 2014 7:05:20 PM UTC-7, Jeremias Santos wrote:
>
> I'm still grasping ruby and rails, but must use this design looks pretty 
> cool, but I'm somewhat difficult to run and if you can help thank algume 
> now. 
>
> I'm trying to use the rails4, but downloaded the branch and after 
> installing the dependencies, I tried to run and I get the following error:
>
> Usage:
>   rails new APP_PATH [options]
>
> Options:
>   -r, [--ruby=PATH]              # Path to the Ruby binary of your choice
>                                  # Default: 
> /home/jeremias/.rvm/rubies/ruby-2.1.0/bin/ruby
>   -m, [--template=TEMPLATE]      # Path to some application template (can 
> be a filesystem path or URL)
>       [--skip-gemfile]           # Don't create a Gemfile
>   -B, [--skip-bundle]            # Don't run bundle install
>   -G, [--skip-git]               # Skip .gitignore file
>       [--skip-keeps]             # Skip source control .keep files
>   -O, [--skip-active-record]     # Skip Active Record files
>   -S, [--skip-sprockets]         # Skip Sprockets files
>   -d, [--database=DATABASE]      # Preconfigure for selected database 
> (options: 
> mysql/oracle/postgresql/sqlite3/frontbase/ibm_db/sqlserver/jdbcmysql/jdbcsqlite3/jdbcpostgresql/jdbc)
>                                  # Default: sqlite3
>   -j, [--javascript=JAVASCRIPT]  # Preconfigure for selected JavaScript 
> library
>                                  # Default: jquery
>   -J, [--skip-javascript]        # Skip JavaScript files
>       [--dev]                    # Setup the application with Gemfile 
> pointing to your Rails checkout
>       [--edge]                   # Setup the application with Gemfile 
> pointing to Rails repository
>   -T, [--skip-test-unit]         # Skip Test::Unit files
>       [--rc=RC]                  # Path to file containing extra 
> configuration options for rails command
>       [--no-rc]                  # Skip loading of extra configuration 
> options from .railsrc file
>
> Runtime options:
>   -f, [--force]    # Overwrite files that already exist
>   -p, [--pretend]  # Run but do not make any changes
>   -q, [--quiet]    # Suppress status output
>   -s, [--skip]     # Skip files that already exist
>
> Rails options:
>   -h, [--help]     # Show this help message and quit
>   -v, [--version]  # Show Rails version number and quit
>
> Description:
>     The 'rails new' command creates a new Rails application with a default
>     directory structure and configuration at the path you specify.
>
>     You can specify extra command-line arguments to be used every time
>     'rails new' runs in the .railsrc configuration file in your home 
> directory.
>
>     Note that the arguments specified in the .railsrc file don't affect the
>     defaults values shown above in this help message.
>
> Example:
>     rails new ~/Code/Ruby/weblog
>
>     This generates a skeletal Rails installation in ~/Code/Ruby/weblog.
>     See the README in the newly created application to get going.
> jeremias@jeremiasNot:/opt/WORK/WorkRubyOnRails/communityengine$ git pull
> Cannot pull with rebase: You have unstaged changes.
> Please commit or stash them.
>
>
>
>
>
>
>
>
> On Sunday, December 1, 2013 8:24:58 PM UTC-3, Bruno wrote:
>>
>> Hi all,
>> Just wanted to let you know we now have a Rails4  (Ruby 2.0) compatible 
>> branch with passing tests:
>>
>> https://github.com/bborn/communityengine/tree/rails4
>>
>> I'm not super-confident that this branch is without bugs yet, since I'm 
>> not using it on any of my apps. I'd appreciate some help getting it tested 
>> a little better.
>>
>> Thanks,
>> Bruno
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"CommunityEngine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to communityengine+unsubscr...@googlegroups.com.
To post to this group, send email to communityengine@googlegroups.com.
Visit this group at http://groups.google.com/group/communityengine.
For more options, visit https://groups.google.com/d/optout.

Reply via email to