![]() ![]() ![]() ![]() # File 'lib/generators/rdcms/install_generator.rb', line 20 def install_test_env if yes? ( " Would you like to install a test Environment " ) gem ( " rspec-rails ", ' ~> 2.12.2 ', :group => " test " ) gem ( " annotate ", :group => " test " ) gem ( " ruby-graphviz ", :group => " test " ) gem ( " mysql2 ", :group => " test " ) gem ( " cucumber ", :group => " test " ) gem ( " cucumber-rails ", :group => " test ", :require => false ) gem ( " factory_girl ", :group => " test " ) gem ( " factory_girl_rails ", :group => " test " ) gem ( " database_cleaner ", :group => " test " ) gem ( " capybara ", :group => " test " ) gem ( " capybara-webkit ", :group => " test " ) gem ( " guard ", :group => " test " ) gem ( " guard-rspec ", :group => " test " ) gem ( " guard-cucumber ", :group => " test " ) gem ( " guard-livereload ", :group => " test " ) gem ( " rb-fsevent ", ' ~> 0.9. " git :commit => " -m 'Server configuration files added' " git :push => " origin master " system ( " cap deploy:create_gemset " ) system ( " cap deploy:setup " ) if yes? ( " Would you like to create remote database? " ) system ( " cap deploy:db:setup " ) end system ( " cap deploy " ) if yes? ( " Would you like to seed your remote db? " ) system ( " cap deploy:seed " ) end if yes? ( " Would you like to configure apache on your server? " ) system ( " cap deploy:apache_setup " ) end end end Because with watch /./ guard-livereload will send the local path to the browser, maybe guard-jekyll-plus is serving something different. Seems like an obvious productivity enhancement.# File 'lib/generators/rdcms/install_generator.rb', line 156 def install_capistrano if yes? ( " Would you like to configure git? " ) = ask ( " What is your git url? (bsp: ssh:// :requestdev/website.git) " ) git :init git :remote => " add origin # " system ( " bundle install " ) #Add Changes to git Still odd that this isn’t something Rails does out of the box. To connect the extension to Guard, click the LiveReload button in your browser extensions bar, and Guard should output Browser connected. ( browser extension, livereload.js) If you prefer going through a GUI, that option is available. ( Guard screen cast) You will also need a browser component to communicate with LiveReload. About Press Copyright Contact us Creators Advertise Developers Terms Privacy Policy & Safety How YouTube works Test new features NFL Sunday Ticket Press Copyright. I just realized that this line from the guide probably just means that the server need not be restarted for code changed to be picked up but that the browser will still need to be refreshed-which the gem listed above solves for. Sass+Compass, Guard, LiveReload Raw README.mdown This will enable Sass + Compass with LiveReload through Guard. Ruby 6. Thanks (in advance) to anyone willing to cure my ignorance here! Guard is a command line tool to easily handle events on file system modifications. Provides Chrome browser integration for the official LiveReload apps (Mac & Windows) and third-parties like guard-livereload and yeoman. ![]() In the development environment, Rails does not generally require you to restart the server changes you make in files will be automatically picked up by the server.īut the way I read that, no special gems or additional configuration is needed to get auto-reloads. Sign up to get free protection for your applications and to get access to all the features. I might also be mis-interpreting this from the “Getting Started with Rails” guide: When a browser load livereload.js, it connects to the LiveReloadX server using WebSocket. It's the best Markdown editor I've found (and I've tried a lot of them 1). You can use it via the command: bundle exec jekyll serve -livereload The Problem I use LightPaper to blog. I thought that Rails had hot code reloading straight out of the box. Guard::LiveReload automatically reloads your browser when 'view' files are modified. Type livereloadx path/to/dir on your command line, then LiveReloadX starts: watching path/to/dir running as a web server on port 35729 which serves livereload.js and acts as a WebSocket server. With the release of Jekyll 3.7 in January of 2018, LiveReload support was built into the core development server. Second, it’s been a very long time since I’ve done any Rails development work so I am likely not recalling things well. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |