Coder Social home page Coder Social logo

backgroundrb's People

Contributors

benwyrosdick avatar denisdefreyne avatar eyvoro avatar gnufied avatar jdwyah avatar miloops avatar nbibler avatar peteonrails avatar swindsor avatar

Stargazers

 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  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  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

backgroundrb's Issues

48 hours interval cron

I am trying to schedule job on 48 hours interval with "0 30 13 */2 * * *" option but job next executed on right time.

After some debugging I found cron executed for odd dates but not for even dates.

RAILS_ENV overridden from rake spec

This might be a bug tickled by the latest version of rspec, because I've been using rspec and backgroundrb for ages without any problems.

What I'm finding is if I run 'rake spec' from a rails project with the backgroundrb plugin and a backgroundrb.yml file which specifies ":environment: development", line 23 of bdrb_config.rb sets RAILS_ENV to 'development'. This means that rake spec clobbers the development database.

"No such file" issue and "Fix"

Seems like for some time now, backgroundrb version 1.1 has been plaguing certain users with a "no such file" error for log_worker when starting up the backgroundrb server. It hit me today, and the cause quickly became apparent. Somewhere around version 0.1.7, packet's code changed in some way that causes WORKER_ROOT or WORKER_LOAD_ENV paths with spaces in them to cause a no such file error. It has to do with the way packet constructs the command line for packet_worker_runner.

While it would probably make more sense for the maintainers of packet to fix this issue on their end, the fix in backgroundrb is really simple. Just add preceding and trailing " characters to WORKER_ROOT and WORKER_LOAD_ENV.

I'd submit a patch myself, but I'm really new to ruby and not sure if my fix would be considered the "right way" to go about working around the packet issue. I plan on mentioning this to the packet maintainers too.

rails 3 support

What is the status and plans for Rails 3 compatibility of backgroundrb?

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.