keppler 2.0.2 → 2.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA256:
-  metadata.gz: b1405a8b35554ae46a0b240661cb61c4e2a3f01239c84efd987c787b108f90db
-  data.tar.gz: 3cb9e4bd862050e898b16bb313de928066bc25b236b0f478e8d98be2f1870749
+SHA1:
+  metadata.gz: 1a636d8dffac8ec8919a04334a85e8df3eecc6a4
+  data.tar.gz: a403f9a8e77b5f33bee8d49ae8231c035a7f61c1
 SHA512:
-  metadata.gz: a53897d30c1cea1f9e52c1e4f3d796a7d052b9aa4747f775dbf2fb25baf61d46a2beb317572105697ae324ac7bb939770773ab11c5d5a5c5f2508ad8915f4720
-  data.tar.gz: 4b1ab2216b8bfed6772cc936d2588ad4be5afc5026385dd21d5694607d46b227abd0a00da24199f643f04a384275c03b1129058e2f6515b8ead2f151e9ffe091
+  metadata.gz: '08b55b457ca65e64c6180c02296cd375283053b8bc787da1676d44a8b3258a05ff0fe7b9f1295dd17e9bb104de35e8b8f9a6748bd272730464c32add437c98ae'
+  data.tar.gz: 6a48e5cf9da493d080bb9e5923868ee39423d67237a463caedd46ab2e76a4c5554a6d5c6539b836d4a511612d42dc7fe3b3d2e8c73668507e9dc06cc382433b1

data/.gitignore

@@ -0,0 +1,8 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at luis.prz7@gmail.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile.lock

@@ -0,0 +1,26 @@
+PATH
+  remote: .
+  specs:
+    keppler (2.0.3)
+      httparty
+      thor
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    httparty (0.16.2)
+      multi_xml (>= 0.5.2)
+    multi_xml (0.6.0)
+    rake (10.5.0)
+    thor (0.20.0)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler (~> 1.16)
+  keppler!
+  rake (~> 10.0)
+
+BUNDLED WITH
+   1.16.1

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2018 Luis Perez
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -1,41 +1,112 @@
-# Keppler 2.0.2
+### KEPPLER
 
-Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/keppler`. To experiment with that code, run `bin/console` for an interactive prompt.
+Keppler Admin es un CMS con un entorno de desarrollo que cuenta con una base de gemas ya integradas, de tal forma que acelerará el desarrollo de aplicaciones de vanguardia bajo la plataforma de Ruby on Rails.
 
-TODO: Delete this and the text above, and describe your gem
 
-## Installation
+### Características
 
-Step 1
+* Base de datos por defecto PostreSQL
+* Integración para autenticación de usuarios con [Devise](https://github.com/plataformatec/devise)
+* Integración para roles de usuarios con [Rolify](https://github.com/RolifyCommunity/rolify)
+* Integración para autorizaciones con [Pundit](https://github.com/varvet/pundit)
+* Inegración para el manejo de de paginación con [Kaminari](https://github.com/amatsuda/kaminari)
+* Integración para helpers de formularios con [SimpleForm](https://github.com/RolifyCommunity/rolify)
+* Integración para búsquedas full-text con [Ransack](https://github.com/activerecord-hackery/ransack)
+* Integración con framework fronte-end para el administrativo con [AdminLTE](https://adminlte.io/)
+* Integración con framework javascript [VueJS](https://vuejs.org/)
+* Integración sitemap dinamicos con [Sitemap Generator](https://github.com/kjvarga/sitemap_generator)
 
-    gem install keppler
+#### Instalación
 
-Step 2
-	
-	sh ~/.rvm/gems/ruby-2.5.1/gems/keppler-2.0.2/installer/run.sh
+Una de las novedades de Keppler Admin v2.0 es el lanzamiento de una gema que nos
+permite el fácil y rápido manejo de las funcionalidades del CMS. Para instalarlo
+necesitamos ejecutar el siguiente comando desde la consola:
 
-Step 3
+`gem install keppler`
 
-	source ~/.keppler/scripts/bin.sh
+#### Lista de comandos
 
-## Usage
+Para verificar que está instalada la gema correctamente y ver una lista de los posibles comandos
+que podemos utilizar, ejecutamos:
 
-TODO: Write usage instructions here
+`keppler`
 
-## Development
+#### Nuevo Proyecto
 
-After checking out the repo, run `bin/setup` to install dependencies. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+Para crear un nuevo proyecto en Ruby on Rails con Keppler Admin, podemos ejecutar:
 
-To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+`keppler new NuevoProyecto`
 
-## Contributing
+#### Creación del archivo secrets.yml
 
-Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/keppler. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+Si detienes el proceso a la mitad o aún no tienes configurado un archivo `secrets.yml` con la configuración de
+la base de datos y otros inicializadores, puedes crear la base de datos ejecutando:
 
-## License
+`keppler db_conf`
 
-The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+#### Instalación de las dependencias
 
-## Code of Conduct
+Antes de poder iniciar con un proyecto nuevo, primero debemos instalar todas las gemas
+instanciadas en el `Gemfile`, ubicado en la raíz del proyecto, con el comando:
 
-Everyone interacting in the Keppler project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/keppler/blob/master/CODE_OF_CONDUCT.md).
+`keppler dep`
+
+### Keppler Scaffolds
+
+Keppler ofrece la posibilidad de realizar tareas de scaffolds totalmente
+configurados para adaptarse al administrativo. Para crear un nuevo
+módulo sólo debes llamar al siguiente comando desde la consola:
+
+`keppler add module ModuleName attribute:type`
+
+Por ejemplo, crearemos un scaffold de productos con diversos campos y tipos de datos:
+
+`keppler add module Product title:string description:text quantity:integer price:float arrival_date:date arrival_time:time available:boolean user:references`
+
+Luego debemos migrar la tabla a la base de datos con:
+
+`keppler migrate`
+
+Si luego deseamos borrar, crear, migrar y llenar la base de datos desde cero,
+podemos realizarlo ejecutando el comando:
+
+`keppler reset`
+
+Por último, si todo ha sido ejecutado debida y correctamente, podemos iniciar
+el proyecto ejecutando en la consola:
+
+`keppler server`
+
+### SimpleForm con Bootstrap
+
+Se ofrece una integración por defecto entre SimpleForm y Bootstrap, usted tiene la posibilidad de cambiar su funcionalidad en `config/initializers/simple_form_bootstrap.rb`
+
+Aqui algunos ejemplos para la creación de inputs:
+
+```ruby
+# Inputs de tipo string o textarea
+= f.input :name
+
+# Inputs de tipo CKEditor
+= f.input :description, as: :ckeditor, input_html: { ckeditor: { toolbar: 'mini'} }
+
+# Inputs de tipo boolean
+= f.input :public, as: :keppler_boolean
+
+# Inputs de tipo file
+= f.input :image, as: :keppler_file
+
+# Inputs de tipo select
+= f.input :role_ids, collection: Role.all, label: false, include_blank: "Seleccione un rol"
+
+# Inputs de tipo radio buttons
+= f.collection_radio_buttons :option, [['vegan', 'vegan'] ,['vegetarian', 'vegetarian']], :first, :last
+
+# Inputs de tipo check_boxes
+= f.collection_check_boxes :options, [['vegan', 'vegan'] ,['vegetarian', 'vegetarian']], :first, :last
+
+# Inputs de tipo date
+= f.input :date, input_html: { class: 'datepicker' }
+```
+
+**Nota:** *Puede revisar la documentación de [AdminLTE](https://adminlte.io) para agregar nuevas integraciones para sus formularios a través de los [Wrappers](https://github.com/plataformatec/simple_form/wiki/Custom-Wrappers) de simpleform.*

data/Rakefile

@@ -1,2 +1,8 @@
 require "bundler/gem_tasks"
 task :default => [:spec]
+
+namespace :gem do
+  task :build do
+    system "rake build && rake install"
+  end
+end

data/bin/keppler

@@ -1,5 +1,9 @@
-#!/usr/bin/env ruby 
+#!/usr/bin/env ruby
 
 require 'keppler'
 
-Keppler::Generate.start( ARGV )
+Keppler::Generate.start( ARGV )
+
+
+
+

data/bin/setup

@@ -4,4 +4,5 @@ IFS=$'\n\t'
 set -vx
 
 bundle install
-# Do any other automated setup that you need to do here
+# Do any other automated setup that you need to do here
+

data/exe/keppler

@@ -0,0 +1,6 @@
+#!/usr/bin/env ruby
+
+require 'keppler/cli'
+
+Keppler::Cli.start
+

data/installer/core/.gitignore

@@ -0,0 +1,87 @@
+#----------------------------------------------------------------------------
+# Ignore these files when commiting to a git repository.
+#
+# See http://help.github.com/ignore-files/ for more about ignoring files.
+#
+# The original version of this file is found here:
+# https://github.com/RailsApps/rails-composer/blob/master/files/gitignore.txt
+#
+# Corrections? Improvements? Create a GitHub issue:
+# http://github.com/RailsApps/rails-composer/issues
+#----------------------------------------------------------------------------
+
+# bundler state
+/.bundle
+/vendor/bundle/
+/vendor/ruby/
+/public/uploads
+# minimal Rails specific artifacts
+db/*.sqlite3
+db/schema.rb
+/db/*.sqlite3-journal
+/log/*
+/tmp/*
+Gemfile.lock
+# various artifacts
+**.war
+*.rbc
+*.sassc
+.redcar/
+.sass-cache
+.byebug_history
+/.byebug_history
+/app/assets/javascripts/guard_javascript/*
+/app/assets/stylesheets/frontend/native_stylesheets/guard_stylesheets/*
+/config/application.yml
+/config/secrets.yml
+/config/secrets.yml.example
+/coverage.data
+/coverage/
+/db/*.javadb/
+/db/*.sqlite3
+/db/schema.rb
+/doc/api/
+/doc/app/
+/doc/features.html
+/doc/specs.html
+/public/cache
+/public/uploads
+/public/stylesheets/compiled
+/public/system/*
+/spec/tmp/*
+/cache
+/capybara*
+/capybara-*.html
+/gems
+/specifications
+rerun.txt
+pickle-email-*.html
+.zeus.sock
+
+# 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
+#
+# Here are some files you may want to ignore globally:
+
+# scm revert files
+**.orig
+
+# Mac finder artifacts
+.DS_Store
+
+# Netbeans project directory
+/nbproject/
+
+# RubyMine project files
+.idea
+
+# Textmate project files
+/*.tmproj
+
+# vim artifacts
+**.swp
+
+# Environment files that may contain sensitive data
+.env
+.powenv

data/installer/core/.ruby-version

@@ -0,0 +1 @@
+2.5.1

data/installer/core/Gemfile

@@ -8,7 +8,7 @@ gem 'rails', '5.2.0'
 gem 'ckeditor', '4.2.4'
 gem 'jquery-rails', '4.3' # jQuery library
 gem 'nprogress-rails', '0.2.0.2' #
-gem 'remotipart', '1.4.0'
+gem 'remotipart', '1.3.0'
 gem 'vuejs-rails', '2.5.13' # VueJS library
 
 # Server
@@ -42,7 +42,7 @@ gem 'sitemap_generator', '6.0.1'
 gem 'public_activity', '1.5.0'
 
 # AdminLTE
-source 'https://rails-assets.org/' do
+source 'http://insecure.rails-assets.org/' do
   gem 'rails-assets-adminlte'
   gem 'rails-assets-animate-css'
   gem 'rails-assets-noty'
@@ -56,9 +56,11 @@ gem 'paranoia', '2.4.1'
 gem 'cocoon', '1.2.11'
 gem 'jquery-minicolors-rails', '~> 2.2', '>= 2.2.6.0'
 gem 'simple_form', '4.0.0'
-#
+
 # Upload
 gem 'carrierwave', '1.2.2'
+gem 'carrierwave-imageoptimizer', '~> 1.4'
+gem 'mini_magick', '4.8.0'
 gem 'rmagick', '2.16.0' # fix issue: 'sudo apt install libmagick++-dev'
 
 # Design
@@ -101,7 +103,7 @@ group :development, :test do
   gem 'rubocop', '~> 0.54.0', require: false
   gem 'spring', '2.0.2'
   # gem 'table_print'
-  gem 'web-console', '3.6.0'
+  gem 'web-console', '>= 3.3.0'
 
   # Style guides
   gem 'haml_lint', '~> 0.27.0', require: false