Write someting meaningful about your project!
If it's your first time using react-admin then the official docs offer a 30min tutorial that's great to get up and running quickly.
yarnTo get started with the project, run yarn in the root directory to install the required dependencies for each package.
yarn startTo run the app in development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
yarn lint --fixTo fix formatting errors.
This project comes with CI/CD pipelines setup out of the box using Bitbucket Pipelines.
These pipelines are:
- lint every pull request
- build and deploy staging on push
- build and deploy master on push
How do we handle deploys? We do so with AWS S3 and CloudFront. S3 hosts all the static files that make up your build and CloudFront serves them in a way that allows us to set up SSL certificates (HTTPS) and enhance performance because CloudFront is, in its core, a CDN.
These pipelines work if certain variables are set in your repository, required variables are:
AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAWS_DEFAULT_REGIONS3_BUCKET_MASTERDISTRIBUTION_ID_MASTERS3_BUCKET_STAGINGDISTRIBUTION_ID_STAGING
Variables named S3_BUCKET_<branch> are just there to hold the name of the bucket created to hold static files, DISTRIBUTION_ID_<branch> variables are there to hold the CloudFront distribution ID. Why do we need the latter? Because if you are caching responses to requests received by CloudFront (which you should) you need to invalidate that cache so you get the latest content, if you don't you'll see old content even after a deploy.