Is it possible to move activerecord models to a separate gem?

Question

Ruby on Rails

The well-known rails provide the division of the application into, conditionally, 3 parts: model, view, controller. All logic related to data processing and interaction with the database should usually be kept in models.
Have you come across situations in which it would be desirable to separate a certain part (mainly models) from the rest of the application and include it as a gem? For example, if there is some independent part of the system that you would not like to mix with the rest of the application and develop separately. Maybe someone who wrote articles about this, throw links or share your experience.
update
After thinking it over again, I want to rephrase the question. Let's say I have some core functionality that I want to use in different applications. The problem is that this kernel uses activerecord models. What is the best way to arrange this so as not to copy model files from project to project each time?

Answer 1

Engines .
In fact, these are gems.

Answer 2

In fact, all active record models are a set of classes that are not related to the database, view-control, or anything else.
Make sure the model names are unique and wrap the gem with a simple require of each file in the gemname .rb file

Answer 3

<option {% if state == "all" %}selected="selected"{% endif %} value="all">Все</option>
<option {% if state == "true" %}selected="selected"{% endif %} value="true">Оплачено</option>
<option {% if state == "false" %}selected="selected"{% endif %} value="false">Не оплачено</option>

Answer 4

I would say that here it is not a specific template that needs to be changed, but the whole approach. Writing such HTML by hand is wrong. It's hard to write, hard to read, and even harder to modify.
It is correct to use django.forms.Formor django.forms.ModelFormand let it be displayed automatically by means of the same Django (form.as_p, form.as_ul) or django-crispy-forms.