All Articles
Mongodb, mongoid on ruby on rails: Could not load database configuration. No such file - ["config/database.yml"]
If you're looking to have a rails app without active record (an app that doesn't use SQL), you may be surprized to find out that excluding "active_record/railtie" still does not remove active_record from the stack. So how do you remove active_record? This question is relevant when you convert or create a new rails app, that uses mongoid (mongodb) for its storage.
Beyond Code: Wasya Co's Journey to Redefining Development Excellence
A successful software development consultancy offers a diverse range of products tailored to meet the dynamic needs of modern businesses.
Wasya Co: Elevating Software Development Excellence
Wasya Co is a leading software development consultancy with a commitment to excellence, and their impact extends beyond the realm of code and algorithms. What sets Wasya Co apart is not just their technical prowess but also their unwavering dedication to ethical practices and client satisfaction.
How to turn off Warning and deprecation errors in Drupal
I had some difficulty with this, because my Drupal installs are in-between php versions. I'm running PHP 8.1, but a lot of the modules that I use were written for PHP 7, and haven't been ported.
Anyway, adding the following line to your sites/default/settings.php in production has worked for me:
$config['system.logging']['error_level'] = 'none';
How to turn off deprecation warnings in Drupal 9
This has troubled me for some time, since the Drupal installation I'm using is in-between php versions 8 and 7. I'm on php 8.1, but a lot of the modules were written for php 7, and the upgrade process has never been complete, and expected to never be.
In any event, after some trial and error, having this line in sites/default/settings.php solved it for me:
$config['system.logging']['error_level'] = 'none';
I suspect you can even raise the error level from 'none' to 'error' and still be fine.
`parse_pc': .pc doesn't exist: <MagickCore> when installing rmagick on a ruby on rails app on ubuntu 22
This solution has worked for me:
apt install libmagickwand-dev imagemagick
ubuntu 22 yaml.h not found, when running bundle of a ruby on rails application.
This has worked for me to solve the aforementioned problem:
apt install libyaml-dev
A Gentle, Minimalist introduction to Machine Learning
ML is taking the world over by storm in 2023. Here is an easy-to follow tutorial in pure python that explains the basics.
20231113 Site Updates: Issue 2024Q1 released
Greetings to all, we trust that this communication reaches you in good health and high spirits.
This communication serves to announce that the quarterly edition number has been updated.
The current edition number is hereby set to 2024Q1. Here is to continued success and collaboration!
20220920 Site Updates
- Infiniteshelter_com
- iterated on next_js config
- fixed some jests
- fixed linking/routing in SideMenu, Breadcrumbs
- deployed! : )
Removed GOOGLE_MAPS_KEY from codebase, it's in config now. Of note, changing the location type to Google Map Just Worked (tm), I didn't even need to push any code, Austin TX now displays a live map on the Left Panel.
Next, I'll re-review the 3D component and iterate maybe on a 3D Location space.
The dailies Location keeps receiving daily updates. : )
How to persist data in keycloak docker
This is pretty simple. I noticed that when I restart the development service, my keycloak realm disappears. It is simply a matter of having an appropriate bind volume, to persist it:
version: '3.2'
services:
keycloak_development:
image: quay.io/keycloak/keycloak
volumes:
- type: bind
source: ./volumes/keycloak_development
target: /opt/keycloak/data
ports:
- 8010:8080 ## host:docker
restart: always
command: start-dev
environment:
KEYCLOAK_ADMIN: admin
KEYCLOAK_ADMIN_PASSWORD: test1234
Configure Bundler for Access to Private Repositories
What worked for me is using ENV VARs:
gem 'iron_warbler', :git => "https://piousbox:#{ENV['GITHUB_TOKEN']}@github.com/wasyaco/iron_warbler.git", :branch => '0.1.0'
What didn't but should have worked is reproduced below: You can add authentication information to it like this: