People may want to host their own instance of this store, especially in light of issue #15. There are currently no instructions on how to do so.
While the code could be checked out and copied over to a web server, it would not be easy to keep updated with this repo. In addition, the host may want to just have a page on their site which is their store and not have the MagicWebStore branding visible to customers.
Requirements
The desired functionality for this use case is to be able to:
A. manage a store (add/remove items, check for orders, etc.)
B. allow people to shop at the store
C. allow the shoppers to only see what's in the store; no explanations about magic strings, Nostr relays or anything else
Implementation
I suggest checking out the git repo into a directory under the webroot on the web server. Getting updates can be as simple as a git pull.
The code for the store will all be in a directory (e.g. superstore) which need not be linked from anywhere on the site, thus the customers do not need to see any branding. Meanwhile, the seller can manually navigate to that directory and it's no big deal to have them see the branding.
Here's an example setup:
example.com: main site
example.com/store.html: this is a symlink to superstore/index.html
example.com/store/superstore: git checkout of this repo
Closing this ticket should just be a matter of documenting how one could set this up and how to get updates.
Side note
Having this would also help other developer (like me) in contributing to this project. This would allow developers to set up their own test store where they can make code changes and test out those changes before submitting pull requests.
Problem
People may want to host their own instance of this store, especially in light of issue #15. There are currently no instructions on how to do so.
While the code could be checked out and copied over to a web server, it would not be easy to keep updated with this repo. In addition, the host may want to just have a page on their site which is their store and not have the MagicWebStore branding visible to customers.
Requirements
The desired functionality for this use case is to be able to:
A. manage a store (add/remove items, check for orders, etc.) B. allow people to shop at the store C. allow the shoppers to only see what's in the store; no explanations about magic strings, Nostr relays or anything else
Implementation
I suggest checking out the git repo into a directory under the webroot on the web server. Getting updates can be as simple as a
git pull.The code for the store will all be in a directory (e.g. superstore) which need not be linked from anywhere on the site, thus the customers do not need to see any branding. Meanwhile, the seller can manually navigate to that directory and it's no big deal to have them see the branding.
Here's an example setup:
Closing this ticket should just be a matter of documenting how one could set this up and how to get updates.
Side note
Having this would also help other developer (like me) in contributing to this project. This would allow developers to set up their own test store where they can make code changes and test out those changes before submitting pull requests.