luismts

Git Commit Best Practices

Basic Rules

Commit Related Changes

A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.

Commit Often

Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.

luismts

Enhancements and Desired Features for Directus: Contributing to the Platform's Future

Directus is an open-source content management system that offers exceptional flexibility in creating custom content interfaces. The community surrounding Directus plays a vital role in its evolution and continuous improvement. One of the most effective ways to influence the development of this platform is through requesting new features or improvements.

Through GitHub, the Directus team values the contributions and suggestions from the community. This article aims to compile a list of features and enhancements that could further drive the utility and versatility of Directus.

🚀 Your Voice Matters! Join and Support these Key Enhancements for Directus 🌟

Features:

luismts

Docker Best Practices

• Keep containers stateless.
• Use COPY instead of ADD.
• Make COPY last line before CMD or ENTRYPOINT.
  • Each line in the Dockerfile is cached.
  • Separate COPY of requirements.txt from source code.
• CMD vs ENTRYPOINT: ENTRYPOINT is the main command. Treat CMD as the default flag for the entrypoint. Example:

luismts

rest-api-response-format

REST API response format based on some of the best practices

Rest API Popular Endpoint Formats

https://api.example.com/v1/items

https://example.com/api/v1/items

Rest API Success Responses

luismts

#!/bin/bash
echo "
----Commands aliases for Docker Compose
alias dc='docker-compose'
alias dcps='docker-compose ps'
alias dcstart='docker-compose start'
alias dcstop='docker-compose stop'
alias dcup='docker-compose up -d'

----Commands aliases for Docker

luismts

.elementor-widget-price-table, .elementor-widget-price-table>div, .elementor-price-table {
    height: 100%;
}

.elementor-price-table {
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
    -webkit-box-orient: vertical;
    -webkit-box-direction: normal;

luismts

/**
 * PHP version 5
 * @package    AzulPaymentGateway
 * @author     ideologic SRL <touch@ideologic.do>
 * @since      File available since Release 1
 */
	 
<?php namespace App;
// use Illuminate\Database\Eloquent\Model;
// use DB;

luismts

To remove a submodule you need to:

• Delete the relevant section from the .gitmodules file.
• Stage the .gitmodules changes git add .gitmodules
• Delete the relevant section from .git/config.
• Run git rm --cached path_to_submodule (no trailing slash).
• Run rm -rf .git/modules/path_to_submodule (no trailing slash).
• Commit git commit -m "Removed submodule "
• Delete the now untracked submodule files rm -rf path_to_submodule

luismts

<?xml version="1.0" encoding="UTF-8"?>
<ScrollView 
    xmlns="http://xamarin.com/schemas/2014/forms" 
    xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" 
    x:Class="Project.Controls.BindableScrollableStackLayout">
    
    <StackLayout x:Name="stackLayout" />
        
</ScrollView>

luismts

public class BaseModel
{
    public Guid Id { get; set; }
        
    public DateTime CreateDate { get; set; }
    public bool IsActive { get; set; }
    public string LastUpdatingUserName { get; set; }
    public DateTime LastUpdatingDate { get; set; }        
}