Class: Jets::Booter

Inherits:
Object
  • Object
show all
Defined in:
lib/jets/booter.rb

Class Method Summary collapse

Class Method Details

.boot!(options = {}) ⇒ Object 



4
5
6
7
8
9
10
11
12
13
14
15
 
# File 'lib/jets/booter.rb', line 4

def boot!(options={})
  return if @booted

  redirect_output(options)
  confirm_jets_project!
  require_bundle_gems
  Jets::Dotenv.load!
  Jets.application # triggers application.setup! # autoload_paths, routes, etc
  setup_db

  @booted = true
end

.bundler_groups ⇒ Object 



100
101
102
 
# File 'lib/jets/booter.rb', line 100

def bundler_groups
  [:default, Jets.env.to_sym]
end

.confirm_jets_project! ⇒ Object

Cannot call this for the jets new



105
106
107
108
109
110
 
# File 'lib/jets/booter.rb', line 105

def confirm_jets_project!
  unless File.exist?("#{Jets.root}config/application.rb")
    puts "It does not look like you are running this command within a jets project.  Please confirm that you are in a jets project and try again.".colorize(:red)
    exit
  end
end

.flush_output ⇒ Object

Used in ruby_server.rb



43
44
45
46
47
48
 
# File 'lib/jets/booter.rb', line 43

def flush_output
  IO.write("/tmp/jets-output.log", $stdout.string)
  # Thanks: https://stackoverflow.com/questions/28445000/how-can-i-clear-a-stringio-instance
  $stdout.truncate(0)
  $stdout.rewind
end

.message ⇒ Object 



112
113
114
 
# File 'lib/jets/booter.rb', line 112

def message
  "Jets booting up in #{Jets.env.colorize(:green)} mode!"
end

.redirect_output(options = {}) ⇒ Object

TODO: Reconsider if we should redirect stdout to stderr globally for local request. Dont think we need to anymore now that we’re not using the old shim.

So for ‘false` and `jets call –local`, redirecting helps but we can also just go fix that jets call method. Though there might be a lot of other places where we might have to fix puts calls.



23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
 
# File 'lib/jets/booter.rb', line 23

def redirect_output(options={})
  $stdout.sync = true
  $stderr.sync = true
  if options[:stringio]
    # Set both $stdout and $stdout to a StringIO object as a buffer.
    # At the end of the request, write this buffer to the filesystem.
    # In the node shim, read it back and write it to AWS Lambda logs.
    #
    # This allows using `puts` to write to CloudWatch.
    $stdout = $stderr = StringIO.new # for ruby_server and AWS Lambda to capture log
  else
    # Printing to stdout can mangle up the response if we're piping the value to
    # jq. For exampe, `jets call --local .. | jq`
    # By redirecting stderr we can use jq.
    #
    $stdout = $stderr # jets call and local jets operation
  end
end

.require_bundle_gems ⇒ Object

require_bundle_gems called when environment boots up via Jets.boot. It also useful for when to loading Rake tasks in Jets::Commands::RakeTasks.load!

For example, some gems like webpacker that load rake tasks are specified with a git based source:

gem "webpacker", git: "https://github.com/tongueroo/webpacker.git"

This results in the user having to specific bundle exec in front of jets for those rake tasks to show up in jets help.

Instead, when the user is within the project folder, jets automatically requires bundler for the user. So the rake tasks show up when calling jets help.

When the user calls jets help from outside the project folder, bundler is not used and the load errors get rescued gracefully. This is done in Jets::Commands::RakeTasks.load! In the case when there are in another project with another Gemfile, the load errors will still be rescued.



70
71
72
73
74
75
76
77
 
# File 'lib/jets/booter.rb', line 70

def require_bundle_gems
  # NOTE: Dont think ENV['BUNDLE_GEMFILE'] is quite working right.  We still need
  # to be in the project directory.  Leaving logic in here for when it gets fix.
  if ENV['BUNDLE_GEMFILE'] || File.exist?("Gemfile")
    require "bundler/setup"
    Bundler.require(*bundler_groups)
  end
end

.setup_db ⇒ Object

Only connects connect to database for ActiveRecord and when config/database.yml exists. Dynomite handles connecting to the clients lazily.



82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
 
# File 'lib/jets/booter.rb', line 82

def setup_db
  return unless File.exist?("#{Jets.root}config/database.yml")

  db_configs = Jets.application.config.database
  # DatabaseTasks.database_configuration for db:create db:migrate tasks
  # Documented in DatabaseTasks that this is the right way to set it when
  # using ActiveRecord rake tasks outside of Rails.
  ActiveRecord::Tasks::DatabaseTasks.database_configuration = db_configs

  current_config = db_configs[Jets.env]
  if current_config.empty?
    abort("ERROR: config/database.yml exists but no environment section configured for #{Jets.env}")
  end
  # Using ActiveRecord rake tasks outside of Rails, so we need to set up the
  # db connection ourselves
  ActiveRecord::Base.establish_connection(current_config)
end