Overview Spree Commerce is one of the best open source e-commerce platform written in Ruby language. It boasts of its feature completeness coupled with a vast ecosystem of extensions and quick pace of development. SpreeOnReact is an open source SpreeCommerce front-end solution … Continue reading
Category Archives: E-Commerce
As a potential customer of an ecommerce store, a big assurance and confidence boost for me is to see testimonials from existing customers. If you want to add this capability to your Spree store, there is help available. We extracted … Continue reading
As an eCommerce business you can do better than your competition by allowing your customers to customize product that they want to order. Of course not all products can be customized but if you deal in a product which renders itself … Continue reading
When it comes to marketing it’s important to target the right people. Say, you have the perfect marketing strategy for increasing retention or just the right content for promoting a product. What else do you need for a successful marketing … Continue reading
You will learn how to Build an exrm release for NectarCommerce and a quick heads-up on roadblocks and their solutions. It will help you do a dry run in development and production environment on local for less surprises when deployed for use. Continue reading
In the past few posts we have learned how to write code that extends existing models, routers, added methods to override view rendering and run multiple phoenix application together in the same umbrella project. Let’s Continue to build upon that and write our first extension for NectarCommerce favorite products and ultimately our store based on NectarCommerce.
For our curious readers, we tried another extension approach which had linear dependency (nectar => extensions_manager => extensions) helpful in development but turned out to had the serious limitation of Nectar being unavailable for testing.
To overcome the barrier of testing and pleasant developer workflow, what we need is that Nectar is available and compiled while developing extensions and if an extension is added it should recompile itself to include the new extensions.
We have modified Nectar for this approach to seek for extensions and used a custom compiler step(A story for another time) to mark files for recompilation. Let’s get started and see if we can scale the testing barrier.
It’s a walk-through of Extension Approach which has simple, linear dependency (nectar => extensions_manager => extensions) between Nectar, Extensions and Extension Manager and developing an extension is also quite straightforward but turned out to have the serious limitation of Nectar being unavailable for testing. Continue reading
This post aims at documenting how the approach we took to make NectarCommerce extensible is structured, the order of dependencies amongst the various nuts and bolts of NectarCommerce and its extensions as implemented.
NectarCommerce can be divided in two components, both of which reside in the same umbrella application.
We want to allow Extensions to add routes into Nectar Router without modifying the Nectar Router source.
Let’s begin the journey of incremental changes to bring consumer, service and library code into existence starting from a simple use-case of adding a route for showing favorites.
We want to allow Extensions to add support functions to existing Nectar Models without changing the Nectar Models.
Let’s begin the journey of incremental changes to bring consumer, service and library code into existence starting from a simple use-case of adding a function, say
fn_from_outside, to Nectar Product.