docs: added technical design #3
@ -23,13 +23,13 @@ Cellar Social will provide the following capabilities:
|
||||
- Order the product.
|
||||
- Engage with product related community.
|
||||
- Provide NIP-05 names.
|
||||
- View and sign on to events.
|
||||
- View and sign up to in-person events.
|
||||
y marked this conversation as resolved
Outdated
|
||||
|
||||
## Design
|
||||
|
||||
Cellar Social consists of the backend and frontend apps supported by the database and the relay.
|
||||
|
||||
All hosted services will be containerised and deployed to the linux ([Ubuntu](https://ubuntu.com/)) server and traffic routing will be manged by [Nginx](https://nginx.org/). The entire server should be backed up daily.
|
||||
All hosted services will be containerised and deployed to the linux ([Ubuntu](https://ubuntu.com/)) server and traffic routing will be manged by [Nginx](https://nginx.org/). The entire server should be backed up (at the host level) daily.
|
||||
y marked this conversation as resolved
Outdated
b
commented
Backups will happen at the host level, right? Backups will happen at the host level, right?
y
commented
yes yes
|
||||
|
||||
Cellar Social will also use an external service ([nostr.build](http://nostr.build/)) for media hosting to avoid inappropriate data.
|
||||
|
||||
@ -95,7 +95,7 @@ The following tables are planned in the database:
|
||||
- Reviews
|
||||
- NostrEvents
|
||||
|
||||
Database has to be backed up daily.
|
||||
Database has to be backed up (at the host level) daily.
|
||||
|
||||
### Relay
|
||||
y marked this conversation as resolved
b
commented
maybe a description of how this will work - eg, a javascript function injection on the relay event listener, which calls maybe a description of how this will work - eg, a javascript function injection on the relay event listener, which calls `GET /user/verify/$npub` or sth like that
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user
sign UP to in-person events