Skip to content

Latest commit

 

History

History
130 lines (97 loc) · 3.31 KB

README.md

File metadata and controls

130 lines (97 loc) · 3.31 KB
Raw

Vee-API

Background

We as Indonesian people usually still calculate the expense that comes from our vehicle manually, by gathering all bills that came from gas stations. We usually calculate the total expenses from all bills at the end of the month. Our problem led us to our ideas in this project. To build an integrated mobile app for tracking the expenses from our vehicle. Later on, this app will be our everyday’s partner when using our vehicle.

Documentation

TODO

  • Gethering requirements for cloud solutions, design, and architectures
  • Developing API Backend using NodeJs
  • Configuring GCP Project, budget, and API
  • Hosting database Postgre SQL to Cloud SQL
  • Deploy API Backend to APP engine
  • Build CI/CD for API Backend Development using Cloud BUild
  • Deploy Machine Learning to Compute Engine with Load Balancer
  • Monitoring running resources from GCP

GCP Resources

  • App Engine : to host api
  • Cloud SQL : to host postgre sql
  • cloud build : ci/cd
  • cloud repository : ci/cd
  • secret manager : save key or credential
  • Monitoring : creating alert for sql and app engine cpu utilization
  • API Places : search nearby gas station
  • Cloud Run : deploy api for ml
  • Compute Engine : deploy api for ml mode (more low latency)

Local Installation Instructions

Fork and clone the forked repository:

git clone git://github.com/<your_fork>/Vee-API

Navigate into cloned repository:

cd Vee-API

Install all required packages:

npm install

Run the NodeJS API:

npm run start

API will run on http://localhost:5000

GCP Deployment Instructions

Fork and clone the forked repository in cloud shell, enable API and right permission.

git clone git://github.com/<your_fork>/Vee-API

Query for postgre:

create extension cube;
create extension earthdistance;

GRANT ALL PRIVILEGES ON DATABASE veeapp TO developer;
GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA public TO developer;

CREATE TABLE public.users (
	id varchar(50) NOT NULL,
	firstname text NOT NULL,
	lastname text NULL,
	email text NOT NULL,
	"password" text NULL,
	CONSTRAINT users_email_key UNIQUE (email),
	CONSTRAINT users_pkey PRIMARY KEY (id)
);

CREATE TABLE public.authentications (
	"token" text NOT NULL
);

CREATE TABLE public.activities (
	id varchar(50) NOT NULL,
	"date" date NOT NULL,
	lat float8 NULL,
	lon float8 NULL,
	km int4 NOT NULL,
	price int4 NOT NULL,
	liter float4 NOT NULL,
	"owner" varchar(50) NOT NULL,
	CONSTRAINT activities_pkey PRIMARY KEY (id)
);

ALTER TABLE public.activities ADD CONSTRAINT "fk_activities.owner_users.id" FOREIGN KEY ("owner") REFERENCES public.users(id) ON DELETE CASCADE;

CREATE TABLE public.gasstations (
	id varchar(50) NOT NULL,
	"name" text NOT NULL,
	lat float8 NULL,
	lon float8 NULL,
	vendor text NOT NULL,
	operate bool NOT NULL,
	time_create int8 NOT NULL,
	CONSTRAINT gasstations_pkey PRIMARY KEY (id)
);

Move to project directory:

cd Vee-API

Deploy to appengine:

gcloud app deploy