Files
bracket/docs
BachErik be2ec7d9dd fix: publish docker image workflow (#830)
After many tests, I have now discovered that there is currently a
problem with node and arm64 in GitHub workflows. There is the following
issue: https://github.com/nodejs/docker-node/issues/1335. As already
mentioned at the top of the Node.js issue, a possible solution would be
to run it in offline mode, i.e. to cache the packages.

I have now adapted the GitHub workflow file so that it already works.
As you have already correctly noted, I have added QEMU.

Since this problem only affects Node, the backend is not affected and
already has the multi-architecture variant. To give the frontend
multi-arch as well, you would only have to add `linux/arm64` to the
platform, and then it should also work there.

But I still have a question: Why do you not work with the versions in
the workflow file, but with special commits?

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2024-07-29 09:17:30 +02:00
..
2024-05-05 09:35:06 +02:00
2024-02-04 21:00:52 +01:00
2023-04-18 20:41:07 +02:00
2023-11-27 21:46:41 +01:00
2023-11-27 21:46:41 +01:00
2023-11-27 21:46:41 +01:00

Website

This website is built using Docusaurus 2, a modern static website generator.

Installation

yarn

Local Development

yarn start

This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.

Build

yarn build

This command generates static content into the build directory and can be served using any static contents hosting service.

Deployment

Using SSH:

USE_SSH=true yarn deploy

Not using SSH:

GIT_USER=<Your GitHub username> yarn deploy

If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.