meetings/ 20250416.md

@@ -1,5 +0,0 @@
-[design]
-
-- To change up the colors / test it out with black purple white and see how that goes
-- On user login, checks if it's a new user or not, if yes, popup appears to to ask user if this npub is a normal user/consumer or producer (this would affect how their profile page works, and a product cannot review any other product / they can just publish product)
-- There's two profiles, one user and one producer

meetings/20250326.md

@@ -1,3 +0,0 @@
-- Use MongoDB instead of Cassandra.
-- Add precommit hook checking licenses of the third-party libraries.
-- Add CI/CD step to double-check licenses of the third-party libraries.

meetings/20250409.md

@@ -1,11 +0,0 @@
-[design]
-
-- Edit the design of of initial search in hero section in the landing page (remove search bard, and all selections: product, type, style, characteristic, location (this one specifically has filter checkboxes in its popup) [search button]), popups remain.
-- don't change navigation bar
-- round corners where seemed appropriate, like buttons and maybe tags
-- add / change review submission to include a lengthy selection process, and present it
-- - to also have a summary design of total reviews (excluding text reviews of course)
-- reply system/style is similar to deg mods (popup depth system)
-- remove "Seller Name's Latest Products" section
-- Add "Product Details" or "Details" tab (last tab) after reviews/comments
-- Publishing a review costs money, replying (normal commenting/replying) to review doesn't (free), and commenting is also free

meetings/20250423.md

@@ -1,8 +0,0 @@
-# Product
-
-- `Producer` can modify product only during 24 hours after submition.
-- `Producer` can delete product at any time.
-
-# Review
-
-- `Reviwer` can modify review only during 24 hours after submition.

server-configuration/staging.md

