GithubHelp home page GithubHelp logo

ministryofjustice / accelerated_claims Goto Github PK

View Code? Open in Web Editor NEW
0.0 0.0 1.0 19.33 MB

** Unmaintained repository! ** Accelerated Claims app

License: Other

Ruby 68.52% CoffeeScript 16.21% JavaScript 4.33% HTML 10.05% CSS 0.73% Shell 0.16%

accelerated_claims's People

Contributors

ashb avatar axemonkey avatar colinbruce avatar dotemacs avatar leoapost avatar lmoney-moj avatar marcincichon avatar mattmb avatar maxf avatar mikepea avatar mloughran avatar pwyborn avatar robmckinnon avatar robyoung avatar stephenrichards avatar symroe avatar tatyree avatar whoojemaflip avatar zaparka avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Forkers

uk-gov-mirror

accelerated_claims's Issues

Use of OGL for code?

When I reviewed this as part of a digital service assessment it had an MIT license (if memory services). I see that has been removed in place of the OGL.

Is OGL compatible with other open source licenses?

I can't find any guidance, advice or other discussions - which would suggest this could create a degree of uncertainty. At @alphagov we explicitly made the decision to use a well understood license for code (normally MIT) and retain OGL for content.

Do you have any pointers to evidence that OGL is open source compatible? Or a rationale for making this decision?

Branch docker_dev_via_runit: .bundler in source folder prevents container from finding gems

Bundler issue

Now is a non-issue

If for any reason you run

bundle install --path xxxxx
to install the gems in a particular location, it will create a .bundle directory in the app root, and as that is shared with the container, it will prevent the app from running in the container properly. This is not an issue if the normal
bundle install
command is used.

The original issue reported here is not an issue if the normal bundle command is used. # Testing in the container

Only the tests in spec/models, spec/lib, spec/routes can be run inside the container. To run all these tests, execute:

rake spec:docker

The integration tests can be run from the host machine against the instance running in the container. To do this, run:

env=docker rake spec:features

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.