Skip to content

Option for evergreen to run its own server instead of mounting on top of Rails application #36

@dlee

Description

@dlee

I have a catch-all route get "*path" => "controller#method" that prevents tests from reaching /evergreen.

I was surprised at first that javascript tests would have anything to do with Rails routes.

My assumption is that you run evergreen on the actual app server to support sprockets. I suggest running a standalone evergreen server that has sprocket support instead of starting up the entire Rails app. Besides, loading the entire Rails app is quite a heavy bootstrapping requirement that loads a bunch of unnecessary dependencies.

At the minimum, the evergreen server should always have /evergreen accessible, even if that means adding a Rails route map that has precedence over all other routes.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions