appyantra_admin 0.0.1

data/lib/appyantra_admin/version.rb

@@ -0,0 +1,3 @@
+module AppyantraAdmin
+  VERSION = "0.0.1"
+end

data/lib/generators/appyantra_admin/install/USAGE

@@ -0,0 +1,8 @@
+Description:
+    Explain the generator
+
+Example:
+    rails generate install Thing
+
+    This will create:
+        what/will/it/create

data/lib/generators/appyantra_admin/install/install_generator.rb

@@ -0,0 +1,34 @@
+class AppyantraAdmin::InstallGenerator < Rails::Generators::Base
+  source_root File.expand_path('../templates', __FILE__)
+
+  desc "Creates an AppyantraAdmin initializer and copies related files to your application."
+
+  def install
+    #copy_initializer
+    template "appyantra_admin.rb", "config/initializers/appyantra_admin.rb"
+    puts "Copying migrations..."
+    copy_migrations
+    add_appyantra_admin_routes
+    puts "After running the migrations, you need to do the following: "
+    puts "(1) Modify the initializer configurations --> config/initializers/appyantra_admin.rb"
+    puts "(2) Run Migrations"
+    puts "(3) Create an admin user by running:"
+    puts "rake appyantra_admin:create_admin email='EMAIL' first_name='FIRST_NAME' last_name='LAST_NAME'"
+    puts "(4) Create basic application settings by running:"
+    puts "rake appyantra_admin:setup_admin"
+    puts "(5) Delete public/index.html"
+  end
+
+  private
+
+  def add_appyantra_admin_routes
+    appyantra_admin_route = %Q{mount AppyantraAdmin::Engine => "/appyantra_admin"}
+    appyantra_admin_route << "\n  "
+    appyantra_admin_route << %Q{root :to => 'appyantra_admin/home#website'}
+    route appyantra_admin_route
+  end
+
+  def copy_migrations
+    %x[rake appyantra_admin:install:migrations]
+  end
+end

data/lib/generators/appyantra_admin/install/templates/appyantra_admin.rb

@@ -0,0 +1,28 @@
+require 'appyantra_admin/utils'
+# Use this hook to configure AppYantra Admin
+AppyantraAdmin.setup do |config|
+
+  include AppyantraAdmin::Utils
+
+  # specify the model names that can be managed as assets from the Admin dashboard
+  # e.g. config.assets = ['Product']
+  config.assets = []
+  # This phrase is used by the AppyantraAdmin::Crypto library for the AES-256 key
+  AppyantraAdmin::Crypto.key_phrase = 'Dont forget to seal all the doors with salt!'
+
+
+  # By default layouts list is made from haml/erb files in views/layouts
+  # You can over-ride this by specifying your list
+  # e.g. config.page_layouts ['layout1', 'layout2', 'nested_folder/layout3']
+  config.page_layouts = list_page_layouts
+
+  Devise.setup do |config|
+    # ==> Mailer Configuration
+    # Configure the e-mail address which will be shown in Devise::Mailer,
+    # note that it will be overwritten if you use your own mailer class with default "from" parameter.
+    config.mailer_sender = "admin.email@yourdomain.com"
+  end
+
+  # set the html format used for HTML 5 use :html5
+  Haml::Template.options[:format] = :xhtml
+end

data/lib/tasks/appyantra_admin_tasks.rake

@@ -0,0 +1,47 @@
+namespace :appyantra_admin do
+
+  desc "Creates an admin user"
+  task :create_admin => :environment do
+    user_params = { first_name: ENV['first_name'], last_name: ENV['last_name'], email: ENV['email'] }
+    admin_user = Admin.new(user_params)
+    puts "Enter password"
+    admin_user.password = $stdin.gets.chomp
+    puts "Confirm password"
+    admin_user.password_confirmation = $stdin.gets.chomp
+    admin_user.save(:validate => false)
+  end
+
+  desc "Creates some basic settings"
+  task :setup_admin => :environment do
+    website_url = Link.create(name: 'website_url', text: 'Visit Website',
+                              href: '#', title: 'Website URL')
+    site_name = ShortText.create(name: 'site_name', value: 'Acme Company')
+    copyright_year = ShortText.create(name: 'copyright_year', value: Time.now.year.to_s)
+    puts 'Creating Website URL setting...'
+    AdminSetting.create_from_entity(website_url.name, website_url)
+    puts 'Creating Site Name setting...'
+    AdminSetting.create_from_entity(site_name.name, site_name)
+    puts 'Creating Copyright Year setting...'
+    AdminSetting.create_from_entity(copyright_year.name, copyright_year)
+  end
+
+  desc "Adds a setting for Rich Text Editor and defaults it to CKEditor"
+  task :use_rich_text_editor => :environment do
+    rich_text_editor = ShortText.create(name: 'rich_text_editor', value: 'ckeditor')
+    AdminSetting.create_from_entity(rich_text_editor.name, rich_text_editor)
+  end
+
+  desc "Create settings for Google Analytics"
+  task :setup_google_analytics => :environment do
+    unless AdminSetting.exists?(group: 'Google Analytics')
+      tracking_code = ShortText.create(name: 'tracking_code', value: ENV['tracking_code'])
+      domain = ShortText.create(name: 'domain', value: ENV['domain'])
+      puts 'Creating Tracking Code setting...'
+      AdminSetting.create_from_entity(tracking_code.name, tracking_code, 'Google Analytics')
+      puts 'Creating Domain Name setting...'
+      AdminSetting.create_from_entity(domain.name, domain, 'Google Analytics')
+      # clears all the cached pages
+      FileUtils.rm_rf Rails.root.join("public/pages")
+    end
+  end
+end

data/script/rails

@@ -0,0 +1,6 @@
+#!/usr/bin/env ruby
+#!/usr/bin/env ruby
+# This command will automatically be run when you run "rails" with Rails 3 gems installed from the root of your application.
+
+ENGINE_PATH = File.expand_path('../..',  __FILE__)
+load File.expand_path('../../test/dummy/script/rails',  __FILE__)

data/test/dummy/.gitignore

@@ -0,0 +1,36 @@
+# See http://help.github.com/ignore-files/ for more about ignoring files.
+#
+# If you find yourself ignoring temporary files generated by your text editor
+# or operating system, you probably want to add a global ignore instead:
+#   git config --global core.excludesfile ~/.gitignore_global
+
+app/assets/javascripts/ckeditor
+
+# Ignore bundler config
+/.bundle
+
+# Ignore all logfiles and tempfiles.
+/log/*.log
+/tmp
+config/database.yml
+db/schema.rb
+db/migrate/*_create_links.rb
+db/migrate/*_create_admin_settings.rb
+db/migrate/*_add_name_to_admins.rb
+db/migrate/*_create_texts.rb
+db/migrate/*_devise_create_admins.rb
+db/migrate/*_devise_create_users.rb
+db/migrate/*_add_name_to_users.rb
+db/migrate/*_create_pages.rb
+db/migrate/*_add_group_to_admin_settings.rb
+db/migrate/*_create_encrypted_texts.rb
+db/migrate/*_create_short_texts.rb
+db/migrate/*_add_seo_to_pages.rb
+db/migrate/*_create_keywords.rb
+db/migrate/*_create_activity_feeds.rb
+
+# will be copied during install
+config/initializers/appyantra_admin.rb
+
+# pages
+public/*/*

data/test/dummy/.rspec

@@ -0,0 +1 @@
+--colour

data/test/dummy/Gemfile

@@ -0,0 +1,43 @@
+source 'http://rubygems.org'
+
+gem 'rails', '3.1.3'
+
+# Bundle edge Rails instead:
+# gem 'rails',     :git => 'git://github.com/rails/rails.git'
+
+group :test, :development do
+  gem 'pg'
+  gem 'appyantra_admin', path: '../../'
+  gem "rspec-rails", "~> 2.8.1"
+  gem "capybara" , "~> 1.1.2"
+  gem "factory_girl_rails"
+  gem "guard-rspec"
+  gem "database_cleaner"
+end
+
+# Gems used only for assets and not required
+# in production environments by default.
+group :assets do
+  gem 'sass-rails',   '~> 3.1.5'
+  gem 'coffee-rails', '~> 3.1.1'
+  gem 'uglifier', '>= 1.0.3'
+end
+
+gem 'jquery-rails'
+
+# To use ActiveModel has_secure_password
+# gem 'bcrypt-ruby', '~> 3.0.0'
+
+# Use unicorn as the web server
+# gem 'unicorn'
+
+# Deploy with Capistrano
+# gem 'capistrano'
+
+# To use debugger
+# gem 'ruby-debug19', :require => 'ruby-debug'
+
+group :test do
+  # Pretty printed test output
+  gem 'turn', '~> 0.8.3', :require => false
+end

data/test/dummy/Guardfile

@@ -0,0 +1,19 @@
+# A sample Guardfile
+# More info at https://github.com/guard/guard#readme
+
+guard 'rspec', :version => 2 do
+  watch(%r{^spec/.+_spec\.rb$})
+  #watch(%r{^lib/(.+)\.rb$})     { |m| "spec/lib/#{m[1]}_spec.rb" }
+  #watch('spec/spec_helper.rb')  { "spec" }
+  #
+  ## Rails example
+  #watch(%r{^app/(.+)\.rb$})                           { |m| "spec/#{m[1]}_spec.rb" }
+  #watch(%r{^app/(.*)(\.erb|\.haml)$})                 { |m| "spec/#{m[1]}#{m[2]}_spec.rb" }
+  #watch(%r{^app/controllers/(.+)_(controller)\.rb$})  { |m| ["spec/routing/#{m[1]}_routing_spec.rb", "spec/#{m[2]}s/#{m[1]}_#{m[2]}_spec.rb", "spec/acceptance/#{m[1]}_spec.rb"] }
+  #watch(%r{^spec/support/(.+)\.rb$})                  { "spec" }
+  #watch('config/routes.rb')                           { "spec/routing" }
+  #watch('app/controllers/application_controller.rb')  { "spec/controllers" }
+  ## Capybara request specs
+  #watch(%r{^app/views/(.+)/.*\.(erb|haml)$})          { |m| "spec/requests/#{m[1]}_spec.rb" }
+end
+

data/test/dummy/README

@@ -0,0 +1,261 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+
+This pattern splits the view (also called the presentation) into "dumb"
+templates that are primarily responsible for inserting pre-built data in between
+HTML tags. The model contains the "smart" domain objects (such as Account,
+Product, Person, Post) that holds all the business logic and knows how to
+persist themselves to a database. The controller handles the incoming requests
+(such as Save New Account, Update Product, Show Post) by manipulating the model
+and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails. You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting Started
+
+1. At the command prompt, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
+* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong. Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files. Have "tail -f" commands
+running on the server.log and development.log. Rails will automatically display
+debugging and runtime information to these files. Debugging info will also be
+shown in the browser on requests from 127.0.0.1.
+
+You can also log your own messages directly into the log file from your code
+using the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
+several books available online as well:
+
+* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two books will bring you up to speed on the Ruby language and also on
+programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your
+Mongrel or WEBrick server with --debugger. This means that you can break out of
+execution at any point in the code, investigate and change the model, and then,
+resume execution! You need to install ruby-debug to run the server in debugging
+mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.all
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8
+          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
+       #<Post:0x14a6620
+          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better, you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you can enter "cont".
+
+
+== Console
+
+The console is a Ruby shell, which allows you to interact with your
+application's domain model. Here you'll have all parts of the application
+configured, just like it is when the application is running. You can inspect
+domain models, change values, and save to the database. Starting the script
+without arguments will launch it in the development environment.
+
+To start the console, run <tt>rails console</tt> from the application
+directory.
+
+Options:
+
+* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
+  made to the database.
+* Passing an environment name as an argument will load the corresponding
+  environment. Example: <tt>rails console production</tt>.
+
+To reload your controllers and models after launching the console run
+<tt>reload!</tt>
+
+More information about irb can be found at:
+link:http://www.rubycentral.org/pickaxe/irb.html
+
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>rails
+dbconsole</tt>. You would be connected to the database with the credentials
+defined in database.yml. Starting the script without arguments will connect you
+to the development database. Passing an argument will connect you to a different
+database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
+PostgreSQL and SQLite 3.
+
+== Description of Contents
+
+The default directory structure of a generated Ruby on Rails application:
+
+  |-- app
+  |   |-- assets
+  |       |-- images
+  |       |-- javascripts
+  |       `-- stylesheets
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   |-- cache
+  |   |-- pids
+  |   |-- sessions
+  |   `-- sockets
+  `-- vendor
+      |-- assets
+          `-- stylesheets
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/assets
+  Contains subdirectories for images, stylesheets, and JavaScript files.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from
+  ApplicationController which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb. Models descend from
+  ActiveRecord::Base by default.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use
+  eRuby syntax by default.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the
+  common header/footer method of wrapping views. In your views, define a layout
+  using the <tt>layout :default</tt> and create a file named default.html.erb.
+  Inside default.html.erb, call <% yield %> to render the view using this
+  layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are
+  generated for you automatically when using generators for controllers.
+  Helpers can be used to wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database,
+  and other dependencies.
+
+db
+  Contains the database schema in schema.rb. db/migrate contains all the
+  sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when
+  generated using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that
+  doesn't belong under controllers, models, or helpers. This directory is in
+  the load path.
+
+public
+  The directory available for the web server. Also contains the dispatchers and the
+  default HTML files. This should be set as the DOCUMENT_ROOT of your web
+  server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the rails generate
+  command, template test files will be generated for you and placed in this
+  directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins
+  subdirectory. If the app has frozen rails, those gems also go here, under
+  vendor/rails/. This directory is in the load path.