Skip to content

Latest commit

 

History

History
69 lines (52 loc) · 1.79 KB

README.md

File metadata and controls

69 lines (52 loc) · 1.79 KB

prototype

Hive prototype, lihive meets rust backend

Requirements

  • rust/cargo
  • nodejs
  • a Firebase project w/ Authentication setup
    • Sign-in providers enabled:
      • Google
      • Anonymous
  • a Postgres database
  • Diesel CLI

Running locally

  1. Setup a Firebase project as defined above, making note of its Web API key, project ID, and project auth domain
  2. Create an .env.local file for the frontend:

js/frontend/.env.local

NEXT_PUBLIC_FIREBASE_API_KEY=
NEXT_PUBLIC_FIREBASE_AUTH_DOMAIN=
NEXT_PUBLIC_FIREBASE_PROJECT_ID="
  1. Run the nextjs dev server. This is configured to proxy /api requests to the rust backend
$ npm install
$ npm run --workspace js/hive-lib build
$ npm run --workspace js/frontend dev
  1. Create a .env file for the backend:

backend/.env

DATABASE_URL=              # whatever the connection string for your Postgres database is
TEST_DATABASE_URL=         # whatever the connection string for your Postgres test databse is, needed for cargo test to work 
FIREBASE_JWT_ISSUER=       # this should be "https://securetoken.google.com/<projectId>", where projectId is your firebase project ID as above
STATIC_FILES_PATH=./dist   # we'll set this up in a moment
  1. Create the static files directory
mkdir backend/dist
  1. Run the Diesel migrations, if you haven't already:
$ cd backend
$ diesel migration run
  1. Run the backend server:
$ cd backend
$ cargo run
  1. Go to http://localhost:3000 (the nextjs dev server's url)

Previous works

lihive frontend by atdyer

hive rust backend by klautcomputing