Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    BergBenji
    @BergBenji
    HI, i tryied your last code snipped. Result: > c.workspace.changeset.each { |c| puts c.path }; nil
    => nil
    Scott Nelson
    @scttnlsn
    @BergBenji Hey, you around?
    Scott Nelson
    @scttnlsn
    @BergBenji I have something else for you to try: https://github.com/scttnlsn/dandelion/issues/117#issuecomment-72907010
    Thanks for helping debug this.
    BergBenji
    @BergBenji
    Hey, Sorry but i were on the highway :D No problem. Hope we get it fixed because i like dandelion.
    Bob Rockefeller
    @bobrocke
    user/plugins/materializer is a submodule
    Scott Nelson
    @scttnlsn
    Ahh, that's the issue.
    Bob Rockefeller
    @bobrocke
    An issue I can fix?
    Scott Nelson
    @scttnlsn
    I have an issue open to support submodules but haven't had the time or need to implement it: scttnlsn/dandelion#74
    Here's what I would recommend...
    Add the submodule directories to the exclude list in your dandelion config
    And also add them to the additional files list
    The downside here is that they will be redeployed each time instead of only when they are changed
    Will that work for you?
    Bob Rockefeller
    @bobrocke
    I can try it. I know about the exclude: list, but what is the additional files list?
    Scott Nelson
    @scttnlsn
    Check out the example config here: https://github.com/scttnlsn/dandelion#config
    It's a list of files that will be deployed each time you run dandelion deploy (usually this is used for unversioned config files, etc.)
    Bob Rockefeller
    @bobrocke
    So:
    exclude:
        - .gitignore
        - dandelion.yml
        - deployment-config.json
        - user/plugins/materializer
    
    additional:
        - user/plugins/materializer
    Scott Nelson
    @scttnlsn
    Another option is to just deploy the submodule separately
    Bob Rockefeller
    @bobrocke

    Actually:

    exclude:
        - .gitignore
        - dandelion.yml
        - deployment-config.json
        - user/plugins/materializer
        - user/themes/materialize
    
    additional:
        - user/plugins/materializer
        - user/themes/materialize

    Correct?

    Scott Nelson
    @scttnlsn
    Yeah, does that work?
    Bob Rockefeller
    @bobrocke
    I’ll try it...
    Scott Nelson
    @scttnlsn
    Not sure if I've every tried directories in the additional list
    Bob Rockefeller
    @bobrocke
    No joy. Same error:
    Writing file:  user/plugins/materializer
    /Users/bob/.rvm/gems/ruby-2.0.0-p247@rails3/gems/rugged-0.21.4/lib/rugged/repository.rb:99:in `lookup': Object not found - failed to find pack entry (24fc42875a5cac592aac66b85686c97e91d32216) (Rugged::OdbError)
    Scott Nelson
    @scttnlsn
    Hmmm
    Well, I guess I would recommend deploying them separately for now then I guess
    Try removing the additional list and deploying to make sure that will work
    Bob Rockefeller
    @bobrocke
    OK…
    Scott Nelson
    @scttnlsn
    Keep the submodules excluded
    Bob Rockefeller
    @bobrocke
    Same error!
    exclude:
        - .gitignore
        - dandelion.yml
        - deployment-config.json
        - user/plugins/materializer
        - user/themes/materialize
    Scott Nelson
    @scttnlsn
    Okay, sorry about that. I'll have to look into it further.
    Bob Rockefeller
    @bobrocke
    OK, thanks for the help here. I’ll need to vote up the submodule issue! :)
    Scott Nelson
    @scttnlsn
    Yeah, you've giving me some motivation to work on it!
    *you're giving
    Bob Rockefeller
    @bobrocke
    OK. Maybe you’ll have some spare minutes soon.
    Bob Rockefeller
    @bobrocke
    Looking better for submodule support?
    Bob Rockefeller
    @bobrocke
    Submodule support soon?