| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
* use GraphQL API instead of REST (the inconvenient however is that we
now need an authorization token...)
* move fetcher in services
* add tests
* mock response using MSW
|
| |
|
|
|
|
| |
I also added a custom script to deploy the services with Docker Swarm.
Without it, Docker cannot read the `.env` file. Since I'm using a
variable to define the registry, the script is required.
|
| |
|
|
|
|
| |
It will be useful with Docker. Instead of cloning the project with a
different configuration, I can manage two different configuration
thanks to dotenv and some checking inside the app.
|
| |
|
|
|
|
|
|
|
|
|
| |
* build: add experimental feature outputStandalone
With this option, Next.js can create a standalone folder with the
necessary files for a production deployment. It will be useful for
Docker deployment.
* chore: add Docker configuration
* docs: update README with Docker instructions
|
| |
|
|
|
| |
I do not use all Matomo features so I was searching a lightweight
analytics tools. I will give a try to Ackee.
|
| |
|
|
|
| |
I also renamed and changed the format of some environment variables so
I can reuse them inside the CSP security header.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Instead of using post slug and an environment variable to fetch repo
data, I use the given repo in each project MDX file. It allows me to
fetch data from another user/organization if needed.
To make it work, I no longer provide the full URL in MDX file. The new
format is: "User/repo-slug".
I also replaced the fetch method with SWR to improve caching and to
avoid React complaining about cleanup useEffect.
|
| | |
|
| |
|
|
| |
I also added the featured image on single article.
|
| |
|
|
|
|
| |
I could loop until hasNextPage is false, but I'm not sure if it is the
best solution. So, for now, only the first 100 posts will be added to
the file.
|
| |
|
