Taylor Boyko

For future readers, give this a shot: http://labs.wrprojects.com/how-to-use-google-tag-manager-with-rails-and-turbolinks/

@coderberry Must have been temporary; it's back up.

Second this. In fact, some EC2 instance types like `c5` and `m5` require that ENA support is available. Following these directions to add ENA support to the Graylog AMI image...

@bvirlet still seeing the issue but closed the issue because I didn't want to pull in any victims to my own potential memory issue. Are you seeing similar? I'll reopen...

Yes, seeing the same issue with redis 3.3.5 and MRI ruby 2.4.0 on macOS.

With your same gist, I'm seeing the following (commented out some output for clarity): after pop: 194,412 kilobytes after pop: 199,288 kilobytes after pop: 199,512 kilobytes after pop: 201,340 kilobytes...

Seeing the same issue with bundle not existing where the script expects it. I'm running the "64bit Amazon Linux 2014.03 v1.0.9 running Ruby 2.1 (Puma)" instance and bundle exists at...

Looks like the path issue is throughout the gem. This is tough for me to test (with a forked repo) because my experience with EB is that it just doesn't...

There seems to be an issue. Here's what I got after upgrading, deleting and recreating cron.config, and deploying: 2014-11-07 17:50:08,242 [DEBUG] Running command a_elasticbeanstalk_support_path 2014-11-07 17:50:08,242 [DEBUG] No test for...

``` 2014-11-10 17:33:12,126 [DEBUG] Command a_elasticbeanstalk_support_path output: containerfiles export EB_CONFIG_SUPPORT=/opt/elasticbeanstalk/containerfiles /tmp/update_appenv_include_eb_config_support.sh: line 8: /opt/elasticbeanstalk/support/envvars.d/appenv: No such file or directory 2014-11-10 17:33:12,126 [ERROR] Error encountered during build of prebuild_2_[removed]: Command a_elasticbeanstalk_support_path...