kwmiebach

Usage

(Create a symlink pytest for py.test)

pytest [options] [file_or_dir] [file_or_dir] ...

Help:

ConduciveMammal

<div class="product-item__container">
{% raw %}
{{#unless productAvailable}}
  <span class="badge soldout">
    <span class="badge-label soldout">Sold out</span>
  </span>
{{/unless}}
{{#if onSale}}
  {{#unless soldOut}}

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.

vamshigvk

rmiyazaki6499

Deploying a Production ready Django app on AWS

In this tutorial, I will be going over to how to deploy a Django app from start to finish using AWS and EC2. Recently, my partner Tu and I launched our app Hygge Homes (a vacation home rental app for searching and booking vacation homes based off Airbnb) and we wanted to share with other developers some of the lessons we learned along the way.

Following this tutorial, you will have an application that has:

• An AWS EC2 server configured to host your application
• SSL-certification with Certbot
• A custom domain name
• Continuous deployment with Github Actions/SSM Agent

enamhasan

# add this script in product liquid (Just before addtocart form)

<!-- Code added for Inventory in Pipeline -->            
                <script>       
                  var inv_qty = {};
                  {% for var in product.variants %}
                    inv_qty[{{- var.id -}}] = {{ var.inventory_quantity | default: 0 }};
                  {% endfor %}
                </script>            
                {% if current_variant.inventory_management == "shopify" %}

atikju

<div class='relatedArticles'>
  {% for tag in article.tags %}

  {% assign counter = 0 %}
  {% assign skip_articles = article.handle | split: '.....' %}
  {% for related_article in blog.articles %}
    {% if related_article.tags contains tag and counter < 6 %}
      {% unless skip_articles contains related_article.handle %}
        {% assign counter = counter | plus: 1 %}
        {% assign temp = related_article.handle | split: '.....' %}

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: