A CMS Documentation Clarification
I've started a couple of side projects for community organizations that are pushing me into new areas of development. Along with open-source contributions, these are giving me a sense of what IRL development feels like beyond my own personal projects.
In one case I initially thought I needed an open source CMS which led me to running through a side-by-side installation of several options like a pig race. Documentation for most was spotty but AlchemyCMS and GhostCMS were best documented and -although very different- tied for the win.
Even though I'm now looking into CRM options for both projects instead, I'm going to provide some guidance through my process that resolved a number of issues I ran into getting started with FaeCMS. Not all of the steps below were in the documents, and some were only found through extensive googling and problem solving on my own.
Let's get started!
My current environment versions are ruby 2.6.1p33 and Rails 6.0.2.1 and the repo is currently just the corrected boilerplate.
Naturally I started with running rails new FaeDEV then bundle add fae-rails.
Following the docs, rails g fae:install did not work. I found that I needed to opt out of a Rails 6 dependencies autoloading mode called zeitwerk by adding config.autoloader = :classic to config/application.rb.
Upon running rails g fae:install per the docs, the install broke. Based on the error messages I determined it was down to an ActiveRecord issue. I added '[4.2]' to the end of 'ActiveRecord::Migration' in each migration file. I was then able to run rails db:create && rails db:migrate.
The final error I worked through before successfully spinning up the server was solved by adding '//= link fae/application.css' and '//= link fae/application.js' to app/assets/config/manifest.js.
A run of rails s and a visit to localhost:3000 now led me to creating the first user for the project.
Top comments (0)