8000 'Configure puma' task fails as directory in {{ puma_config_path }} does not exist · Issue #24 · a-chernykh/railsbox · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

'Configure puma' task fails as directory in {{ puma_config_path }} does not exist #24

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.

Sign up for GitHub

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

Jump to bottom
Open
fonglh opened this issue May 22, 2015 · 1 comment
Open

'Configure puma' task fails as directory in {{ puma_config_path }} does not exist #24

fonglh opened this issue May 22, 2015 · 1 comment

Comments

@fonglh
Copy link
fonglh commented May 22, 2015

The directories don't seem to be created yet.
@ferrisoxide
Copy link

@fonglh Had a similar issue with unicorn when provisioning on remote sites. In my setup I have two sets of config files, a site.yml for Vagrant and and remote-site.yml for production/staging. The main difference is the remote-site.yml includes the deploy role, inserted just before webserver (see example below).

This at least ensures that the directories webserver needs are created - and I assume it's similar to what you are seeing for Puma, but does require a code deploy during the provision process. And it surfaces other issues.

I don't know Ansible very well, so this is all feels a bit hacky to me. If anyone with more knowledge can clue me in on what's the best approach that'd be appreciated.

- hosts: application
  handlers:
    - include: roles/delayed_job/handlers/main.yml
  roles:
    - base
    - { role: ruby, tags: ruby }
    - vim
    - deploy
    - webserver

Edit: My provision.sh for staging/production looks a bit like this:

ansible-playbook $@ -s -u root -i inventory ../ansible/remote-site.yml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ferrisoxide @fonglh
0