* add initial testing files * prepare for github * remove empty files * remove ids * set user and password for postgres service * remove node setup * remove unused flag from yarn install * correct medusajs package * arguments for create-medusa project * make create command into one line * working directory update * update workflow * add build * run scripts from medusa-cli * move scripts to medusa-cli * add install * get server output * rename build to install * update login script to get feedback * add arguments to login script * add argument for directory to get-product * pass cli-test to get-products script * add wait command * fix waiting * update wait-for-server * echo status * update start testing * refactor code into test-action * add list config for testing * include shell * update get-products script * test to see if action fails when given wrong input * use custom action for testing devleopment server and extend waiting for server to spin up * update actions * remove cache version * yarn and build in cli-test directory * update core * update working directories * test working dir after cd up * update * fix directories * update directories * use setup server action * invoke correct action * test * update cli action * remove action * test with medusa-dev * remove medusa dev for now * test * include medusa-dev * remove invalid medusa new command * try moving project one dir up * add silent to curl output from live server wait * update seed data directory * test * remove sub workflow * add matrix and postgres override for medusa-config * fix matrix syntax * add database url to job * update yaml * cli should fail on logging in * create setup server action * update test-server * update scripts * run scripts directory instead of cli scripts * make directories current * remove tests from cli * run only on pr * update name * remove batch job model (for testing purposes) * remove ls from test server action * get content from develop * undo changes to generate reference * remove comments from scripts * test failing command * redo migrate command failing * move scripts into interation tests * Apply suggestions from code review Co-authored-by: Oliver Windall Juhl <59018053+olivermrbl@users.noreply.github.com> Co-authored-by: Oliver Windall Juhl <59018053+olivermrbl@users.noreply.github.com>
Medusa
Medusa Admin | Website | Blog | LinkedIn | Twitter | Documentation | Notion
Medusa is an open-source headless commerce engine that enables developers to create amazing digital commerce experiences.
Quickstart
- Install Medusa CLI
npm install -g @medusajs/medusa-cli - Create a new Medusa project
medusa new my-medusa-store --seed - Start your Medusa engine
medusa develop - Use the API
curl localhost:9000/store/products | python -m json.tool
We have a prebuilt admin dashboard that you can use to configure and manage your store find it here: Medusa Admin
After these four steps and only a couple of minutes, you now have a complete commerce engine running locally. You may now explore the documentation to learn how to interact with the Medusa API. You may also add plugins to your Medusa store by specifying them in your medusa-config.js file.
Roadmap 2022
Write-ups for all features will be made available in Github discussions prior to starting the implementation process.
H1 2022
- Admin revamp
- Tax API
- Tax Calculation Strategy
- Cart Calculation Strategy
- Customer Groups API
- Promotions API
- Price Lists API
- Price Selection Strategy
- Bulk import / export
- Extended Product API (custom fields, publishing control, and more)
- Extended Order API (managing placed orders, improved inventory control, and more)
- Sales Channel API
- Multi-warehouse support
- GraphQL API
Setting up a storefront for your Medusa project
Medusa is a headless commerce engine which means that it can be used for any type of digital commerce experience - you may use it as the backend for an app, a voice application, social commerce experiences or a traditional e-commerce website, you may even want to integrate Medusa into your own software to enable commerce functionality. All of these are use cases that Medusa supports - to learn more read the documentation or reach out.
To provide a quick way to get you started with a storefront install one of our traditional e-commerce starters:
- Gatsby Starter
npm install -g gatsby-cli gatsby new my-medusa-storefront https://github.com/medusajs/gatsby-starter-medusa - Nextjs Starter
npx create-next-app -e https://github.com/medusajs/nextjs-starter-medusa my-medusa-storefront
With your starter and your Medusa store running you can open http://localhost:8000 (for Gatsby) or http://localhost:3000 (for Nextjs) in your browser and view the products in your store, build a cart, add shipping details and pay and complete an order.
Features
Medusa comes with a set of building blocks that allow you to create amazing digital commerce experiences, below is a list of some of the features that Medusa come with out of the box:
- Headless: Medusa is a highly customizable commerce API which means that you may use any presentation layer such as a website, app, chatbots, etc.
- Regions allow you to specify currencies, payment providers, shipping providers, tax rates and more for one or more countries for truly international sales.
- Orders come with all the functionality necessary to perform powerful customer service operations with ease.
- Carts allow customers to collect products for purchase, add shipping details and complete payments.
- Products come with relevant fields for customs, stock keeping and sales. Medusa supports multiple options and unlimited variants.
- Swaps allow customers to exchange products after purchase (e.g. for incorrect sizes). Accounting, payment and fulfillment plugins handle all the tedious work for you for automated customer service.
- Claims can be created if customers experience problems with one of their products. Plugins make sure to automate sending out replacements, handling refunds and collecting valuable data for analysis.
- Returns allow customers to send back products and can be configured to function in a 100% automated flow through accounting and payment plugins.
- Fulfillment API makes it easy to integrate with any fulfillment provider by creating fulfillment plugins, check the
/packagesdirectory for a full list of plugins. - Payments API makes it easy to integrate with any payment provider by creating payment plugins, we already support Stripe, Paypal and Klarna.
- Notification API allow integrations with email providers, chatbots, Slack channels, etc.
- Customer Login to give customers a way of managing their data, viewing their orders and saving payment details.
- Shipping Options & Profiles enable powerful rules for free shipping limits, multiple fulfillment methods and more.
- Medusa's Plugin Architecture makes it intuitive and easy to manage your integrations, switch providers and grow with ease.
- Customization is supported for those special use cases that all the other e-commerce platforms can't accommodate.
Database support
In production Medusa requires Postgres and Redis, but SQLite is supported for development and testing purposes. If you plan on using Medusa for a project it is recommended that you install Postgres and Redis on your dev machine.
To use Postgres and Redis you should provide a database_url and redis_url in your medusa-config.js.
Contribution
Medusa is all about the community. Therefore, we would love for you to help us build the most robust and powerful commerce engine on the market. Whether it is fixing bugs, improving our documentation or simply spreading the word, please feel free to join in. Please check our contribution guide for further details about how to contribute.
Repository structure
The Medusa repository is a mono-repository managed using Lerna. Lerna allows us to have all Medusa packages in one place, and still distribute them as separate NPM packages.
Licensed
Licensed under the MIT License