Open jvendetti opened 4 months ago
Do you think that removing from the UI is also a possibility? right now I think we use it only for the license check.
I mean we can move that logic to the API and have no more to support MySQL in the front.
As long as we're committed to using the Ruby on Rails framework I think the application should be properly backed by a reasonably up-to-date version of a MySQL or Postgres database. In addition to the license check, we store clicks on search results. The data isn't used for anything currently, but removing it was rejected the last time the topic was discussed: https://github.com/ncbo/bioportal_web_ui/issues/269#issuecomment-1601310329.
I'm not in favor of moving existing licensing functionality to the API. The sole reason it was developed was to provide a minimally viable solution to encourage users of the OntoPortal virtual appliance to register for and annually renew their licenses in the form of a non-dismissible nag banner across all pages. To me this has always felt like a natural fit for the Rails application.
We currently use MySQL 5.7 in production, which reached end of life in Oct. of 2023. The Homebrew formulae for installing mysql@5.7 is also deprecated: https://formulae.brew.sh/formula/mysql@5.7. The mysql2 gem compatibility chart indicates compatibility with MySQL 8.0.
We should consider attempting an upgrade when we have a window.