Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Movefile case sensitivity on *nix systems #483

Open
rbndelrio opened this issue Jul 4, 2018 · 1 comment
Open

Movefile case sensitivity on *nix systems #483

rbndelrio opened this issue Jul 4, 2018 · 1 comment
Assignees
Labels

Comments

@rbndelrio
Copy link
Contributor

I was trying out docker-wordmove earlier and came across a few roadblocks along the way (I'll make an issue for the others in that repo). I have a docker-compose.yml that looks largely the same as that Medium article about simonbland/docker-wordmove:

...
  wordmove:
    image: welaika/wordmove
    depends_on:
      - wordpress
    restart: always
    working_dir: /var/www/html/
    volumes:
      - ./wp:/var/www/html
      - ./themes:/var/www/html/wp-content/themes/
      - ./config/.env:/var/www/html/.env
      - ./config/movefile.yml:/var/www/html/movefile.yml
      - ~/.ssh:/home/wordmove/.ssh:ro
    tty: true
...

When trying to pull, I got an error (undefined method 'deep_symbolize_keys!' for nil:NilClass (NoMethodError)) that was directed at line 26 of movefile.rb.

Looking at the fetch method
, I'm pretty sure it has to do with how the File and Dir classes treat case-sensitivity on *nix filesystems as it was able to find my movefile but found evaluated to /var/www/html/Movefile.yml

I was able to skip this roadblock by amending docker-compose.yml:

volumes:
  - ./config/movefile.yml:/var/www/html/Movefile

Again, Ruby (and i/o stuff like this) is a little out of my spectrum, but my Google-fu suggests File::FNM_CASEFOLD can make Dir.glob calls case-insensitive, so lines 12-16 could be reworked to utilize that?

@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants