The live marketplace online - A product built to make shopping online more interactive by combining live streaming with small business e-commerce.
Please excuse the mess. We're working here 👷♀️
We've made the repository public, but we're still working on this README and the wiki.
CircleCI:
http://sulo-demo.us-east-1.elasticbeanstalk.com
The demo includes the full web application for both visitors and logged in users. We are using an in-memory database, so you are welcome to play around and make any changes you want.
- Database: Since the demo can be used by anyone, expect changes you make to stick around for a while. We might reset the demo sometimes, but we don't have a schedule for that.
- Login: In the code you'll see our implementation a passwordless login flow using Auth0. We're bypassing that flow in the demo to let anyone login and see the shop owner's UI.
- Payments: Stripe was integrated as the payment service. We use our own fake version of Stripe in this demo, so any functionality involving payments might not behave as expected (you'll not be charged money at any point).
- Live streaming: To save on costs, we had to shut down our streaming server. You'll see an animated example video in place of the streams.
- Photo uploads: Again to save costs, we are on a free tier with our photo storage service and have a limit on uploading photos. Expect any photo uploads to not work properly.
When learning Clojure, it was useful to look at CircleCI's open sourced frontend, just to see how a real project can be structured, which problems they need to solve and how they compose libraries as well as hacks to make things work. As our startup isn't running anymore, we hope that our code can be helpful to someone - just as CircleCI's code was helpful to us. The entire frontend and server is available as well as a skeleton for a react-native app. We've even included all the scripts we used to deploy the product, so you can even take a look at them.
- Fullstack om.next
- Web, Mobile and Server
- Datomic and Datascript with a unified API
- Server side rendering
- Fullstack testing
- Client and Server code reloading on code change
We've described our experience working with an om.next, datascript and datomic architecture in the github wiki. The pages contain ideas, problems and solutions that we've had to figure out, and we've included links and code example where it made sense to us.
We'll start with the more general stuff that might help you in your next project:
- Handling remote responses
- Restricting client queries
- Composable datalog queries
- Single point of server calls & git rebase app state
- Datomic queries returning as little as possible
- Component & om.next shared
- Full stack testing
- Datascript string search
- Datomic database functions used from normal code
- Pagination
- SEO
- Optimizing Server side rendering
- Clone this project
git clone [email protected]:eponai/sulolive.git - Navigate to the cloned sulolive/ folder
cd sulolive
- Start server repl:
lein repl** Initialize local server:eponai.repl=> (start-server)
- Start web client repl:
rlwrap lein figwheel-web - Open Browser and navigate to:
localhost:3000