Still using lineman?
I'm having a similar problem to the prior user:
https://www.loomio.org/d/1dGJrVve/problem-after-create-user
which was solved by running lineman. I followed the directions for installing lineman but I can't find a directory for lineman and am getting a grunt file error.
Is lineman no longer part of loomio?
Here's my error which I get after creating a user:
Started GET "/client/development/app.min.css" for 192.168.99.1 at 2016-02-13 13:32:38 -0500
ActionController::RoutingError (No route matches [GET] "/client/development/app.min.css"):
actionpack (4.2.5.1) lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'
actionpack (4.2.5.1) lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
railties (4.2.5.1) lib/rails/rack/logger.rb:38:in `call_app'
railties (4.2.5.1) lib/rails/rack/logger.rb:20:in `block in call'
activesupport (4.2.5.1) lib/active_support/tagged_logging.rb:68:in `block in tagged'
activesupport (4.2.5.1) lib/active_support/tagged_logging.rb:26:in `tagged'
activesupport (4.2.5.1) lib/active_support/tagged_logging.rb:68:in `tagged'
railties (4.2.5.1) lib/rails/rack/logger.rb:20:in `call'
ahoy_matey (1.1.1) lib/ahoy/engine.rb:20:in `call_with_quiet_ahoy'
request_store (1.1.0) lib/request_store/middleware.rb:8:in `call'
actionpack (4.2.5.1) lib/action_dispatch/middleware/request_id.rb:21:in `call'
rack (1.6.4) lib/rack/methodoverride.rb:22:in `call'
rack (1.6.4) lib/rack/runtime.rb:18:in `call'
activesupport (4.2.5.1) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
rack (1.6.4) lib/rack/lock.rb:17:in `call'
actionpack (4.2.5.1) lib/action_dispatch/middleware/static.rb:116:in `call'
rack (1.6.4) lib/rack/sendfile.rb:113:in `call'
airbrake (4.1.0) lib/airbrake/user_informer.rb:16:in `_call'
airbrake (4.1.0) lib/airbrake/user_informer.rb:12:in `call'
railties (4.2.5.1) lib/rails/engine.rb:518:in `call'
railties (4.2.5.1) lib/rails/application.rb:165:in `call'
rack (1.6.4) lib/rack/content_length.rb:15:in `call'
thin (1.6.3) lib/thin/connection.rb:86:in `block in pre_process'
thin (1.6.3) lib/thin/connection.rb:84:in `catch'
thin (1.6.3) lib/thin/connection.rb:84:in `pre_process'
thin (1.6.3) lib/thin/connection.rb:53:in `process'
thin (1.6.3) lib/thin/connection.rb:39:in `receive_data'
eventmachine (1.0.7) lib/eventmachine.rb:187:in `run_machine'
eventmachine (1.0.7) lib/eventmachine.rb:187:in `run'
thin (1.6.3) lib/thin/backends/base.rb:73:in `start'
thin (1.6.3) lib/thin/server.rb:162:in `start'
rack (1.6.4) lib/rack/handler/thin.rb:19:in `run'
rack (1.6.4) lib/rack/server.rb:286:in `start'
railties (4.2.5.1) lib/rails/commands/server.rb:80:in `start'
railties (4.2.5.1) lib/rails/commands/commands_tasks.rb:80:in `block in server'
railties (4.2.5.1) lib/rails/commands/commands_tasks.rb:75:in `tap'
railties (4.2.5.1) lib/rails/commands/commands_tasks.rb:75:in `server'
railties (4.2.5.1) lib/rails/commands/commands_tasks.rb:39:in `run_command!'
railties (4.2.5.1) lib/rails/commands.rb:17:in `'
script/rails:6:in `require'
script/rails:6:in `'
Rendered /home/loomio/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/actionpack-4.2.5.1/lib/action_dispatch/middleware/templates/rescues/_trace.html.erb (1.9ms)
Rendered /home/loomio/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/actionpack-4.2.5.1/lib/action_dispatch/middleware/templates/routes/_route.html.erb (33.1ms)
Rendered /home/loomio/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/actionpack-4.2.5.1/lib/action_dispatch/middleware/templates/routes/_route.html.erb (0.2ms)
Rendered /home/loomio/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/actionpack-4.2.5.1/lib/action_dispatch/middleware/templates/routes/_table.html.erb (4.0ms)
Rendered /home/loomio/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/actionpack-4.2.5.1/lib/action_dispatch/middleware/templates/rescues/_request_and_response.html.erb (1.3ms)
Rendered /home/loomio/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/actionpack-4.2.5.1/lib/action_dispatch/middleware/templates/rescues/routing_error.html.erb within rescues/layout (128.9ms)
Thanks Markus, that fixed my problem.
+1, we've moved off lineman to a gulp build system which is oh so much more simple and extensible.
I had to do one further thing before gulp dev worked:
npm install -g gulp
@matthewbartlett ah right forgot about that part, in my case I'm using nenv-binstubs so I had to run nenv rehash to make gulp available.
I just set up my own instance a few days ago and didn't have to do anything with lineman, but you do need to build the Angular app:
See angular/README.md for more information.