- clone
yarn
ornpm install
to install dependenciesyarn dev
ornpm run dev
to start local server- Open http://localhost:3000 with your browser to see the result.
This is a Next.js project bootstrapped with create-next-app
.
First, run the development server:
npm run dev
# or
yarn dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying pages/index.js
. The page auto-updates as you edit the file.
API routes can be accessed on http://localhost:3000/api/hello. This endpoint can be edited in pages/api/hello.js
.
The pages/api
directory is mapped to /api/*
. Files in this directory are treated as API routes instead of React pages.
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.
- robinwieruch.de/graphql-apollo-server-tutorial
- GraphQL with MongoDB
- Docker for local development with hot-reloading
- AWS CoPilot for Amazon ECS
Docker Setup source
docker build -t workout-docker:0.1 .
docker run -p 3000:3000 workout-docker:0.1
- Post workouts
- Follow other users
- Mark workouts as favorites
- Display some sort of timeline
- Workouts only contain text
- Search for a workout and or user
- Workout posts can contain photos
- Tags maybe?
- Comments on a workout?
- Trending workouts?
- Tag users?
- Follow/workout suggestions
- Dockerize app
- Deploy to aws
- Implement username password login
- remove the methods using mock data and use data from the database
- Local Storage or firebase hook to persist auth
- https://firebase.google.com/docs/reference/js/v8/firebase.auth.Auth#onauthstatechanged
- I think I also want to send a re-authenticate to the graphql api when the user changes their user info, so we can use the data from the graphql mutation, rather than having two states for the user info
- Global Error boundary to catch errors