Git Product home page Git Product logo

opsworks-chef-cookbooks's People

Contributors

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

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

ta9n coderedhead jalopezcar awesome ivanmb kevindiamond eventx localvox evolution7 ldayan tonymet bmilleare antoniou martinfobian isubscribe douglaslinsmeyer tjlytle gora macgyver2028 iuriandreazza dizzyluo tonymporter firehawkdigital joindup warrantylife nicolindemann mrjonny2 mykehsd andreiroskach c4tech waldfelt carlosafonso bradhanebury digilentweb plentyguy asquel benlipp dealrinc teamsymfony albertleao hackable mozay-llc modpreneur vedranbrnjeticco codelab42 parthmonga alexgt9 publiux dereklea7 wikiclaims macanhhuy sh1n q-ode igostavro arametheus imranqaisar

opsworks-chef-cookbooks's Issues

Supervisor configuration file

What do I name the configuration file for supervisord in the root dir? I'm getting failed deployments due to me not setting it up correctly. Could you help me out?

Cheers

Composer recipes are triggered on non-php applications

I have a stack with a static frontend site app on one layer and a php backend app on another layer. Starting servers in the PHP layer fail because the composer recipe tries to run composer on the static app which does not exist. Example failure log is:

[2015-03-20T21:57:59+00:00] INFO: Running queued delayed notifications before re-raising exception
[2015-03-20T21:57:59+00:00] INFO: template[apache2.conf] sending run action to bash[logdir_existence_and_restart_apache2] (delayed)
[2015-03-20T21:57:59+00:00] INFO: Processing bash[logdir_existence_and_restart_apache2] action run (apache2::default line 46)
[2015-03-20T21:57:59+00:00] INFO: bash[logdir_existence_and_restart_apache2] ran successfully
[2015-03-20T21:57:59+00:00] INFO: bash[logdir_existence_and_restart_apache2] not queuing delayed action restart on service[apache2] (delayed), as it's already been queued
[2015-03-20T21:57:59+00:00] INFO: template[/etc/apache2/ports.conf] sending restart action to service[apache2] (delayed)
[2015-03-20T21:57:59+00:00] INFO: Processing service[apache2] action restart (apache2::default line 32)
[2015-03-20T21:58:04+00:00] INFO: service[apache2] restarted
[2015-03-20T21:58:04+00:00] INFO: execute[mv away default virtual host] sending reload action to service[apache2] (delayed)
[2015-03-20T21:58:04+00:00] INFO: Processing service[apache2] action reload (apache2::default line 32)
[2015-03-20T21:58:06+00:00] INFO: service[apache2] reloaded
[2015-03-20T21:58:06+00:00] ERROR: Running exception handlers
[2015-03-20T21:58:06+00:00] ERROR: Exception handlers complete
[2015-03-20T21:58:06+00:00] FATAL: Stacktrace dumped to /var/lib/aws/opsworks/cache.stage2/chef-stacktrace.out
[2015-03-20T21:58:06+00:00] ERROR: script[install_composer] (composer::install line 6) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of "bash"  "/tmp/chef-script20150320-4505-tax5n2" ----
STDOUT: 
STDERR: /opt/aws/opsworks/releases/20150304172806_33700020150304172806/vendor/bundle/ruby/2.0.0/gems/mixlib-shellout-1.4.0/lib/mixlib/shellout/unix.rb:147:in `chdir': No such file or directory - /srv/www/frontend/current (Errno::ENOENT)

I'm not well-versed enough in Chef to create a PR, but it seems that a guard on the recipes against application.application_type is all that is needed. Perhaps:

only_if { application[:application_type] == "php" }

trying to check out a private repo but failing

Hi there,

In order to check out my private repo, I need to ensure composer is using
~/.composer/auth.json

which looks like

gitauth.erb:
{
"github-oauth": {
"github.com": "<%= @gitauth %>"
}
}

install_gitauth.rb
where @gitauth is passed in a recipe:

template "/home/ubuntu/.composer/auth.json" do
source "gitauth.erb"
mode "0644"
variables(
:gitauth => node["deploy"]["backend"]["environment_variables"]["gitauth"]
)
end

And the :gitauth is specified in my custom stack json

however, this recipe doesnt seam to notice my auth.json file. What can I do?

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.