Category: News
Ruby 3.3.4 Released
Ruby 3.3.4 has been released.
This release fixes a regression in Ruby 3.3.3 that dependencies are missing in the gemspec
of some bundled gems: net-pop, net-ftp, net-imap, and prime
[Bug #20581].
The fix allows Bundler to successfully install those gems on platforms like Heroku.
If your bundle install runs correctly now, you may not have this issue.
Other changes are mostly minor bug fixes.
Please see the GitHub releases for further details.
Release Schedule
Going forward, we intend to release the latest stable Ruby version (currently Ruby 3.3) every 2 months after a .1 release.
For Ruby 3.3, 3.3.5 is supposed to be released on Sep 3rd, 3.3.6 on Nov 5th, and 3.3.7 on Jan 7th.
If there’s any change that affects a considerable amount of people, e.g. Ruby 3.3.3 users on Heroku for this release,
we may release a new version earlier than expected.
Download
-
https://cache.ruby-lang.org/pub/ruby/3.3/ruby-3.3.4.tar.gz
SIZE: 22110179 SHA1: 408362dfb0413122e09d35bafdcced8922b54e71 SHA256: fe6a30f97d54e029768f2ddf4923699c416cdbc3a6e96db3e2d5716c7db96a34 SHA512: 56a0b88954a4efd0236626e49cc90cdb15d9bfd42b27d7fc34efae61f500058e58cb32c73fdef5f1505a36602f4632d6148bf3bd1df539cb5581ae157c78c22b -
https://cache.ruby-lang.org/pub/ruby/3.3/ruby-3.3.4.tar.xz
SIZE: 16366580 SHA1: 4fac2e1609535f71cbdbf9ab9dcea6f6e80a304a SHA256: 1caaee9a5a6befef54bab67da68ace8d985e4fb59cd17ce23c28d9ab04f4ddad SHA512: b26461a13ff82a08a282f10108028bb2a2e4a28da6182a291062fc54089c6655d79c22cc69d59156f9b11cb10a17fe8c69d489343fbae123a45f03361b95c9eb -
https://cache.ruby-lang.org/pub/ruby/3.3/ruby-3.3.4.zip
SIZE: 26995054 SHA1: dcd35f8d428e61807b5c95b6e2e79444fb32f214 SHA256: 3cf0ee03dd4c98e78e8ab5e191af926870415770ef4995088ed069caef639b2a SHA512: c24ca2e6b1114f9c489c049c07acccb0db0916c42c68ea90eaa9acc430973de68342df19710c58130fe264a291958c89e60815c5b00f91decf5a4d1d674a0b32
Release Comment
Many committers, developers, and users who provided bug reports helped us make this release.
Thanks for their contributions.
Posted by k0kubun on 9 Jul 2024
Design and build the next version of OSNews
Mon SteamDeck OELD a un problème…
Mon setup COMPLET (PC / Caméra / Autres) : http://textup.fr/248446PT
Si vous voulez me soutenir, vous pouvez le faire en achetant vos produits technologiques avec ce lien : https://leotechmaker.com/me-soutenir
(Vous ça ne vous change rien au prix de ce que vous achetez, moi je récupère un % de la vente, merci ❤️❤️)
SUIVEZ MOI ICI PARTOUT POUR NE JAMAIS ARRÊTER D’APPRENDRE !
—————————————————
Twitter: / leotechmaker
Instagram: / leotechmaker
TikTok: / leotechmaker
Twitch: / leotechmaker
Mon extension Chrome à installer ABSOLUMENT : http://leotechmaker.com/addon
Si tu es descendu jusque-là, n’oublie pas de liker la vidéo, après tout, t’as bien cliqué sur “en voir plus”, tu peux bien utiliser un clic de plus…
What is a CMS and why using one?
Remember that to understand how a CMS works, you don’t need to study what I’m explaining, it’s just for you to go over the concepts used to create the system. It’s good to know but you won’t use it on a daily basis unless you want to become a coder.
TIMESTAMPS:
00:00 – Intro
00:19 – The DOM
00:44 – HTML
01:13 – CSS
01:30 – Javascript
01:55 – PHP
02:27 – AJAX
03:06 – OOP + Database
04:48 – MySQL
05:05 – The CMS concept
05:30 – Features of a CMS
05:50 – Choices of CMS
For business inquiries contact us at info@digitweaks.com
Whatsapp +34633761802 (Text only)
Digitweaks, Creative agency based in Barcelona
www.digitweaks.com
CREATIVE COMMONS ATTRIBUTIONS:
Photo of Sir Tim Berners-Lee at Knights Foundation:
by Scott Henrichsen used under CC 2.0 License
https://creativecommons.org/licenses/by/2.0/
HTML element content categories:
by Максим Пе used under CC BY-SA 4.0 Deed License
without modification
https://creativecommons.org/licenses/by-sa/4.0/
Brandon Eich’s Mozilla Foundation official photo
by Darcy Padilla used under CC BY-SA 3.0 Deed License
https://creativecommons.org/licenses/by-sa/3.0/
Rasmus Lerdorf photo:
by William Stadtwald Demchick used under CC BY-SA 4.0 Deed License
https://creativecommons.org/licenses/by-sa/4.0/
Jesse James Garrett photo:
by Christine Claypoole used under CC BY-SA 4.0 Deed License
https://creativecommons.org/licenses/by-sa/4.0/
joshics.in: Mastering Multi-Site Configurations in Drupal: A Comprehensive Guide
bhavinhjoshi
Mon, 07/08/2024 – 15:26
In the constantly evolving digital world, the ability to efficiently manage multiple websites has become a necessity for businesses of all sizes.
Thankfully, Drupal, an open-source content management system, has made this simpler with its multi-site configuration feature.
This functionality makes it easier to handle numerous websites from a single Drupal installation, saving time, effort, and resources. But how do we configure this feature in Drupal?
This blog post explores the ways to achieve multi-site configurations in Drupal in thorough detail.
Understanding Drupal Multi-Site Configurations
Before we go deeper, let’s understand what Drupal multi-site configuration means. Simply put, it allows you to run multiple websites from one codebase. Each website can have its own content, settings, enabled modules, and themes, while sharing the core code, contributed modules, and themes. This arrangement benefits website managers who manage multiple sites, as they can apply updates to all at once.
How to Set Up Multi-Site Configurations
- Creating Sub-Directories
The first step is to create sub-directories for each site in the ‘sites’ directory. This is where individual settings for each site reside. The directory name would typically be your site’s URL. For instance, if your site’s URL is ‘example.com’, the directory name would be ‘sites/example.com’. - Setting Up the Database
Each site requires its own database. During Drupal installation, you need to set up a new database for each site. Remember to collate each database in ‘utf8mb4_general_ci’ to avoid any characters failing to write to the database. - Configuring Settings.php
For each site, you will need a settings.php file. This file contains critical information about your site such as base URL, database credentials, and more. You can find a default.settings.php file in the ‘default’ directory. Copy this file into your new site directory and rename it to ‘settings.php’. Update the necessary details like the database name, username, and password. - Configuring the Web Server
Next, you need to configure your web server to point to the correct site directory. For Apache servers, you would use the .htaccess file, while nginx servers use the nginx.conf file. - Installing Drupal
Finally, install Drupal for each site by navigating to your site’s URL in a web browser. Follow the installation prompts, and in no time, your website will be up and running.
The Importance of Multi-Site Configurations
With multi-site configurations, you can centralise your web management tasks, reducing the need for redundant tasks. You can apply core updates, security patches, and other changes across all your sites with a single stroke. This translates into reduced effort, time, and risk of errors.
Further, this simplifies your hosting environment as you’re using a single codebase, making it easier to manage your server resources and optimise for performance.
Pitfalls to Avoid
Despite its numerous benefits, multi-site configurations are not without their challenges. Remember, changes made are site-wide; an update beneficial to one site might disrupt another. Thus, always carry out extensive testing before deploying changes. Additionally, ensure to maintain regular backups to quickly restore any problematic updates.
Conclusion
Mastering Drupal’s multi-site configurations can become an asset in your digital arsenal. It not only optimises resources but also streamlines your web management process. However, it requires strategic planning and careful execution to exploit its full potential.