DEV Community: Nelson Garcia Dev.

Quick tip: How to recover or set up the full MinIO console in Docker (avoiding the limited Community Edition).

Nelson Garcia Dev. — Thu, 19 Mar 2026 20:02:27 +0000

Recently, I ran into a frustrating issue when running MinIO in Docker using the official tag minio/minio:latest.

The web console opens, but it shows up as "Community Edition" with severely limited features: basically just the object browser. No user management, policies, access keys, advanced configurations... all of that vanished from the GUI. 😩

I ended up relying on mc (MinIO Client) to handle almost everything, which works fine but loses the convenience of the browser interface.

After researching and testing several tags, I found a simple solution that restored the complete console (with all admin features visible):

Instead of minio/minio:latest, I'm using this image:
quay.io/minio/minio:RELEASE.2025-04-22T22-12-26Z

With this specific tag (an April 2025 release), the console goes back to normal: full browser access, no restrictions from the newer "Community Edition."

Quick example with docker-compose:

It's been running stable for me for weeks. If you're hitting the same issue with the latest tag, try this older one — it might save you a lot of time!

Has anyone else dealt with this? Or have a better workaround/solution? Share in the comments! 👇

MinIO #Docker #ObjectStorage #DevOps #SelfHosted #S3Compatible #communityedition

🧱 Angular: How to Create Multiple Components at Once (From Basic to Advanced)

Nelson Garcia Dev. — Mon, 21 Apr 2025 13:31:37 +0000

So, have you ever gotten tired of generating components one at a time?
Yeah, me too. That’s why I started looking for smarter ways to automate this process — and now I’m here to share them with you.

📌 Introduction

When developing scalable Angular applications, keeping your components well-structured and organized is crucial.
Instead of generating each one manually using ng generate component, let’s level up and make the process faster, cleaner, and more productive.

📌 Step 1 – Understanding the Basics

✅ What is a Component?

In Angular, a component is a core building block of the user interface. It includes:

ts (logic)
html (template/view)
css/.scss (style)
spec.ts (unit test – optional)

✅ How to Create a Component (manually)

ng generate component components/header

Or simpply:

ng g c components/header

Which generates:

src/app/components/header/
├── header.component.ts
├── header.component.html
├── header.component.scss
└── header.component.spec.ts

🧰 Step 2 – Creating Multiple Components at Once (Intermediate Method)

📦 Option 1: One-liner with a loop (Git Bash, Linux, or Mac)

for c in header sidebar footer dashboard; do ng g c components/$c; done

This command will quickly generate multiple components inside the components/ folder:

header
sidebar
footer
dashboard

📦 Option 2: Using && to chain commands

ng g c components/register && 
ng g c components/list && 
ng g c components/edit && 
ng g c components/delete

This creates the same result in a straightforward way — great for quick setups.

📦 Option 3: Creating a reusable script in package.json

You can add a script to automate component generation:

{
  "scripts": {
    "component-generator": "ng g c components/register && ng g c components/list && ng g c components/edit && ng g c components/delete"
  }
}

Then just run:

npm run component-generater

✨ Step 3 – Advanced Tips

📍 Add extra options to customize component creation:

Option           Description
--skip-tests     Does not create the test file
--style=scss     Uses SCSS instead of CSS
--flat           Creates the component without a folder (saves directly in components/)
--standalone     Creates a standalone component (Angular 14+)

Exemplo:

ng g c components/navbar --skip-tests --style=scss --flat

✅ Expected Final Result

By the end of this guide, you’ll have multiple components quickly generated, organized, and ready to use — following solid practices for modularization and automation in Angular.

Thanks so much for reading! I hope this guide saves you time (and sanity 😅).

If you enjoyed this content, leave a ❤️, Save it for later, and Share it with your dev crew!
And if you want to add something, drop a comment and we’ll learn with your contribuition and go to next level. 🚀

✍️ Written by: Nelson Manuel Garcia
Feel free to reach out if you have questions or want to connect! 🎧💻

💡How to Integrate Materialize-CSS with Angular (Without the Headache!)

Nelson Garcia Dev. — Wed, 16 Apr 2025 16:18:21 +0000

After struggling, crying (a little), and spending hours debugging, I finally managed to integrate Materialize-CSS into my Angular project. 😅

Along the way, I encountered several unexpected bugs and compatibility issues that nearly made me give up.

If you've ever tried to use Materialize-CSS in Angular and couldn't get it to work — or you're just starting out and want to avoid the pain — this post is for you! 🚀

I'll walk you through how to integrate Materialize-CSS into your Angular project in a simple and effective way, without the usual frustration.

Spoiler: It's not just “install and import.” There are a few key tricks that make all the difference.

Let'get into it.

Step-by-step: How to Integrate Materialize-CSS in Angular

first step:

Installing dependecies. First, make sure you have jQuery and its type definitions installed. Then, install Materialize-CSS and its types as well.

# jQuery
npm install jquery

# jQuery types
npm install --save-dev @types/jquery

# Materialize-CSS
npm install materialize-css

# Materialize-CSS types
npm install --save-dev @types/materialize-css

Configuring angular.json You need to include both jQuery and Materialize-CSS in your angular.json file.

"scripts": [
  "node_modules/jquery/dist/jquery.min.js",
  "node_modules/materialize-css/dist/js/materialize.min.js"
],
"styles": [
  "node_modules/materialize-css/dist/css/materialize.min.css"
]

Importing the dependencies You can import the libraries where you'll use them — either in a global module or in a specific component:

import * as $ from 'jquery';
import * as M from 'materialize-css';

for instance:

Initializing Materialize Components Many Materialize components require initialization via JavaScript. Do this inside the ngOnInit() lifecycle hook:

This ensures everything is ready when your component is loaded.

Styling your Template Now you can freely use Materialize's CSS classes in your templates. Here's a simple example:

Using JS-Dependent Components For components that depend on JavaScript (like modals, tooltips, dropdowns, etc.), you'll need to initialize them individually:

In your component.ts:

In your tempate (html code)

Thanks so much for reading! I hope this guide saves you time (and sanity 😅).

If you want to check out the working code, it's available on GitHub:
👉 Repo Link

✍️ Written by: Nelson Manuel Garcia
Feel free to reach out if you have questions or want to connect! 🎧💻