Worklog for task "Locally Deploy the Original Ruby Website"

Local Startup of Legacy Ruby Site Completed

The old bizneshelper.ru has been successfully launched locally using Docker.

Confirmed Legacy Environment Configuration

• Ruby on Rails 3.2.21.
• The original server used Ruby 2.2.5 via Passenger.
• Ruby 2.2.10 was used for the container as a compatible version of the same branch.
• Bundler 1.15.4.
• MySQL is used as an external, already running service.
• The site is launched in the production environment.

What Was Done

• Prepared a Dockerfile for the old Ruby stack based on Ruby 2.2.10.
• Switched apt sources for Debian Jessie to archive repositories, as the standard repositories for this version are no longer available.
• Installed the necessary system dependencies for building legacy gems and running MySQL/libv8.
• Added the bizneshelper service to docker-compose and connected it to the existing MySQL service via environment variables.
• Configured a separate local port for accessing the application.
• Added support in database.yml for connecting to MySQL via host instead of a local Unix socket.
• Downgraded the ckeditor version to a branch compatible with Rails 3.2.
• Confirmed that the presence of Rails 5-oriented directories app/channels and app/jobs does not block startup under the current production configuration with aggressive class loading disabled.

Discovered Features and Risks

1. Debian Jessie requires the use of archive repositories and special package installation parameters.
2. Some legacy gems are incompatible with modern library versions and require pinning to older versions.
3. The older branch of mysql2 is sensitive to the environment and the method of connecting to MySQL.
4. A newer version of ckeditor uses the Rails 4+ API and therefore must be pinned to a compatible version.
5. The original project contains artifacts from newer Rails versions, indicating historical project changes and requiring caution during automated code migration.

Result

The legacy site can be reproduced and launched locally, and is available as a benchmark for further inventory, behavioral comparison, and migration to haih-cms.

What to Check Next

• Completeness of key pages and forms display.
• Solr search operation.
• Correctness of legacy media loading.
• Admin panel behavior.
• Actual routes, friendly_id, and redirects.
• Compliance of the local database with the original data structure.

Passwords, local absolute paths, and other sensitive environment parameters are not recorded in the public worklog.