Worklog for task "Inventory of the current Ruby website"

Clarification on Local Run Results

The local deployment of the legacy site has been successfully completed, which has made it possible to confirm some previously speculative data.

Confirmed

• The original server environment used Ruby 2.2.5 via Passenger.
• Rails 3.2.21 is compatible with running in a container on Ruby 2.2.10.
• The legacy application uses MySQL via a network connection when the host is explicitly specified.
• A newer ckeditor branch is incompatible with Rails 3.2; the working option requires pinning a compatible 4.0.x version.
• The project contains directories and files typical of Rails 5 (app/channels, app/jobs), although the main application remains Rails 3.2. This is important to consider when analyzing the source code structure: not all files in the project tree are part of the actually working legacy runtime.

Conclusion for Inventory

The project can now be explored not only statically through code and dumps, but also dynamically via a locally running copy. This allows models, routes, and content to be cross-checked against the actual behavior of the site and reduces the risk of erroneously migrating unused or historically left-over components.

The next priority is to go through public routes, check media links, search, forms, and the administrative section, comparing the observed behavior with routes.rb, models, and the DB schema.