[foreman-dev] Best Advanced Practices for Puppet Packages to Foreman 1.7.1-0 Development Server Ubuntu
Following the instructions for a Development Install (without foreman-installer): https://theforeman.org/contribute.html I am wrapping my head around how to add Puppet Master and/or Agent to the Install. I have the foreman-puppet modules and rubygems as part of the install. Questions: 1) Can I just apt-get/yum install packages? 2) I think on Ubuntu 14.04, I need puppet 3, due to Ruby 2.4.2? ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-linux-gnu] 3) Can I use foreman-installer to ONLY install Puppet/Puppet Master? https://github.com/theforeman/foreman-installer 3) Can I use a puppetforge module to configure Forman-puppet 3/4/5? https://forge.puppet.com/theforeman/puppet/8.0.2/readme Please respond with the best recommendation (or combinations) above or another trick and/or tool. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[foreman-dev] Re: 1.17 Installation on Ubuntu 14.04 - Missing Dashboard Menu MouseOver Drop Downs && "Host Configuration Status widget loading".. Never Completes
On Wednesday, October 11, 2017 at 5:56:05 PM UTC-7, Lisa Kachold wrote:
>
> I have setup TheForeman 1.17.1-0 in a Development install on AWS.
>
> ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-linux-gnu] (gem/bundler
> errors using other versions)
> WEBrick 1.3.1
> ALL Ports open from Server to my IP
>
> I changed Rails to listen on all interfaces as:
>
> require 'rails/commands/server'
> module Rails
> class Server
> alias :default_options_bk :default_options
> def default_options
> default_options_bk.merge!(Host: '0.0.0.0')
> end
> endend
>
>
> Missing Dashboard Menu MouseOver Drop Downs && "Host Configuration Status
> widget loading".. Never Completes
>
> Output from Log:
>
> 00:36:43 rails.1 | started with pid 19240
>
> 00:36:43 webpack.1 | started with pid 19241
>
> 00:36:45 webpack.1 | { [Error: ENOENT: no such file or directory, open
> '.env'] errno: -2, code: 'ENOENT', syscall: 'open', path: '.env' }
>
> 00:36:45 webpack.1 | Project is running at http://localhost:3808/
>
> 00:36:45 webpack.1 | webpack output is served from /webpack/
>
> 00:36:51 rails.1 | DEPRECATION WARNING: `config.serve_static_files` is
> deprecated and will be removed in Rails 5.1.
>
> 00:36:51 rails.1 | Please use `config.public_file_server.enabled`
> instead.
>
> 00:36:51 rails.1 | (called from at
> /root/foreman/config/application.rb:218)
>
> 00:36:51 rails.1 | => Booting WEBrick
>
> 00:36:51 rails.1 | => Rails 5.0.6 application starting in development
> on http://0.0.0.0:5000
>
> 00:36:51 rails.1 | => Run `rails server -h` for more startup options
>
> 00:36:51 rails.1 | 2017-10-12T00:36:51 [app] [W] DEPRECATION WARNING:
> ActiveRecord::Base.raise_in_transactional_callbacks= is deprecated, has no
> effect and will be removed without replacement. (called from (required)> at /root/foreman/config/environment.rb:5)
>
> 00:36:55 rails.1 | The Apipie cache is turned off. Enable it and run
> apipie:cache rake task to speed up API calls.
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] WARNING: Pry will not
> work with foreman gem, use script/foreman-start-dev
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
> before_filter is deprecated and will be removed in Rails 5.1. Use
> before_action instead. (called from at
> /root/foreman/config/environment.rb:5)
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
> after_filter is deprecated and will be removed in Rails 5.1. Use
> after_action instead. (called from at
> /root/foreman/config/environment.rb:5)
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
> before_filter is deprecated and will be removed in Rails 5.1. Use
> before_action instead. (called from at
> /root/foreman/config/environment.rb:5)
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
> after_filter is deprecated and will be removed in Rails 5.1. Use
> after_action instead. (called from at
> /root/foreman/config/environment.rb:5)
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
> alias_method_chain is deprecated. Please, use Module#prepend instead. From
> module, you can access the original method using super. (called from (required)> at /root/foreman/config/environment.rb:5)
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
> Using a dynamic :controller segment in a route is deprecated and will be
> removed in Rails 5.2. (called from block in at
> /root/foreman/config/routes.rb:17)
>
> 00:36:59 rails.1 | [2017-10-12 00:36:59] INFO WEBrick 1.3.1
>
> 00:36:59 rails.1 | [2017-10-12 00:36:59] INFO ruby 2.4.2 (2017-09-14)
> [x86_64-linux-gnu]
>
> 00:36:59 rails.1 | [2017-10-12 00:36:59] INFO WEBrick::HTTPServer#start:
> pid=19242 port=5000
>
> 00:37:08 webpack.1 | Hash: 1d1afa88f456ce25e96c
>
> 00:37:08 webpack.1 | Version: webpack 3.6.0
>
> 00:37:08 webpack.1 | Time: 22521ms
>
> 00:37:08 webpack.1 | Asset Size Chunks
> Chunk
> Names
>
> 00:37:08 webpack.1 | bundle.js17.5 MB 0 [emitted] [big]
> bundle
>
> 00:37:08 webpack.1 | vendor.js75.7 kB 1 [emitted]
> vendor
>
> 00:37:08 webpack.1 |bundle.css81.7 kB 0 [emitted]
> bundle
>
> 00:37:08 webpack.1 | manifest.json 153 bytes [emitted]
>
> 00:37:08 webpack.1 | [55] ./webpack/assets/javascripts/foreman_tools.js
> 4.22 kB {0} [built]
>
> 00
Re: [foreman-dev] 1.17 Installation on Ubuntu 14.04 - Missing Dashboard Menu MouseOver Drop Downs && "Host Configuration Status widget loading".. Never Completes
On Thursday, October 12, 2017 at 9:55:24 AM UTC-7, Lisa Kachold wrote: > > SOLUTION: (thanks to ohadlevy)* > > Here's the Json version issue: Need to move to Json 1.8.6 from default > Json 2.0.4: > > gem list --local | grep json > > fog-*json* (1.0.2) > > *json* (1.8.6) > > multi_*json* (1.12.2) > > po_to_*json* (1.0.1) > > rack-*json*p (1.3.1) > > To remove a default gem and rebuild bundle: > > gem install json -v 2.0.4 > > gem uninstall json -v 2.0.4 > > bundle install > > locate json-2.0.4.gemspec > > mv json-2.0.4.gemspec /usr/local/src/oldgems/2.0.4/ > > bundle install > > Suggestion from ovahlevy that showed me the error output for Json. I was > using: bundle *exec* foreman start from > 'Setup Development Environment': > https://theforeman.org/contribute.html#SupportedRubyversions > > *BIND*=0.0.0.0 foreman start > > > Now webrick and rails for foreman listen on all ports! > > AND Javascript work GREAT! > > > On Thursday, October 12, 2017 at 8:50:04 AM UTC-7, Lisa Kachold wrote: >> >> ohadlevy - This will be the ultimate solution for Listening on all ports >> in 17.1 Development >> >> For "listening on all ports for Foreman 1.17.1" - starting up via: >> >> "BIND=0.0.0.0 foreman start" fails with Json errors for Bundler (which >> shines light on the Menu dropdown javascript issues). >> >> Strange that the tests didn't catch this? I will resolve the bundler >> version and ensure my Ruby stack. >> >> Thanks again! >> >> -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] 1.17 Installation on Ubuntu 14.04 - Missing Dashboard Menu MouseOver Drop Downs && "Host Configuration Status widget loading".. Never Completes
SOLUTION: (thanks to ohadlevy)* Here's the Json version issue: Need to move to Json 1.8.6 from default Json 2.0.4: gem list --local | grep json fog-*json* (1.0.2) *json* (1.8.6) multi_*json* (1.12.2) po_to_*json* (1.0.1) rack-*json*p (1.3.1) To remove a default gem and rebuild bundle: gem install json -v 2.0.4 gem uninstall json -v 2.0.4 bundle install locate json-2.0.4.gemspec mv json-2.0.4.gemspec /usr/local/src/oldgems/2.0.4/ bundle install Suggestion from ovahlevy that showed me the error output for Json. I was using: bundle *exec* foreman start from 'Setup Development Environment': https://theforeman.org/contribute.html#SupportedRubyversions *BIND*=0.0.0.0 foreman start Now webrick and rails for foreman listen on all ports! AND Javascript work GREAT! On Thursday, October 12, 2017 at 8:50:04 AM UTC-7, Lisa Kachold wrote: > > ohadlevy - This will be the ultimate solution for Listening on all ports > in 17.1 Development > > For "listening on all ports for Foreman 1.17.1" - starting up via: > > "BIND=0.0.0.0 foreman start" fails with Json errors for Bundler (which > shines light on the Menu dropdown javascript issues). > > Strange that the tests didn't catch this? I will resolve the bundler > version and ensure my Ruby stack. > > Thanks again! > > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] 1.17 Installation on Ubuntu 14.04 - Missing Dashboard Menu MouseOver Drop Downs && "Host Configuration Status widget loading".. Never Completes
pring/client/rails.rb:28:in
`call'
15:44:18 rails.1 | from
/var/lib/gems/2.4.0/gems/spring-2.0.2/lib/spring/client/command.rb:7:in
`call'
15:44:18 rails.1 | from
/var/lib/gems/2.4.0/gems/spring-2.0.2/lib/spring/client.rb:30:in `run'
15:44:18 rails.1 | from
/var/lib/gems/2.4.0/gems/spring-2.0.2/bin/spring:49:in `'
15:44:18 rails.1 | from
/var/lib/gems/2.4.0/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `load'
15:44:18 rails.1 | from
/var/lib/gems/2.4.0/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `'
15:44:18 rails.1 | from
/usr/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
15:44:18 rails.1 | from
/usr/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
15:44:18 rails.1 | from /root/foreman/bin/spring:13:in `'
15:44:18 rails.1 | from bin/rails:3:in `load'
15:44:18 rails.1 | from bin/rails:3:in `'
15:44:18 webpack.1 | { [Error: ENOENT: no such file or directory, open
'.env'] errno: -2, code: 'ENOENT', syscall: 'open', path: '.env' }
15:44:18 rails.1 | exited with code 1
15:44:18 system | sending SIGTERM to all processes
15:44:19 webpack.1 | terminated by SIGTERM
15:44:19 | Project is running at http://0.0.0.0:3808/
15:44:19 | webpack output is served from /webpack/
On Thursday, October 12, 2017 at 1:14:48 AM UTC-7, ohadlevy wrote:
>
>
>
> On Oct 12, 2017 3:56 AM, "Lisa Kachold" > wrote:
>
> I have setup TheForeman 1.17.1-0 in a Development install on AWS.
>
> ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-linux-gnu] (gem/bundler
> errors using other versions)
> WEBrick 1.3.1
> ALL Ports open from Server to my IP
>
> I changed Rails to listen on all interfaces as:
>
> No need for that at all, just type:
> BIND=0.0.0.0 foreman start
>
>
> require 'rails/commands/server'
> module Rails
> class Server
> alias :default_options_bk :default_options
> def default_options
> default_options_bk.merge!(Host: '0.0.0.0')
> end
> endend
>
>
> Missing Dashboard Menu MouseOver Drop Downs && "Host Configuration Status
> widget loading".. Never Completes
>
> Output from Log:
>
> 00:36:43 rails.1 | started with pid 19240
>
> 00:36:43 webpack.1 | started with pid 19241
>
> 00:36:45 webpack.1 | { [Error: ENOENT: no such file or directory, open
> '.env'] errno: -2, code: 'ENOENT', syscall: 'open', path: '.env' }
>
> 00:36:45 webpack.1 | Project is running at http://localhost:3808/
>
> 00:36:45 webpack.1 | webpack output is served from /webpack/
>
> 00:36:51 rails.1 | DEPRECATION WARNING: `config.serve_static_files` is
> deprecated and will be removed in Rails 5.1.
>
> 00:36:51 rails.1 | Please use `config.public_file_server.enabled`
> instead.
>
> 00:36:51 rails.1 | (called from at
> /root/foreman/config/application.rb:218)
>
> 00:36:51 rails.1 | => Booting WEBrick
>
> 00:36:51 rails.1 | => Rails 5.0.6 application starting in development
> on http://0.0.0.0:5000
>
> 00:36:51 rails.1 | => Run `rails server -h` for more startup options
>
> 00:36:51 rails.1 | 2017-10-12T00:36:51 [app] [W] DEPRECATION WARNING:
> ActiveRecord::Base.raise_in_transactional_callbacks= is deprecated, has no
> effect and will be removed without replacement. (called from (required)> at /root/foreman/config/environment.rb:5)
>
> 00:36:55 rails.1 | The Apipie cache is turned off. Enable it and run
> apipie:cache rake task to speed up API calls.
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] WARNING: Pry will not
> work with foreman gem, use script/foreman-start-dev
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
> before_filter is deprecated and will be removed in Rails 5.1. Use
> before_action instead. (called from at
> /root/foreman/config/environment.rb:5)
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
> after_filter is deprecated and will be removed in Rails 5.1. Use
> after_action instead. (called from at
> /root/foreman/config/environment.rb:5)
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
> before_filter is deprecated and will be removed in Rails 5.1. Use
> before_action instead. (called from at
> /root/foreman/config/environment.rb:5)
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
> after_filter is deprecated and will be removed in Rails 5.1. Use
> after_action instead. (called from at
> /root/foreman/config/environment.rb:5)
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEP
Re: [foreman-dev] 1.17 Installation on Ubuntu 14.04 - Missing Dashboard Menu MouseOver Drop Downs && "Host Configuration Status widget loading".. Never Completes
Timo,
Thanks for the suggestion; I will try it and let you know.
On Wednesday, October 11, 2017 at 11:32:06 PM UTC-7, Timo Goebel wrote:
>
> Hi Lisa,
>
> The Foreman dev setup basically needs two webservers running: One to serve
> the rails app via http and one to server webpacked javascript code.
>
> I suspect, that the connection to the latter does not work. The two
> webservers are started using foreman (not "our forman", but a process
> manager gem with the same name). You can take a look at the Procfile to see
> what's going on. You can customize the startup with environment variables.
>
>
> export RAILS_STARTUP='puma -w 3 -p 3000 --preload'
>
> export WEBPACK_OPTS='... more options ...'
>
> bundle exec foreman start
>
>
> Timo
> Am 12.10.17 um 02:56 schrieb Lisa Kachold:
>
> I have setup TheForeman 1.17.1-0 in a Development install on AWS.
>
> ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-linux-gnu] (gem/bundler
> errors using other versions)
> WEBrick 1.3.1
> ALL Ports open from Server to my IP
>
> I changed Rails to listen on all interfaces as:
>
> require 'rails/commands/server'
> module Rails
> class Server
> alias :default_options_bk :default_options
> def default_options
> default_options_bk.merge!(Host: '0.0.0.0')
> end
> endend
>
>
> Missing Dashboard Menu MouseOver Drop Downs && "Host Configuration Status
> widget loading".. Never Completes
>
> Output from Log:
>
> 00:36:43 rails.1 | started with pid 19240
>
> 00:36:43 webpack.1 | started with pid 19241
>
> 00:36:45 webpack.1 | { [Error: ENOENT: no such file or directory, open
> '.env'] errno: -2, code: 'ENOENT', syscall: 'open', path: '.env' }
>
> 00:36:45 webpack.1 | Project is running at http://localhost:3808/
>
> 00:36:45 webpack.1 | webpack output is served from /webpack/
>
> 00:36:51 rails.1 | DEPRECATION WARNING: `config.serve_static_files` is
> deprecated and will be removed in Rails 5.1.
>
> 00:36:51 rails.1 | Please use `config.public_file_server.enabled`
> instead.
>
> 00:36:51 rails.1 | (called from at
> /root/foreman/config/application.rb:218)
>
> 00:36:51 rails.1 | => Booting WEBrick
>
> 00:36:51 rails.1 | => Rails 5.0.6 application starting in development
> on http://0.0.0.0:5000
>
> 00:36:51 rails.1 | => Run `rails server -h` for more startup options
>
> 00:36:51 rails.1 | 2017-10-12T00:36:51 [app] [W] DEPRECATION WARNING:
> ActiveRecord::Base.raise_in_transactional_callbacks= is deprecated, has no
> effect and will be removed without replacement. (called from (required)> at /root/foreman/config/environment.rb:5)
>
> 00:36:55 rails.1 | The Apipie cache is turned off. Enable it and run
> apipie:cache rake task to speed up API calls.
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] WARNING: Pry will not
> work with foreman gem, use script/foreman-start-dev
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
> before_filter is deprecated and will be removed in Rails 5.1. Use
> before_action instead. (called from at
> /root/foreman/config/environment.rb:5)
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
> after_filter is deprecated and will be removed in Rails 5.1. Use
> after_action instead. (called from at
> /root/foreman/config/environment.rb:5)
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
> before_filter is deprecated and will be removed in Rails 5.1. Use
> before_action instead. (called from at
> /root/foreman/config/environment.rb:5)
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
> after_filter is deprecated and will be removed in Rails 5.1. Use
> after_action instead. (called from at
> /root/foreman/config/environment.rb:5)
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
> alias_method_chain is deprecated. Please, use Module#prepend instead. From
> module, you can access the original method using super. (called from (required)> at /root/foreman/config/environment.rb:5)
>
> 00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
> Using a dynamic :controller segment in a route is deprecated and will be
> removed in Rails 5.2. (called from block in at
> /root/foreman/config/routes.rb:17)
>
> 00:36:59 rails.1 | [2017-10-12 00:36:59] INFO WEBrick 1.3.1
>
> 00:36:59 rails.1 | [2017-10-12 00:36:59] INFO ruby 2.4.2 (2017-09-14)
> [x86_64-linux-gnu]
>
> 00:36:59 rails.1 | [2017-10-12 00:3
[foreman-dev] 1.17 Installation on Ubuntu 14.04 - Missing Dashboard Menu MouseOver Drop Downs && "Host Configuration Status widget loading".. Never Completes
I have setup TheForeman 1.17.1-0 in a Development install on AWS.
ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-linux-gnu] (gem/bundler
errors using other versions)
WEBrick 1.3.1
ALL Ports open from Server to my IP
I changed Rails to listen on all interfaces as:
require 'rails/commands/server'
module Rails
class Server
alias :default_options_bk :default_options
def default_options
default_options_bk.merge!(Host: '0.0.0.0')
end
endend
Missing Dashboard Menu MouseOver Drop Downs && "Host Configuration Status
widget loading".. Never Completes
Output from Log:
00:36:43 rails.1 | started with pid 19240
00:36:43 webpack.1 | started with pid 19241
00:36:45 webpack.1 | { [Error: ENOENT: no such file or directory, open
'.env'] errno: -2, code: 'ENOENT', syscall: 'open', path: '.env' }
00:36:45 webpack.1 | Project is running at http://localhost:3808/
00:36:45 webpack.1 | webpack output is served from /webpack/
00:36:51 rails.1 | DEPRECATION WARNING: `config.serve_static_files` is
deprecated and will be removed in Rails 5.1.
00:36:51 rails.1 | Please use `config.public_file_server.enabled` instead.
00:36:51 rails.1 | (called from at
/root/foreman/config/application.rb:218)
00:36:51 rails.1 | => Booting WEBrick
00:36:51 rails.1 | => Rails 5.0.6 application starting in development on
http://0.0.0.0:5000
00:36:51 rails.1 | => Run `rails server -h` for more startup options
00:36:51 rails.1 | 2017-10-12T00:36:51 [app] [W] DEPRECATION WARNING:
ActiveRecord::Base.raise_in_transactional_callbacks= is deprecated, has no
effect and will be removed without replacement. (called from at /root/foreman/config/environment.rb:5)
00:36:55 rails.1 | The Apipie cache is turned off. Enable it and run
apipie:cache rake task to speed up API calls.
00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] WARNING: Pry will not
work with foreman gem, use script/foreman-start-dev
00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
before_filter is deprecated and will be removed in Rails 5.1. Use
before_action instead. (called from at
/root/foreman/config/environment.rb:5)
00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
after_filter is deprecated and will be removed in Rails 5.1. Use
after_action instead. (called from at
/root/foreman/config/environment.rb:5)
00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
before_filter is deprecated and will be removed in Rails 5.1. Use
before_action instead. (called from at
/root/foreman/config/environment.rb:5)
00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
after_filter is deprecated and will be removed in Rails 5.1. Use
after_action instead. (called from at
/root/foreman/config/environment.rb:5)
00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
alias_method_chain is deprecated. Please, use Module#prepend instead. From
module, you can access the original method using super. (called from at /root/foreman/config/environment.rb:5)
00:36:58 rails.1 | 2017-10-12T00:36:58 [app] [W] DEPRECATION WARNING:
Using a dynamic :controller segment in a route is deprecated and will be
removed in Rails 5.2. (called from block in at
/root/foreman/config/routes.rb:17)
00:36:59 rails.1 | [2017-10-12 00:36:59] INFO WEBrick 1.3.1
00:36:59 rails.1 | [2017-10-12 00:36:59] INFO ruby 2.4.2 (2017-09-14)
[x86_64-linux-gnu]
00:36:59 rails.1 | [2017-10-12 00:36:59] INFO WEBrick::HTTPServer#start:
pid=19242 port=5000
00:37:08 webpack.1 | Hash: 1d1afa88f456ce25e96c
00:37:08 webpack.1 | Version: webpack 3.6.0
00:37:08 webpack.1 | Time: 22521ms
00:37:08 webpack.1 | Asset Size ChunksChunk
Names
00:37:08 webpack.1 | bundle.js17.5 MB 0 [emitted] [big]
bundle
00:37:08 webpack.1 | vendor.js75.7 kB 1 [emitted]
vendor
00:37:08 webpack.1 |bundle.css81.7 kB 0 [emitted]
bundle
00:37:08 webpack.1 | manifest.json 153 bytes [emitted]
00:37:08 webpack.1 | [55] ./webpack/assets/javascripts/foreman_tools.js
4.22 kB {0} [built]
00:37:08 webpack.1 | [322] multi
(webpack)-dev-server/client?http://localhost:3808 webpack/hot/dev-server
./webpack/assets/javascripts/bundle.js 52 bytes {0} [built]
00:37:08 webpack.1 | [323]
(webpack)-dev-server/client?http://localhost:3808 7.23 kB {0} [built]
00:37:08 webpack.1 | [371] (webpack)/hot/dev-server.js 1.61 kB {0} [built]
00:37:08 webpack.1 | [373] ./webpack/assets/javascripts/bundle.js 1.46 kB
{0} [built]
00:37:08 webpack.1 | [414]
./node_modules/expose-loader?jstz!./node_modules/jstz/index.js 88 bytes {0}
[built]
00:37:08 webpack.1 | [420]
./node_modules/expose-loader?JsDiff!./node_modules/diff/lib/index.js 94
bytes {0} [built]
00:37:08 webpack.1 | [431] ./webpack/assets/javascripts/bundle_flot.js 240
bytes {0} [built]
00:37:08 we
Re: [foreman-dev] Re: Bundler is unable to solve deps for fresh checkout
I had all these same issues in a 16.04 Ubuntu LTS (on AWS) with Ruby 2.1 and 6. There were a few hurdles after the upgrade/downgrade to 2.4 also. I still have a JavaScript issue, as the pull downs don't render, so I am rerunning tests. I have modified Foreman to listen on all ports. I have my history file from my install if you want to contact me directly. On Thursday, September 21, 2017 at 12:41:00 AM UTC-7, Lukas Zapletal wrote: > > I just upgraded, but I think putting Gemfile.lock (even an older one > from 1.14 stable branch) could work. Weird really. > > On Wed, Sep 20, 2017 at 6:57 PM, Daniel Lobato > wrote: > > http://ci.theforeman.org/view/Release%20pipeline/job/release_tarballs > > > > seems to have suffered from this today (Monday 1.15.4 tarballs were > built > > just fine) > > > > Did you find any other way to fix this? Switching to 2.4 could be an > option, > > probably > > putting a Gemfile.lock on every tagged release isn't a bad idea either. > > > > On Thursday, September 14, 2017 at 3:13:29 PM UTC+2, Lukas Zapletal > wrote: > >> > >> Hey, > >> > >> when I do fresh foreman clone with clean Ruby version (tried 2.0.0 and > >> 2.4.1), bundle install is not able to resolve dependencies and loops > >> forever. I am using latest stable bundler, tried also pre1 version. > >> > >> Can someone confirm and provide a workaround? I think copying > >> Gemfile.lock from someone else should do it. Can someone attach a > >> pastebin me one? I currently have my workstation down (CPU in RMA) and > >> got clean setup. > >> > >> If this is confirmed, it is quite an issue for newcomers. The second > >> command new developer is asked to execute fails hard. Any suggestions? > >> > >> LZ > >> > >> -- > >> Later, > >> Lukas @lzap Zapletal > > > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "foreman-dev" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to foreman-dev...@googlegroups.com . > > For more options, visit https://groups.google.com/d/optout. > > > > -- > Later, > Lukas @lzap Zapletal > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
