aboutsummaryrefslogtreecommitdiff
path: root/Gemfile
Commit message (Collapse)AuthorAgeFilesLines
* Upgrade Rails and add StimulusJS supporthellekin2021-01-221-4/+4
|
* User commonmarker gemhellekin2020-10-271-0/+2
| | | | | | | This adds support for Markdown for Resource descriptions. CommonMark: https://commonmark.org/ Gem documentation: https://gjtorikian.github.io/commonmarker/
* Add Classifications and Resource validationshellekin2020-10-091-3/+6
| | | | | | | | | | | | | | | | - Turn `has_and_belongs_to_many` into `has_many :through`: now, resources and sections are related through Classifications. - Refactor usage of jsonb column to use ActiveRecord validations - Attention! store_accessor: NOTE: If you are using structured database data types (eg. PostgreSQL hstore/json, or MySQL 5.7+ json) there is no need for the serialization provided by .store. Simply use .store_accessor instead to generate the accessor methods. Be aware that these columns use a string keyed hash and do not allow access using a symbol. NOTE: The default validations with the exception of uniqueness will work. For example, if you want to check for uniqueness with hstore you will need to use a custom validation to handle it. https://api.rubyonrails.org/classes/ActiveRecord/Store.html
* Add model foundation for classificationshellekin2020-10-081-0/+2
| | | | | | | | Taxonomy > Category > Section This commit adds models for it. https://doc.incommon.cc/#classifications
* Added leaflet gem and changed a bit the Edit Ressource page to be able to ↵Nemael2020-10-081-0/+4
| | | | edit categories
* User Kaminari gem for paginationhellekin2020-10-061-0/+2
| | | | | | | | | Since we're dealing with lots of resources, we need a way to handle pagination. This gem seems to be the new kid on the block and doing things right, including pagination by default an I18n support. Let's see. Kaminari: https://github.com/kaminari/kaminari
* Add Resource modelhellekin2020-10-061-0/+2
| | | | | | Resources will be stored as JSON, in the (GeoJSON) :feature column. They are assigned an UUID upon creation if they don't comme with one. They belong to an Agent.
* Add better integration with systemdhellekin2020-10-061-0/+1
|
* [SECURITY] Update Ruby to v2.6.6 (take two)hellekin2020-10-061-1/+1
|
* Use Discourse API gemhellekin2020-10-061-0/+2
| | | | | | We use the DiscourseApi::Client to interact with https://talk.incommon.cc discourse_api: https://meta.discourse.org/t/using-the-discourse-api-ruby-gem/17587
* Use pry and bitfieldshellekin2020-10-051-0/+5
| | | | | | | | | | | | | Pry is a great console enhancement for development. You can navigate through code and object with `cd` and `ls`, or use `show-method foo` to see how it's written... Bitfields allow to store multiple flags in an efficient integer. It will be used to keep track of a User's roles within an Agent. Pry: https://pry.github.io/ Pry-Rails: https://github.com/rweng/pry-rails Bitfields: https://github.com/grosser/bitfields
* rails new incommon-map -d postgresql -C -Thellekin2020-10-051-0/+44