DEV Community: somen das

I added if-else & loops in HTML5

somen das — Sat, 07 Jun 2025 03:38:31 +0000

So it's time to stop the meme that HTML is not a programming language. i just added support to HTML5 of for loops
if else conditions.
template inclusions.
automatic State rebuild on variable change.
lot's of things nowadays they have in bloatwares like react.

check it out on guthub under KTBsomen/httl-s
To use this library, simply include the script in your HTML file after the body tag this should be loaded at last after defining all custom components:

    <script src="https://cdn.jsdelivr.net/gh/KTBsomen/httl-s@main/statejs.js"></script>

<for-loop array="[1, 2, 3]" valueVar="item" indexVar="index" loopid="loop1">
    <template loopid="loop1">
        <p>Index: ${index}, Value: ${item}</p>
    </template>
</for-loop>

<condition-block ifid="condition1">
    <if-condition value="5" eq="5" elseid="conditionElse">
        <p>Condition is true!</p>
    </if-condition>
    <else-condition elseid="conditionElse">
        <p>Condition is false!</p>
    </else-condition>
</condition-block>

here is a full example

<!DOCTYPE html>
<html lang="en">
   <head>
      <meta charset="UTF-8" />
      <title>Reactive Counter with HTTL-S</title>
      <script src="https://cdn.jsdelivr.net/gh/KTBsomen/httl-s@main/statejs.js"></script>
   </head>
   <body>
      <condition-block ifid="condition1">
         <template ifid="condition1">
            <h1>Counter: {{ count }}</h1>
         </template>
      </condition-block>
      <button onclick="count++">Increment</button>
      <script>
         // Declare the reactive variable

         watch("count",(x,y)=>{
           setState()
         },0); // This makes `count` reactive and bindable in HTML
         initState()
      </script>
   </body>
</html>

Combine multiple S3 storage

somen das — Tue, 27 May 2025 15:16:04 +0000

I currently have some files stored in AWS S3 and others in Cloudflare R2. That made me realize—it would be really convenient to combine everything into a single API. By doing so, I can take advantage of the free tiers offered by multiple cloud storage providers. As soon as I reach the limit on one provider, I can simply create another account or switch to another service and add it to my unified system.

This approach allows me to maintain a single source of truth for all my file storage and retrieval needs. Behind the scenes, it intelligently manages connections to multiple S3-compatible storage providers. This would significantly simplify how I handle file uploads and access across services.

🎯 Why I'm Building This Package:

I'm building a package that acts as a unified interface for multiple S3-compatible cloud storage APIs. The goal is to:

Simplify File Management: Upload and access files through a single API, regardless of the underlying provider (e.g., AWS S3, Cloudflare R2, Wasabi, Backblaze B2, etc.).
Optimize Cost: Leverage free tiers across various providers by intelligently routing uploads or downloads to the least costly or most available storage bucket.
Seamless Scalability: As storage needs grow, I can add more cloud accounts or services without changing how the API is used.
Abstraction of Complexity: Hide provider-specific quirks and authentication behind a single clean interface.
Failover and Redundancy: If one provider fails or reaches a quota, the system automatically falls back to another available provider.

This package will make it easy to build apps or services that need reliable and affordable cloud storage without locking into a single provider or dealing with vendor-specific APIs.

MultiBucket

github

A Node.js library for generating presigned URLs for multiple object storage providers (AWS S3, Cloudflare R2) with automatic load balancing.

Features

Support for multiple storage providers (AWS S3 and Cloudflare R2)
Automatic load balancing between providers using various strategies
Live configuration updates from file or remote URL
Rate limiting and error handling
RESTful API endpoints for generating presigned URLs
Monitoring and statistics

Installation

npm install multibucket

Dependencies

This library requires the following dependencies:

npm install @aws-sdk/client-s3 @aws-sdk/s3-request-presigner express axios chokidar

Basic Usage

const MultiBucket = require('multibucket');

// Create an instance with initial providers
const storagePresigner = new MultiBucket({
  providers: [
    {
      id: 's3-main',
      type: 's3',
      bucket: 'my-main-bucket',
      region: 'us-east-1',
      accessKeyId: 'YOUR_AWS_ACCESS_KEY',
      secretAccessKey: 'YOUR_AWS_SECRET_KEY',
      weight: 3,
      rateLimit: 100
    },
    {
      id: 'r2-cloudflare',
      type: 'r2',
      bucket: 'my-r2-bucket',
      endpoint: 'https://account-id.r2.cloudflarestorage.com',
      accessKeyId: 'YOUR_R2_ACCESS_KEY',
      secretAccessKey: 'YOUR_R2_SECRET_KEY',
      publicUrlBase: 'https://cdn.example.com'
    }
  ],
  loadBalanceStrategy: 'round-robin',
  defaultExpiry: 3600
});

// Start the API server
storagePresigner.createServer(3000);

Configuration Options

Constructor Options

providers: Array of storage provider configurations
configSource: Path or URL to a config file (optional)
loadBalanceStrategy: Strategy for load balancing (default: 'round-robin')
defaultExpiry: Default expiry time for presigned URLs in seconds (default: 3600)

Provider Configuration

Each provider object requires the following properties:

Common Properties:

id: Unique identifier for the provider
type: Provider type ('s3' or 'r2')
bucket: Bucket name
accessKeyId: Access key ID
secretAccessKey: Secret access key
weight (optional): Weight for weighted-random load balancing
rateLimit (optional): Maximum requests per second
publicUrlBase (optional): Base URL for public access

S3-specific Properties:

region: AWS region
endpoint (optional): Custom endpoint for S3-compatible services
forcePathStyle (optional): Use path-style addressing

R2-specific Properties:

endpoint: R2 endpoint URL

Load Balancing Strategies

round-robin: Cycle through providers sequentially
least-used: Select the provider with the fewest requests
least-errors: Select the provider with the lowest error rate
weighted-random: Select providers randomly based on their weight

External Configuration

You can provide a path to a JSON file or a URL in the configSource option:

const storagePresigner = new MultiBucket({
  configSource: './storage-config.json'
});

The library will watch for changes to the file or poll the URL to update the configuration dynamically.

API Endpoints

When you start the server with createServer(), the following endpoints are available:

Generate Upload URL

POST /generate-upload-url

Request body:

{
  "filename": "example.jpg",
  "contentType": "image/jpeg",
  "path": "uploads/images",
  "expiry": 1800,
  "providerId": "s3-main"
}

Response:

{
  "uploadUrl": "https://my-main-bucket.s3.us-east-1.amazonaws.com/uploads/images/uuid-example.jpg?...",
  "publicUrl": "https://my-main-bucket.s3.us-east-1.amazonaws.com/uploads/images/uuid-example.jpg",
  "key": "uploads/images/uuid-example.jpg",
  "bucket": "my-main-bucket",
  "provider": "s3-main",
  "expires": "2023-06-01T12:30:00.000Z"
}

Generate Read URL

POST /generate-read-url

Request body:

{
  "key": "uploads/images/uuid-example.jpg",
  "providerId": "s3-main",
  "expiry": 3600
}

Response:

{
  "readUrl": "https://my-main-bucket.s3.us-east-1.amazonaws.com/uploads/images/uuid-example.jpg?...",
  "key": "uploads/images/uuid-example.jpg",
  "bucket": "my-main-bucket",
  "provider": "s3-main",
  "expires": "2023-06-01T13:00:00.000Z"
}

Get Stats

GET /stats

Response:

{
  "providerCount": 2,
  "totalRequests": 150,
  "providerStats": [
    {
      "id": "s3-main",
      "type": "s3",
      "requestCount": 100,
      "errorCount": 2,
      "errorRate": "0.0200"
    },
    {
      "id": "r2-cloudflare",
      "type": "r2",
      "requestCount": 50,
      "errorCount": 0,
      "errorRate": "0.0000"
    }
  ]
}

Health Check

GET /health

Response:

{
  "status": "ok",
  "providers": 2,
  "timestamp": "2023-06-01T11:00:00.000Z"
}

Programmatic Usage

You can also generate presigned URLs programmatically:

// Generate upload URL
const uploadUrlInfo = await storagePresigner.generateUploadUrl({
  filename: 'example.jpg',
  contentType: 'image/jpeg',
  path: 'uploads/images',
  expiry: 1800
});

// Generate read URL
const readUrlInfo = await storagePresigner.generateReadUrl({
  key: 'uploads/images/uuid-example.jpg',
  providerId: 's3-main',
  expiry: 3600
});

License

MIT
"presigned",
"url",
"s3",
"r2",
"cloudflare",
"load-balancing",
"storage",
"upload",
"multi-storage",
"multi-bucket",
"aws-sdk",
"cloudflare-r2",
"express",
"axios",
"chokidar",
"dotenv",
"multi-provider",
"multi-provider-presigner",
"multi-storage-presigner",
"multi-bucket-presigner",
"multi-storage-url",
"multi-bucket-url",
"multi-storage-upload",
"multi-bucket-upload",
"s3-presigner",
"r2-presigner",
"s3-upload",
"r2-upload",
"s3-url",
"r2-url",
"s3-multi-provider",
"r2-multi-provider",
"s3-multi-storage",
"r2-multi-storage"

Local MongoDB in Flutter 😱🤯

somen das — Mon, 05 May 2025 14:25:19 +0000

FlutterDB

FlutterDB is a lightweight, SQLite-based document database for Flutter applications. It provides a MongoDB-like API for managing collections and documents while leveraging the performance benefits of SQLite.

Why do I build this?

So I am using MongoDB in my NodeJS application. Now I am building a chat application in Flutter, and for rendering performance, I thought I should store the messages locally and render a sliding window on it. Still, I have no luck finding a good local database that is flexible enough and also fast enough. And so I thought, why not build a MongoDB-like database in Flutter, which gets the job done. It's not a full-fledged MongoDB running locally, but it is similar to it, and most of the common tasks are going very well, as I tested.

Features

Document-oriented database with collections and documents
MongoDB-style query syntax and operations
Built on top of SQLite for performance and reliability
Unique ID generation for documents
Support for complex queries, updates, and aggregations
Batch operations for better performance

Installation

Add the following dependencies to your pubspec.yaml:

dependencies:
  flutterdb: ^0.0.1

Getting Started

Import the package:

import 'package:flutterdb/flutterdb.dart';

Initialize the database:

final db = FlutterDB();

Basic Usage

Working with Collections

// Create or get a collection
final users = await db.collection('users');

// List all collections
final collections = await db.listCollections();

// Drop a collection
await db.dropCollection('users');

CRUD Operations

Create

// Insert a single document
final userId = await users.insert({
  'name': 'John Doe',
  'email': 'john@example.com',
  'age': 30
});

// Insert multiple documents
final ids = await users.insertMany([
  {
    'name': 'Jane Smith',
    'email': 'jane@example.com',
    'age': 25
  },
  {
    'name': 'Bob Johnson',
    'email': 'bob@example.com',
    'age': 40
  }
]);

Read

// Find all documents in a collection
final allUsers = await users.find({});

// Find documents with a simple query
final adults = await users.find({'age': {'$gte': 18}});

// Find a document by ID
final user = await users.findById(userId);

// Count documents
final userCount = await users.count({'age': {'$gt': 30}});

Update

// Update a document by ID
await users.updateById(userId, {'status': 'active'});

// Update multiple documents
final updatedCount = await users.updateMany(
  {'age': {'$lt': 30}},
  {'status': 'young'}
);

Delete

// Delete a document by ID
await users.deleteById(userId);

// Delete multiple documents
final deletedCount = await users.deleteMany({'status': 'inactive'});

Advanced Queries

Comparison Operators

// Greater than
await users.find({'age': {'$gt': 30}});

// Less than or equal
await users.find({'age': {'$lte': 25}});

// Not equal
await users.find({'status': {'$ne': 'inactive'}});

// In array
await users.find({'role': {'$in': ['admin', 'moderator']}});

Logical Operators

// AND
await users.find({
  '$and': [
    {'age': {'$gte': 18}},
    {'status': 'active'}
  ]
});

// OR
await users.find({
  '$or': [
    {'role': 'admin'},
    {'permissions': {'$in': ['write', 'delete']}}
  ]
});

// NOR
await users.find({
  '$nor': [
    {'status': 'banned'},
    {'role': 'guest'}
  ]
});

Text Search

// Regex search
await users.find({'name': {'$regex': '^Jo'}});

// Simple text search
await users.find({'bio': {'$like': 'flutter developer'}});

Aggregation

final results = await users.aggregate([
  {'$match': {'status': 'active'}},
  {'$sort': {'age': -1}},
  {'$skip': 10},
  {'$limit': 20},
  {'$project': {
          'name': 1,
          'age': 1,
          'city': 1,
          '_id': 0,
               }
  },
  {'$group': {
          '_id': '\$city',
          'count': {'\$sum': 1}
        }
  },
]);

Best Practices

Performance Optimization

Use batch operations for multiple insertions or updates:

   await users.insertMany(manyUsers); // Better than inserting one by one

Keep document size reasonable:
- Large documents can slow down performance
- Consider storing large binary data (images, files) separately
Create indexes for frequently queried fields:
- Currently, FlutterDB automatically indexes collection names
- Future versions may support custom indexes
Use appropriate queries:
- Finding by ID is faster than complex queries
- Limit results when possible using $limit

Data Structure

Use consistent schemas:
- While FlutterDB is schemaless, consistent document structures improve code maintainability
Choose good document IDs:
- Let FlutterDB generate IDs unless you have specific requirements
- Custom IDs should be unique and consistent
Handle relationships thoughtfully:
- For one-to-many relationships, consider embedding related data or using references

Error Handling

Always implement error handling:

try {
  await users.insert({'name': 'John'});
} catch (e) {
  print('Error inserting document: $e');
  // Handle error appropriately
}

Limitations

Not a full MongoDB replacement:
- Limited subset of MongoDB query operators
- Some complex aggregation operations not supported
Performance with large datasets:
- Best suited for mobile apps with moderate data size
- Consider pagination or limiting queries for large collections
No built-in encryption:
- Data is stored in plain text
- Consider additional encryption for sensitive data
Limited indexing options:
- Custom indexes not yet supported
- Consider query performance for large collections
No network synchronization:
- Local database only
- Implement your own sync solution if needed

Complete Example

import 'package:flutter/material.dart';
import 'package:flutterdb/flutterdb.dart';

class UserRepository {
  final FlutterDB _db = FlutterDB();
  late Future<Collection> _users;

  UserRepository() {
    _users = _db.collection('users');
  }

  Future<String> addUser(String name, String email, int age) async {
    final collection = await _users;
    return await collection.insert({
      'name': name,
      'email': email,
      'age': age,
      'createdAt': DateTime.now().toIso8601String(),
    });
  }

  Future<List<Map<String, dynamic>>> getAdultUsers() async {
    final collection = await _users;
    return await collection.find({
      'age': {'$gte': 18},
    });
  }

  Future<void> updateUserStatus(String id, String status) async {
    final collection = await _users;
    await collection.updateById(id, {
      'status': status,
      'updatedAt': DateTime.now().toIso8601String(),
    });
  }
}

void main() async {
  WidgetsFlutterBinding.ensureInitialized();

  final userRepo = UserRepository();

  // Add a user
  final userId = await userRepo.addUser('Alice', 'alice@example.com', 28);
  print('Added user with ID: $userId');

  // Update user status
  await userRepo.updateUserStatus(userId, 'premium');

  // Get all adult users
  final adults = await userRepo.getAdultUsers();
  for (var user in adults) {
    print('User: ${user['name']}, Age: ${user['age']}, Status: ${user['status']}');
  }
}

Future Enhancements

Custom indexing support
More aggregation pipeline operators
Full-text search capabilities
Data encryption options
Schema validation
Observable queries
Migration support

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

This project is licensed under the GNU AGPLv3 License - see the LICENSE file for details.

If you are searching for this keywords
"offline-first Flutter apps"
"local storage in Flutter"
"best local database Flutter"

your search ends here
I'd love your thoughts. Try FlutterDB in your next project and let me know how it goes! You can ⭐️ the GitHub repo or open an issue if you hit any snags. 🙌

Why Your Flutter App Needs `event_handeler`: A Fun, Powerful Alternative (and Companion) to State Management

somen das — Wed, 23 Apr 2025 14:54:56 +0000

Flutter developers, unite!

If you've ever gotten frustrated with setting up full-blown state management just to send a simple message across your app — maybe from a payment success page back to your home screen — you're not alone.

Enter: event_handeler, a lightweight, fun-to-use event broadcasting system that makes your app feel more like a party and less like a board meeting. 🎉

Let's dive into why this little package is a hidden gem, how it can complement your existing setup (like Riverpod, Provider, or Bloc), and why you should definitely give it a try.

🎩 What is `event_handeler`?

It’s a Dart package that lets you:

Send custom events from anywhere in your app
Listen to those events anywhere else
Dispatch global messages, no context required
Handle one-time events automatically

Imagine it as your app’s internal radio station. Tune in to a channel (event type), and whenever someone broadcasts a message, you hear it loud and clear.

✨ Use Cases That Just Make Sense

1. 🚀 Triggering Actions from Background Pages

Your payment page finishes a transaction:

dispatchCustomEvent("done", "paymentComplete");

Back on your cart screen, you’re listening:

addCustomEventListener("paymentComplete", (_) => showSuccessToast());

Boom. Simple. Fast. No weird state gymnastics.

2. 🔄 Coordinating Across Screens

User logs in? Let the profile and home screens update in harmony:

dispatchCustomEvent(userData, "userLoggedIn");

Anywhere in the app:

addCustomEventListener("userLoggedIn", (data) {
  updateProfile(data);
  showWelcomeToast(data.name);
});

3. 🧪 Handling Events Once (and Only Once)

addOneTimeEventListener("userDeleted", (_) {
  Navigator.pushReplacementNamed(context, '/goodbye');
});

Perfect for alerts, confirmations, and transitions that should only happen once.

⚔️ `event_handeler` vs State Management Libraries

Let’s line it up against the big dogs like Riverpod and Bloc:

Feature	`event_handeler`	Riverpod/Provider/Bloc
Setup time	Super quick	Requires architecture
Rebuild widgets	Manual	Yes
Broadcast style	Global (decoupled)	Scoped (contextual)
Best use	Message passing	Reactive state updates
Boilerplate	Almost none	Some required
Widget-dependent?	Nope	Yes (usually)

💡 When to Use It (and When Not To)

✅ Use It When:

You want to keep things simple
You just need to send events around
You’re working on a plugin or tool package
You don’t want to rebuild widgets
You’re building non-UI logic that needs communication

🚫 Don’t Use It Alone If:

You need a persistent or reactive state
Your UI rebuilds are tied to state changes
You want devtools/time travel/debugging integrations

🔄 Using It With Riverpod or Provider

Don't choose — combine!

// event triggered by event_handeler
dispatchCustomEvent("logout", "userLogout");

// update Riverpod state
addCustomEventListener("userLogout", (_) {
  ref.read(authProvider.notifier).logout();
});

Use event_handeler For fire-and-forget comms, and use Riverpod to handle the reactive state part.

🧘‍♂️ Developer-Friendly Philosophy

Minimalism-first: Why over-engineer something simple?
Works everywhere: Widgets, services, controllers, doesn’t matter
No build context madness
Feels like Dart, not magic incantations

🧪 Try It, Just Once

"Try event_handeler once, and you may never go back to callback spaghetti again."

Whether you're an indie dev, a pro working on a plugin, or just someone tired of shouting across widget trees — this is your sign to give it a go.

Check it out on pub.dev, toss it into your project, and let your app's parts start talking like besties at brunch.

👇 Final Thoughts

event_handeler is not trying to replace Riverpod. It's not trying to outsmart Bloc. It’s here to simplify the moments in your app where traditional state management feels like overkill.

In short: it's your app's walkie-talkie. Keep it handy.

📡 Happy dispatching!

Install event_handeler →

new opensource tool 🔥 for one command server deployments and horizontal scaling.

somen das — Mon, 16 Sep 2024 20:23:41 +0000

CICD - Advanced Continuous Integration & Deployment for Modern Workflows

give it a star on GitHub and visit it's homepage

CICD is a fully automated Continuous Integration and Continuous Deployment (CI/CD) system tailored for developers seeking seamless integration, deployment, and monitoring for their applications. Designed to remove the complexities of managing deployments across cloud platforms and on-premise environments, CICD helps streamline your development pipeline with automatic code updates, real-time error detection, and service monitoring.

Built with scalability and flexibility in mind, CICD empowers teams to focus on building features while handling deployment and maintenance automatically, ensuring your infrastructure is always up-to-date and your applications are running optimally.

Why CICD?

1. Completely Automated Deployment Pipeline

CICD provides end-to-end automation for your deployment process. From cloning your Git repository to starting and monitoring services, CICD is designed to require zero manual intervention once configured. Whether you're deploying to a cloud environment or on-premise servers, it gets the job done with minimal configuration.

2. Real-Time Code Monitoring with Webhook Integration

Out-of-the-box support for Git webhooks ensures that every push or pull request to your repository is detected and automatically deployed to your servers. Real-time monitoring makes sure your application is always running on the latest version of your codebase without requiring manual triggers.

3. Dynamic Multi-Environment Setup

Deployments can be set up dynamically across different environments (staging, production, etc.) with environment-specific configurations. CICD adapts to the specific needs of each environment, making it highly flexible for diverse projects and infrastructures.

4. Automated Error Detection and Logging

When something goes wrong, CICD’s integrated logging and notification system automatically sends detailed error reports to your designated admin email. This allows developers to address issues quickly without sifting through logs manually.

5. Infrastructure-as-Code

CICD treats your entire deployment and monitoring process as code. It provides configurable templates that you can customize for any environment or language, enabling reproducible and scalable deployments for large or growing infrastructures.

Core Features

1. One-Command Setup

Deploy your codebase with a single command. With minimal inputs, CICD will pull the latest changes from your repository, configure your environment, and ensure your application runs as a service that automatically restarts on failure or system reboot.

python3 main.py --setup manual --repo-url <git-repo> --admin-email <your-email> --service-dir <service-directory>

2. GitHub & GitLab Webhook Integration

CICD listens for webhooks from both GitHub and GitLab. Every new commit triggers an automated deployment process, ensuring that your servers are always running the latest stable code.

3. Service Management via Systemd

CICD automatically registers your deployed application as a systemd service on Linux-based systems. This means your app will start on system boot and stay running, with automatic restarts in the event of failure.

4. SMTP-based Error Reporting

CICD integrates with SMTP to send error logs directly to the designated admin. When a failure occurs, a detailed report of the problem is sent, ensuring quick diagnostics and minimal downtime.

5. Multi-Language Support

CICD is language-agnostic and can be customized to deploy apps in various languages such as Node.js, Python, Go, and more. Configuration is as simple as providing a setup command for your specific project requirements.

6. MongoDB Integration for Deployment Tracking

CICD integrates with MongoDB to maintain deployment histories and keep track of which commit/version is deployed. This makes rollbacks and audits easier by retaining metadata related to the deployment process.

7. Advanced Customization for Different Environments

You can tailor deployments for staging, production, or testing environments using environment-specific configurations, allowing you to maintain multiple instances of your app with different configurations while using the same core tool.

8. Security-First Design

With encrypted Git credentials and support for secure webhook secrets, CICD ensures that your deployment pipeline is safe from unauthorized access.

Technical Comparison with Existing CI/CD Tools

Feature	CICD	GitLab CI/CD	Jenkins	CircleCI
One-Command Setup	Yes (minimal configuration)	Requires custom pipelines	Requires custom pipelines	Requires custom pipelines
Webhook Listener	Integrated (GitHub & GitLab support)	Requires manual setup	Requires manual setup	Requires manual setup
Systemd Integration	Built-in for Linux environments	Not available	Not available	Not available
Error Reporting (SMTP)	Integrated (via SMTP)	Requires external plugins	Requires plugins (e.g., Mailer)	Requires plugins
Service Monitoring	Included	Requires external plugins	Requires external plugins	Requires external plugins
Rollback Functionality	Planned for future versions	Available	Available	Available
Custom Environment Setup	Fully customizable for each environment	Limited to pipeline configuration	Requires scripting	Requires scripting
Multi-Language Support	Yes (Node.js, Python, Go, etc.)	Limited	Yes	Limited
Scalability	High (built for multi-environment scaling)	Medium	Medium	High
Ease of Use	Simple, one-command setup	Moderate complexity	Complex	Moderate complexity

Benefits to Developers

1. Reduced Complexity

With CICD, developers don't have to spend time building custom pipelines for deployment. The entire process from repository update to service restart is automated, leaving you free to focus on building features, not managing infrastructure.

2. Seamless Integration with Existing Tools

CICD integrates natively with GitHub and GitLab for webhooks, as well as MongoDB for version tracking. This gives developers a holistic and real-time view of what’s deployed without the need for multiple tools or dashboards.

3. Error-First Approach

Unlike many CI/CD tools that only focus on deployment, CICD ensures post-deployment monitoring and error detection, notifying developers immediately when something goes wrong. It minimizes the time it takes to identify and resolve issues.

4. Scalable and Flexible

CICD is highly adaptable to your growing infrastructure. It works across different environments, languages, and platforms, giving your team a consistent and scalable way to manage deployments for everything from small apps to enterprise-grade solutions.

Installation & Setup

To get started, clone the repository and run the setup script. In minutes, your environment will be configured and deployed:

git clone https://github.com/KTBsomen/cicd.git
cd cicd
python3 main.py --setup manual --repo-url <your-git-repo> --admin-email <your-email> --service-dir /home/your-service/

This will:

Clone your repository
Deploy the app
Set up environment configurations
Register the service using systemd for continuous monitoring

Future Roadmap

Rollback Functionality: Automated rollback to previous stable versions if a deployment fails.
Dashboard for Monitoring: A web-based UI for monitoring deployments, viewing logs, and managing services.
Multi-Cloud Deployments: Ability to deploy across multiple cloud providers (AWS, GCP, Azure) simultaneously.

How CICD Benefits Investors

For businesses, CICD ensures rapid and error-free deployment cycles, minimizing downtime and improving developer productivity. Its automation reduces infrastructure costs by removing the need for manual interventions in complex deployment environments. This results in faster time-to-market for new features and products, making it a vital tool in the competitive tech landscape.

Keywords: CI/CD, automated deployment, continuous integration, webhook listener, GitHub CI, real-time monitoring, service management, error reporting, multi-environment deployment, scalable CI/CD, infrastructure automation

currently in beta so give it a try and contribute to it.

I am creating the best UI framework.

somen das — Sat, 03 Aug 2024 08:47:16 +0000

Problem

So I hate react and every UI framework out there. I am a jQuery guy. So I come from that simplicity. I can't change my stack but I can't deny this frameworks offers many features.

so I want something simple which I can code in notepad no need to any faking setup script, build tools compilation steps, then a very heavy bundle to push to the client for eating there RAM and CPU and many more I can't tell now it's just a messed up thing now.

I can say we don't need any fricking UI framework

htmx is also a joke, as a backend developer we can't build a faking API for HTML response for web and also a JSON response for mobile,

solution:

I created a draft UI library.

this can be loaded with a script tag.
it offers automatic state change on variable change. and also you have full control over it.
everything is plain old HTML and javascript it's using custom web components under the hood.
you can also import other html files into another html file. they will act as templates with there own js scope as well as interact with main page.
lots of other small features I have already added more need to be added.

here is a demo website i built with this

everything is HTML based so just wget it to get the frontend code it's very simple.

If more of you people comments on this post and make it a wildfire the we will build a documentation. you should have to resonate with our ideas in the comments. or contact us.

I want you to contribute to this project so that this can be the final nail in the coffin. there should be no need for any new framework. world should be a better place.
Here is the GitHub link of the draft.

ILoveDevelopers

Level Up Your Node.js Performance with Mongoplusplus – The Ultimate MongoDB Load Balancer.

somen das — Sun, 05 May 2024 10:48:03 +0000

Introducing Mongoplusplus: Revolutionizing MongoDB Load Balancing for Node.js Developers

In the ever-evolving world of web development, efficient database management is crucial. Enter Mongoplusplus, a groundbreaking Node.js package designed to seamlessly manage read and write operations across multiple MongoDB databases. Here's why it could be the next big thing in your development toolkit.

Key Features:

Effortless Load Balancing:
- Automatically distribute database operations to optimize performance and reliability.
Simple Schema Definition:
- Leverages familiar Mongoose-like schema definitions, making it accessible for existing MongoDB users.
Robust CRUD Operations:
- Offers comprehensive methods for create, read, update, and delete operations across all databases.
Advanced Querying:
- Supports complex queries, including aggregation and real-time change watching, tailored for multi-database setups.
Developer-Friendly:
- Easy installation via npm, and clear, concise documentation to get you started quickly.

Getting Started:

Install via npm:

npm install mongoplusplus

Initialize and connect to your databases:

const mongoplusplus = require('mongoplusplus');
const mongodb = new mongoplusplus([mongoURI1, mongoURI2]);

(async () => {
  await mongodb.connectToAll();
})();

Define your schema:

const likeSH = mongodb.Schema({
  user_id: { type: mongoose.Schema.Types.ObjectId, required: true, ref: "users" },
  postId: { type: mongoose.Schema.Types.ObjectId, required: true  },
  dbIndex: { type: Number, required: true },
  like_time: { type: Date, default: Date.now }
});

Build and use your model:

const likes = mongodb.buildModel("likes", likeSH);
const result = await likes.findInAllDatabase({ name: 'John' }, { limit: 10 });

Why Mongoplusplus?

Mongoplusplus stands out by offering a robust, scalable solution for handling multiple MongoDB instances, simplifying complex database operations and improving overall application performance. Its intuitive API and powerful features make it an indispensable tool for modern Node.js developers.

Discover more about Mongoplusplus and start optimizing your MongoDB operations today!

Explore Mongoplusplus on npm

DEV Community: somen das

I added if-else & loops in HTML5

here is a full example

Combine multiple S3 storage

🎯 Why I'm Building This Package:

MultiBucket

Features

Installation

Dependencies

Basic Usage

Configuration Options

Constructor Options

Provider Configuration

Common Properties:

S3-specific Properties:

R2-specific Properties:

Load Balancing Strategies

External Configuration

API Endpoints

Generate Upload URL

Generate Read URL

Get Stats

Health Check

Programmatic Usage

License

Local MongoDB in Flutter 😱🤯

FlutterDB

Why do I build this?

Features

Installation

Getting Started

Basic Usage

Working with Collections

CRUD Operations

Create

Read

Update

Delete

Advanced Queries

Comparison Operators

Logical Operators

Text Search

Aggregation

Best Practices

Performance Optimization

Data Structure

Error Handling

Limitations

Complete Example

Future Enhancements

Contributing

License

Why Your Flutter App Needs `event_handeler`: A Fun, Powerful Alternative (and Companion) to State Management

🎩 What is event_handeler?

✨ Use Cases That Just Make Sense

1. 🚀 Triggering Actions from Background Pages

2. 🔄 Coordinating Across Screens

3. 🧪 Handling Events Once (and Only Once)

⚔️ event_handeler vs State Management Libraries

💡 When to Use It (and When Not To)

✅ Use It When:

🚫 Don’t Use It Alone If:

🔄 Using It With Riverpod or Provider

🧘‍♂️ Developer-Friendly Philosophy

🧪 Try It, Just Once

👇 Final Thoughts

new opensource tool 🔥 for one command server deployments and horizontal scaling.

CICD - Advanced Continuous Integration & Deployment for Modern Workflows

Why CICD?

1. Completely Automated Deployment Pipeline

2. Real-Time Code Monitoring with Webhook Integration

3. Dynamic Multi-Environment Setup

4. Automated Error Detection and Logging

5. Infrastructure-as-Code

Core Features

1. One-Command Setup

2. GitHub & GitLab Webhook Integration

3. Service Management via Systemd

4. SMTP-based Error Reporting

5. Multi-Language Support

🎩 What is `event_handeler`?

⚔️ `event_handeler` vs State Management Libraries