The .env file is outside of the web/ folder which should be your site’s webroot. Meaning anything outside of it isn’t accessible.
Hi, I still have a problem with my configuration. cap staging deploy finishes now but somehow the css grunt makes, is not in the release (roots/assets/css). And further strange - it is in the previous release. When I delete all releases to start from scratch, the deploy fails with a ‘directory doesn’t exist’. When I manually set the current symlink one release back everything is fine. What is going on?
deploy.rb https://gist.github.com/gabrielwolf/7aae3c4876831e15f4cb
I know that this isn’t payed support, but if I don’t get it completely running, I have to find another deployment method. My problem is, that I’m not familiar with ruby, so I can’t dig deeper to debug. Maybe a short Skype/Teamviewer session would solve the problem.
Please help me.
The hook you’re using is wrong. You have before 'deploy:updated', 'grunt', 'build'.
It should just be before 'deploy:updated', 'grunt'. That’s straight from the documentation from README and what I had in my Gist
Nothing changes when I do so. Same thing.
When I set set :grunt_tasks, 'deploy' like in the documentation, it fails with:
DEBUG[7acb4374] Warning: Task “deploy” not found. Use --force to continue.
Do I have to declare that deploy task myself? What should be in it?
That’s just an example. It’s not Roots specific. You had that part correct before. The grunt task for Roots is build.:
set :grunt_tasks, 'build'
edit: use this exact deploy.rb deploy.rb · GitHub
I think the problem is somewhere inside Bedrock/Capistrano. After a sucessfull deploy I manually changed the current symlink one release back. Then everything works like a charm.
Have a look: http://wolfzeit.net/~jibazee/wolfzeit.com/current/web/
Maybe a bug?
Are you talking about a different issue now? You’ve fixed the deploy errors? I’m confused what your current issue/bug is.
I don’t think this is a new thread. The deploy errors are fixed, but the deploy is still not working.
Scott could we make another attempt to solve the maze? Can you ask me a good question where I should dig for the wrong configuration or setting in my setup? When I deploy 2 times the penultimate deploy is fine. The last deploy lacks of the compiled css files. Ok, maybe there’s a workaround, but thats not poetry…
Maybe it’s due to this bug: https://github.com/roots/bedrock/pull/101 / https://github.com/roots/bedrock/issues/98