fac-11 / myspace Goto Github PK

View Code? Open in Web Editor NEW

0.0 5.0 0.0 13.71 MB

A travel review website for space

Home Page: https://myspace-taja.herokuapp.com/

License: MIT License

JavaScript 47.60% HTML 16.08% PLpgSQL 18.62% CSS 17.70%

myspace's Introduction

Myspace: a travel review website for space 🌏 🚀 🌞

because in space no one can hear you Yelp

User stories

On the welcome page I can search for planetary destinations by their distance from Earth
As a user I can a list of clickable search results, or choose to view all the options
As a user I can view individual planet pages and:
- I can upvote planets
- I can see reviews and add my own reviews
- I can rate reviews, good or bad
SG I can log in
SG I can see a map of the planets

Requirements

Build an app using the Express framework.
Use a PostgreSQL database to store and retrieve your data.
Use the retrieved data to populate a Handlebars template for server-side rendering to be displayed on the front-end.
Include tests and set up code coverage.
Use Heroku or a similar service to host the app and the database.
Try to include ES6 syntax on the server.

Architecture

Put the database folder in the model folder.

Schema

Planets

Column	Type
id	serial primary key
name	varchar(20)
distance	float
description	text
temperature	integer
weather	varchar(200)
interest	integer
filename	varchar(40)
thumbnailname	varchar(40)

Reviews

Column	Type
id	serial primary key
planet_id	integer references planets(id)
user	varchar(20)
content	text
likes	integer
dislikes	integer

Setup

To setup myspace with a database running on a local installation of PostgreSQL,

createdb myspace
sudo -u postgres createuser majortom
sudo -u postgres createdb myspace ```
and in `psql`,

GRANT ALL PRIVILEGES ON DATABASE myspace TO majortom ; ALTER USER majortom WITH PASSWORD 'milkymilkyway'; ``` Create a config.env for the project if you don't have one already and add to it the line

DB_TEST_URL = postgres://majortom:milkymilkyway@localhost:5432/myspace

Finally build the database:

npm run dbinit

Learnings & Links

Express makes most things simpler but routing in express carries its own new risk of bugs.
transform-origin is kewl.
:after allows you to define CSS properties to be applied after others, so they will take effect no matter what the properties are changed to previously.

myspace's People

Contributors

Watchers

myspace's Issues

Write comprehensive readme

With schema, user stories, approach, flows and learnings.

Write index.js

Write partials: footer

Testing setup

@ameliejyc @azayneeva We discussed this already but for historical note I think in the future rather than replicate your entire database setup for testing I would suggest changing the connection in dbuild depending on the desired environment

Basic db_build.sql

as per spec

Pics

Your assets should all be save together in the folder served by your express.static middleware without outlying files in your handlebars directory

Write planet.js in controllers

How to run your project locally

It would be good to include quick start instructions in the README.md with the environment variables which I will need for the project.

See dangerdak/interstellar-soulmates#33 and dangerdak/interstellar-soulmates#34

Populate index.html

Write planet.hbs

Write thumbs up and down handlers

Use handlebars each method

https://github.com/FAC-11/myspace/blob/master/src/views/home.hbs#L7 could have been written in a DRYer way.

Something like this:

{{#each ["5", "10", "15", "20", "25", "30"]}}
    <li><button class="distance-li__link" name="distance" value="{{this}}" onclick="window.location.href='/results/{{this}}'">{{this}}au</button></li>
{{/each}}

Or something like that. This is quite a trivial example, but making more use of these helpers in general will help your projects

Write error.hbs

Write app.js

Populate style.css

Write partials: htmlHead

Set up file structure and download all dependencies

Write database queries

Set up Heroku

Write home.hbs

SQL Queries

When it comes to SQL queries it is best to write out the full queries even if it leads to verbosity rather than attempt to compose or concatenate strings as in practice your sql would be written for all the different situations and used where necessary.