@@ -1,236 +0,0 @@
-# Server configuration of the staging server
-
-Staging server has `51.161.134.20` IP address and `staging.cellar.social` DNS record associated with it.
-
-`otto` user has sudo rights at staging server, all operations that require sudo rights will be performed under this user.
-
-## Fail2ban
-
-Install `fail2ban` to scan the log files for too many failed login attempts and block the IP address which is showing malicious signs.
-
-```bash
-sudo apt-get install fail2ban
-```
-
-## Nginx
-
-Under `otto` user:
-
-```bash
-# Update packages
-sudo apt update
-
-# Install Nginx
-sudo apt install nginx
-
-# List the application configurations that ufw knows how to work with
-sudo ufw app list
-
-# Activate firewall
-sudo ufw enable
-
-# Allow ssh connections
-sudo ufw allow 'OpenSSH'
-
-# Allow HTTPS traffic
-sudo ufw allow 'Nginx HTTPS'
-
-# Allow HTTP traffic (HTTP traffic should be allowed to equire SSL certificate and will be disabled later)
-sudo ufw allow 'Nginx HTTP'
-
-# Check ufw status
-sudo ufw status
-
-# Check Nginx status
-systemctl status nginx
-
-# Create the directory for `api` domain
-sudo mkdir -p /var/www/api/html
-
-# Assign ownership of the directory to the `api` user
-sudo chown -R api:api /var/www/api/html
-
-# Adjust permissions
-sudo chmod -R 755 /var/www/api
-
-# Install certbot
-sudo apt install certbot python3-certbot-nginx
-
-# Fetch a certificate from Let's Encrypt and follow the prompts
-sudo certbot --nginx -d staging.cellar.social
-
-# Verify that certificate renewal is on
-sudo systemctl status certbot.timer
-
-# Create a configuration file for api subdomain
-sudo nano /etc/nginx/sites-available/api
-```
-
-Paste into `/etc/nginx/sites-available/api`:
-
-```bash
-server {
-    listen 80;
-    listen [::]:80;
-
-    root /var/www/html;
-    index index.html index.htm index.nginx-debian.html;
-
-    # Put your domain name here
-    server_name staging.cellar.social;
-
-    # Needed for Let's Encrypt verification
-    location ~ /.well-known/acme-challenge {
-	    allow all;
-    }
-
-    # Force HTTP to HTTPS
-    location / {
-	    return 301 https://$http_host$request_uri;
-    }
-}
-
-server {
-    listen 443 ssl http2;
-
-    ssl on;
-
-    # SSL certificate by Let's Encrypt in this Nginx
-    ssl_certificate      /etc/letsencrypt/live/staging.cellar.social/fullchain.pem;
-    ssl_certificate_key  /etc/letsencrypt/live/staging.cellar.social/privkey.pem;
-
-    # root /var/www/html;
-    # index index.html index.htm index.nginx-debian.html;
-
-    # domain name here
-    server_name staging.cellar.social;
-
-    location /api/ {
-	proxy_pass http://127.0.0.1:3000/;
-
-	proxy_set_header Host $http_host;
-	proxy_set_header X-Forwarded-Proto $scheme;
-	proxy_set_header X-Real-IP $remote_addr;
-	proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-
-	proxy_set_header Upgrade $http_upgrade;
-    }
-
-    # Needed for Let's Encrypt verification
-    location ~ /.well-known/acme-challenge {
-	allow all;
-    }
-}
-```
-
-Next:
-
-```bash
-# Enable the file by creating a link from it to the sites-enabled directory, which Nginx reads from during startup
-sudo ln -s /etc/nginx/sites-available/api /etc/nginx/sites-enabled/
-
-# Restart Nginx
-sudo systemctl restart nginx
-
-# Check Nginx status
-systemctl status nginx
-
-# Check firewall status
-sudo ufw status
-
-# Deny HTTP traffic
-sudo ufw deny 'Nginx HTTP'
-
-# Check firewall status
-sudo ufw status
-```
-
-## Install Node and NPM
-
-```bash
-# Update packages
-sudo apt update
-
-# Install nvm (node version manager)
-curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.3/install.sh | bash
-
-# Install Node v20
-nvm install 20.12.2
-
-# Set 20.12.2 as a default version of Node
-nvm alias default 20.12.2
-
-# Use default Node version
-nvm use default
-```
-
-## API user
-
-`api` user doesn't have sudo rights and will be used to run `cellar-api` and all related processes.
-
-Under `otto` user:
-
-```bash
-# Create api user
-sudo adduser api
-
-# Switch to api user
-su api
-```
-
-Under `api` user:
-
-```bash
-# Generate SSH keys.
-# These keys will be used by CI/CD pipeline.
-ssh-keygen
-
-# Change to ssh directory
-cd .ssh/
-
-# Create authorized_keys file
-touch authorized_keys
-
-# Copy public key from `id_ed25519.pub` and paste into `authorized_keys` file
-# Private key is stored in SSH_STAGING_PRIVATE_KEY variable of the CI/CD pipeline.
-
-# Install PM2 package globally
-npm i -g pm2
-
-# Clone cellar/cs-backend repository
-git clone ssh://git@git.nostrdev.com:29418/cellar/cs-backend.git
-
-# Change to cs-backend directory
-cd cs-backend
-
-# Install dependencies
-npm ci
-
-# Build API app
-npm run build
-
-# Start API app
-npm run start
-
-# Verify that cellar-api process is running
-pm2 list
-```
-
-## Docker
-
-Under `otto` user:
-
-```bash
-# Install docker
-curl -fsSL https://get.docker.com | sudo sh
-
-# Add api user to the docker group so it can run docker without sudo rights
-sudo usermod -aG docker api
-```
-
-Under `api` user:
-
-```bash
-# Log in to docker group to avoid to log out and log in again
-newgrp docker
-```

technical-design.md

@@ -87,7 +87,7 @@ The backend app will also manage Npub whitelisting that `APP Relay` will use.
 
 #### Database
 
-[MongoDB Community Edition](https://www.mongodb.com/products/self-managed/community-edition) will be used as a NoSQL database (`DB`) to persist business data. Only the backend app will have access to the database.
+[Cassandra](https://cassandra.apache.org/_/index.html) will be used as a NoSQL database (`DB`) to persist business data. Only the backend app will have access to the database.
 
 The following tables are planned in the database: