-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CW2-24 Setup Backend #12
Conversation
MVP Resources and Contacts Page
Sponsors
* Add formatting and linting * Add github workflow
CW2-5 Sponsors Page Draft/Template
* added events template * removed section * modified events to coordinate with navbar on click --------- Co-authored-by: Stuart Cutbush <[email protected]> Co-authored-by: Derek Xu <[email protected]>
* changed the h1 tags * changed image alt tags * changed tailwind * CW2-3 Add events section (#4) * added events template * removed section * modified events to coordinate with navbar on click --------- Co-authored-by: Stuart Cutbush <[email protected]> Co-authored-by: Derek Xu <[email protected]> * changes to make linter approve * formatted code? --------- Co-authored-by: Stuart Cutbush <[email protected]> Co-authored-by: Derek Xu <[email protected]>
CW2-7-move-social-media-to-footer
…te-2023 into CW2-24-Setup-backend
|
||
export default function EventsPage() { | ||
const pingBackend = async () => { | ||
axios |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't intend to make this the norm for calling APIs - this was just for MVP
Later I will abstractify the API calling logic in a "middleware" per se
frontend/.env.production
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't intend to keep this in the repo for long - again, just for MVP
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
I've rewritten the README.md
in line with the new changes, feel free to have a quick look and see if there is anything you would like to add / change.
Otherwise, happy to merge
Significant change to the fundamental structure of the repo - adding in the Express backend.
Now the structure of the repo is a monorepo, with
docker-compose.yml
in the base directory, and subdirectories for/frontend
and/backend
./ping
endpoint to verify connectionbackend