Skip to main content

Documentation: docs.machcomposer.io

MACH composer is a framework that you use to orchestrate and extend modern digital commerce & experience platforms, based on MACH technologies and cloud native services. It provides a standards-based, future-proof tool-set and methodology to hand to your teams when building these types of platforms.

It includes:

  • A configuration framework for managing MACH-services configuration, using infrastructure-as-code underneath (powered by Terraform)
  • A microservices architecture based on modern serverless technology (AWS Lambda and Azure Functions), including (alpha) support for building your microservices with the Serverless Framework
  • Multi-tenancy support for managing many instances of your platform, that share the same library of micro services
  • CI/CD tools for automating the delivery of your MACH ecosystem
  • Tight integration with AWS an Azure, including an (opinionated) setup of these cloud environments

The framework is intended as the 'center piece' of your MACH architecture and incorporates industry best practises such as the 12 Factor Methodology, Infrastrucure-as-code, DevOps, immutable deployments, FAAS, etc.

With combining (and requiring) these practises, using the framework has significant impact on your engineering methodology and organisation. On the other hand, by combining those practises we believe it offers an accelerated 'way in' in terms of embracing modern engineering practises in your organisation.

Getting started

Read our getting started guide on how to deploy your MACH stack with MACH composer.

Example yaml file

---
mach_composer:
  version: '1.2'
global:
  environment: test
  cloud: aws
  terraform_config:
    aws_remote_state:
      bucket: mach-tfstate-tst
      key_prefix: mach-composer-tst
      region: eu-central-1
sites:
  - identifier: my-site
    aws:
      account_id: 1234567890
      region: eu-central-1
    endpoints:
      public: api.tst.mach-example.net
    commercetools:
      project_key: my-site-tst
      client_id: ...
      client_secret: ...
      scopes: manage_project:my-site-tst manage_api_clients:my-site-tst view_api_clients:my-site-tst
      token_url: https://auth.europe-west1.gcp.commercetools.com
      api_url: https://api.europe-west1.gcp.commercetools.com
      project_settings:
        languages:
          - en-GB
          - nl-NL
        currencies:
          - GBP
          - EUR
        countries:
          - GB
          - NL
    components:
      - name: payment
        variables:
          STRIPE_ACCOUNT_ID: 0123456789
        secrets:
          STRIPE_SECRET_KEY: secret-value
components:
  - name: payment
    source: git::ssh://git@github.com/your-project/components/payment-component.git//terraform
    endpoints:
      main: public
    version: e638e57

Installation

  • Make sure you have Terraform 0.14 installed (tip: Use tfenv to support multiple versions of Terraform)
  • Create a new virtualenv with Python 3.8
  • Run the following commands:
$ make install

Running MACH

To generate the files:

mach generate # generates all available configs.

mach generate -f main.yml

To init Terraform (optional):

mach init

To plan Terraform:

mach plan

To apply Terraform config:

mach apply

Checking for updates

MACH can check your components for available updates.

To do this, run:

mach update -f main.yml

Contributing

Code style

The Python source code should be formatted using black and the JavaScript code should be formatted using prettier. You can use make format to run both black and prettier.

This project uses pre-commit to validate the changed files before they are committed. You can install it on MacOS using brew:

$ brew install pre-commit

In the repository you need to register the hooks in git the first time using:

$ pre-commit install

The pre-commit config (.pre-commit-config.yaml) currently runs black and flake8.

Metadata

Release files for mach-composer 1.2.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mach-composer 1.2.4
File Size Uploaded Provenance Actions
mach-composer-1.2.4.tar.gz 38.9 kB Without provenance Details for mach-composer-1.2.4.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for mach-composer 1.2.4
File Interpreter ABI Platform Actions
mach_composer-1.2.4-py3-none-any.whl Python 3 none any Details for mach_composer-1.2.4-py3-none-any.whl

Total release size: 90.9 kB

Release files / mach-composer-1.2.4.tar.gz

Download URL mach-composer-1.2.4.tar.gz
Size 38.9 kB
Tags Source
SHA-256 checksum
How to use checksums
d1fb264d72838e670af9074fd37cfe69e3cf82e5bb67d494b28bb930509ee89a
BLAKE2b-256 checksum
How to use checksums
1a73ae19cb50cb052a0bccd1f0e82216f53a0c430b99b0b00b85105b4eaac7d9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.6.0 importlib_metadata/4.11.2 pkginfo/1.8.1 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.1

Release files / mach_composer-1.2.4-py3-none-any.whl

Download URL mach_composer-1.2.4-py3-none-any.whl
Size 52.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
371b1fd98a98de2568b062c2bb4a2286938f6a6e56571ec5e4fba77658cd3e79
BLAKE2b-256 checksum
How to use checksums
8ce4d23fd1830f6ce747b6d92f604ceddfe468c9a069927d56699034306789fa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.6.0 importlib_metadata/4.11.2 pkginfo/1.8.1 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.1

Security for mach-composer 1.2.4

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page