I simply followed this guide for setting up a replica set in MongoDB with Docker Compose. I am trying to connect to my local MongoDB replica set (configured via Docker Compose) via an application running on Quarkus, however I am getting the following logs as soon as I try to access the database via the application: 13:18:30,299 INFO (cluster-ClusterId])įor some reason it seems to automatically remove the node from the client view when the application tries to connect to the database for reading/retrieving data. This is my complete docker-compose.yml file: version: '3' I deleted, pruned, removed cache, etc, and still, vendor reappear. I want to combine the articles and podcasts in one field make it look like thisīy following recommendations online, the intended way to ignore a subdirectory inside a bind volume is to "map" the subfolder to an anonymous volume with no definitions like so: version: '3'īut for some reason in my host machine, I still see the vendor folder. I currently have my rails configuration setup as such: config.model InhouseBanner do Has_many :podcasts, through: :adapter_inhouse_banner, source: :inhouse, source_type: 'Podcast' Has_many :articles, through: :adapter_inhouse_banner, source: :inhouse, source_type: 'Article' Has_many :adapter_inhouse_banners, as: :inhouseĬlass AdapterInhouseBanner < ApplicationRecord Podcast and Article use adapter_inhouse_banner for the inhouse_id and inhouse_type.Īdapter_inhouse_banner also keeps an inhouse_banner_id column which has a foreign key connection with the id on inhouse_bannerįor context: The idea behind inhouse banners is to choose articles and podcasts to be displayed in a seperate pages with ids called inhouse banners class Podcast < ApplicationRecord I have these four classes which are combined with polymorphic association.
Rubymine remote debug how to#
Rubymine remote debug install#
In addition you can install the New Windows Terminal to work with bash, powershell, cmd and others.I am experimenting with Rubymine's "Docker-Compose" integration. In this simple way we can take advantage of WSL to work with Ruby in a more efficient and comfortable way.