Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

646 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

peony

A content management system and shoping cart API.

Goals

peony is a headless ecommerce software designed to satisfy publishers, merchants and service providers.

peony aims to be multi-language, multi-channel, multi-currency, multi-warehouse, and support physical, virtual products and services.

Get started

Clone the starter and customize it to fit your needs.

Architecture

This graph represents how peony works on a single-server deployment. This setup may scale horizontally by deploying each box on its own independent server.

                    ┌──────────────────────┐ ┌───────────┐
 ┌────────────────┐ │        peony         │ │           │
 │                │ │                      ◄─► providers │
 │ Admin frontend ◄─►     ┌─────────┐      │ │           │
 │                │ │     │         │      │ └───────────┘
 └────────────────┘ │     │   API   │      │ ┌────────┐   
                    │     │         │      │ │        │   
                    │     └─────────┘      ◄─► Redict │   
                    │                      │ │        │   
 ┌────────────────┐ │     ┌──────────┐     │ └────────┘   
 │                │ │     │          │     │ ┌──────────┐ 
 │ Store frontend ◄─►     │  worker  │     │ │          │ 
 │                │ │     │          │     ◄─► Firebird │ 
 └────────────────┘ │     └──────────┘     │ │          │ 
                    └──────────────────────┘ └──────────┘ 

peony is a commerce backend. It consists of an API and a worker. The API and worker portions may be combined (for example, in a single-server deployment) or separated (for example, in a horizontally scaled system).

Data is persisted on a Firebird database, and Redict is used for cache, job queues and events. Other core components (called providers) are swappable: implement the provider interface to replace a provider.

Environment variables

If a .env file exists, peony will read it and use the variables provided in the file. Please look at the provided .env.template file for more information.

About

CMS and commerce API

Topics

Resources

Contributing

Stars

7 stars

Watchers

1 watching

Forks

Contributors

Languages