sr9yar

#!/bin/bash
echo '# Running apt-get update ...'
apt-get update
echo '# Installing imagemagick ...'
apt-get install -y imagemagick
echo '# Installing blender ...'
apt-get install -y software-properties-common
add-apt-repository -y ppa:thomas-schiex/blender
apt-get install -y blender
echo '# Installing python-pip ...'

sr9yar

FROM ubuntu:bionic

RUN \
  apt-get update && \
  apt-get -y upgrade && \
  apt-get install -y python3 python3-pip python3-dev python3-setuptools ca-certificates nano

RUN \
  cp /usr/bin/python3.6 /usr/bin/python && \
  cp /usr/bin/pip3 /usr/bin/pip

sr9yar

Writing Magento Modules

All custom modules should have a Namespace and Module Name. These are used below as {Namespace} and {Module}.

Caution: The Magento autoloader is known to have problems with CamelCase namespaces and/or modules between Windows and *nix systems. If your module requires more than one word for either of these, it is best to just concatenate them to avoid any issues (Example: {Namespace}_{Examplemodule}).

Index

• Directory Structure

sr9yar

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Principal": "*",
            "Action": [
                "s3:ListBucket",
                "s3:GetBucketLocation"
            ],

sr9yar

Keybase proof

I hereby claim:

• I am sr9yar on github.
• I am sr9yar (https://keybase.io/sr9yar) on keybase.
• I have a public key ASBDwStsY3cFBvc4vGB0iMGHrciiN2-kJG9ll3mjlQeIlAo

To claim this, I am signing this object: