# copied from https://github.com/sidekiq/sidekiq/blob/main/Gemfile Source "https://rubygems.org" Gemspec Gem "rake" RAILS_VERSION = "~> 8.0" Gem "actionmailer", RAILS_VERSION Gem "actionpack", RAILS_VERSION Gem "activejob", RAILS_VERSION Gem "activerecord", RAILS_VERSION Gem "railties", RAILS_VERSION Gem "redis-client" # gem "bumbler" # gem "debug" Gem "sqlite3", "~> 2.2", platforms: :ruby Gem... - Source: dev.to / about 1 month ago

All the things we've done for a gem are to release it on https://rubygems.org/. To release the gem, you need an account on https://rubygems.org/ first. So, sign up for one if you haven't done that yet. Then execute rake build to build a gem file under pkg, it should look like pkg/your_gem-0.0.1.gem. The version number 0.0.1 is defined in the lib/your_gem/version.rb. Finally, we call. - Source: dev.to / 3 months ago

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org. - Source: dev.to / 6 months ago

Gem install asciidoctor-pdf ERROR: SSL verification error at depth 2: unable to get local issuer certificate (20) ERROR: You must add /......../=Zscaler Root CA/emailAddress=support@zscaler.com to your local trusted store ERROR: SSL verification error at depth 2: unable to get local issuer certificate (20) ERROR: You must add /......../=Zscaler Root CA/emailAddress=support@zscaler.com to your local trusted... - Source: dev.to / 6 months ago

Source 'https://rubygems.org' Git_source(:github) do |repo_name| repo_name = "#{repo_name}/#{repo_name}" unless repo_name.include?("/") "https://github.com/#{repo_name}.git" End Gem 'pronto' Gem 'oj' Gem 'pronto-rubocop', require: false Gem 'pronto-scss', require: false Gem 'pronto-eslint', require: false Gem 'pronto-brakeman', require: false Gem 'pronto-rails_best_practices', require: false. - Source: dev.to / 11 months ago

You might wonder why we use Supervisor instead of alternatives like Systemd, PM2, or containerized solutions like Docker. Here’s a quick comparison:. - Source: dev.to / about 2 months ago

Idk, when systemd became the main thing I hated it too. But mostly because it was different and I didn't know how to use it. But then I learned and you know what? I agreed. This took awhile though and I had to see the problems they are solving. Otherwise it looks really bloaty and confusing. Like why have things like nspawn? Why use systemd jobs instead of using cron? Why use systemd-homed instead of useradd? Well... - Source: Hacker News / 4 months ago

Here's my take at this point. If you require blazing speed, the Momento SDK for Rust handles topic subscriptions like a champion. It's easy to code with. Easy to set up. And I get an amazing performance. In cases where I need to update a leaderboard, perhaps deal with real-time chats, or work with financial data that needs to be updated as it happens, this would 100% be the way I'd go. There is no substitute... - Source: dev.to / 10 months ago

To that end, I created a script called journal.sh, and then created a systemd unit on my Linux machine that runs this using systemd timers (like cron but infinitely more powerful and flexible). Source: over 1 year ago

You want your application to be available on the internet whenever it is accessed on any authorized device, from any authorized location. To achieve this, you can create a service to manage your node app. This service will be managed in Systemd to reliably ensure that your application is always running smoothly (i.e. starting, stopping, restarting, monitoring and occasionally fixing issues to keep the application... - Source: dev.to / over 1 year ago