gatsby-starter-shopify VS gatsby-london

GitHub source

Link to your store Follow these instructions here to link your Shopify store. Create a .env file with your Shopify store URL, password, and Storefront access token, using the .env.example file as an example. If you want to try with a development store, see the sample data and instructions here.

Would you say gatsby-shopify-starter is generally a good place to start wirh Gatsby & Shopify?

Are you referring to the payment processing being done at a Shopify's domain instead of the original one? Like how on this gatsby-shopify-demo when clicking checkout it's redirected to https://gatsby-dev-30k-sku.myshopify.com/56348803256/checkouts/....?

Update: I actually realised that I didn't have nginx-proxy container running! However I'm still having issues accessing pages that are served via SSR.. i.e. '/search', when running 'gatsby serve' behind the nginx reverse proxy. I just get a 404. I can access '/search' when running locally (on port 9000) but not when it's dockerized. I'm aware it may be the case that SSR in Gatsby refers to service rendering purely to produce a build but when I build and deploy the static assets to be served under nginx '/search' still produces a 404. In a nutshell '/search' doesn't work unless being accessed by 'gatsby serve' with no reverse proxy. I've been voicing my troubles on this GitHub ticket: https://github.com/gatsbyjs/gatsby-starter-shopify/issues/57

I absolutely love Gatsby, but more so for marketing sites. When it comes to Ecommerce, Gatsby developed a Shopify starter: https://github.com/gatsbyjs/gatsby-starter-shopify

If you feel like using Gatsby instead, the other store I linked can be forked from here.

My budget for now is around 1000-1100$. Because this project is without design and styling, and because there is a huge Gatsby Shopify Starter I think a lot of work has already been done.

GitHub source