c90bb1f898
Bumps [date-fns](https://github.com/date-fns/date-fns) from 3.6.0 to 4.0.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/date-fns/date-fns/blob/main/CHANGELOG.md">date-fns's changelog</a>.</em></p> <blockquote> <h2>v4.0.0 - 2024-09-16</h2> <p>I have great news! First, ten years after its release, date-fns finally gets first-class time zone support.</p> <p>Another great news is that there aren't many breaking changes in this release. All of them are type-related and will affect only those explicitly using internal date-fns types. Finally, it has been less than a year since the last major release, which is an improvement over the previous four years between v2 and v3. I plan on keeping the pace and minimizing breaking changes moving forward.</p> <p><a href="https://blog.date-fns.org/v40-with-time-zone-support/">Read more about the release in the announcement blog post</a>.</p> <p>- <a href="https://twitter.com/kossnocorp"><code>Sasha @kossnocorp</code></a></p> <h3>Added</h3> <ul> <li> <p>Added time zones support via <a href="https://github.com/date-fns/tz"><code>@date-fns/tz</code></a>'s <code>TZDate</code> class and <code>tz</code> helper function. See its <a href="https://github.com/date-fns/tz">README</a> for the details about the API.</p> </li> <li> <p>All relevant functions now accept the context <code>in</code> option, which allows to specify the time zone to make the calculations in. If the function also returns a date, it will be in the specified time zone:</p> <pre lang="ts"><code>import { addDays, startOfDay } from "date-fns"; import { tz } from "@date-fns/tz"; <p>startOfDay(addDays(Date.now(), 5, { in: tz("Asia/Singapore") }));<br /> //=> "2024-09-16T00:00:00.000+08:00"<br /> </code></pre></p> <p>In the example, <code>addDays</code> will get the current date and time in Singapore and add 5 days to it. <code>startOfDay</code> will inherit the date type and return the start of the day in Singapore.</p> </li> </ul> <h3>Changed</h3> <ul> <li> <p>The function arguments, as well as <code>Interval</code>'s <code>start</code> and <code>end</code>, now can be of different types, allowing you to mix <code>UTCDate</code>, <code>TZDate</code>, <code>Date</code>, and other extensions, as well as primitives (strings and numbers).</p> <p>The functions will normalize these values, make calculations, and return the result in the same type, preventing any bugs caused by the discrepancy. If passed, the type will be inferred from the context <code>in</code> option or the first encountered argument object type. The <code>Interval</code>'s <code>start</code> and <code>end</code> will be considered separately, starting from <code>start</code>.</p> <p>In the given example, the result will be in the <code>TZDate</code> as the first argument is a number, and the <code>start</code> takes precedence over the <code>end</code>.</p> <pre lang="ts"><code>clamp(Date.now(), { start: new TZDate(start, "Asia/Singapore"), end: new UTCDate(), }); //=> TZDate </code></pre> </li> <li> <p><strong>BREAKING</strong>: This release contains a bunch of types changes that should not affect the library's expected usage. The changes are primarily internal and nuanced, so rather than listing them here, I recommend you running the type checker after the upgrade. If there are unfixable problems, please <a href="https://github.com/date-fns/date-fns/issues/new">open an issue</a>.</p> </li> <li> <p><strong>BREAKING</strong>: The package now is ESM-first. The CommonJS is still support and It should not affect most users, but it might break in certains environments. If you encounter any issues, please <a href="https://github.com/date-fns/date-fns/issues/new">report them</a>.</p> </li> </ul> <h3>Fixed</h3> <ul> <li>Fixed CDN build compatibility with jQuery and other tools that expose <code>$</code> by properly wrapping the code in an IIFE.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/date-fns/date-fns/commits">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Demo · Documentation · Quickstart · GitHub · Releases
Tournament system meant to be easy to use. Bracket is written in async Python (with FastAPI) and Next.js as frontend using the Mantine library.
It has the following features:
- Supports single elimination, round-robin and swiss formats.
- Build your tournament structure with multiple stages that can have multiple groups/brackets in them.
- Drag-and-drop matches to different courts or reschedule them to another start time.
- Various dashboard pages are available that can be presented to the public, customized with a logo.
- Create/update teams, and add players to teams.
- Create multiple clubs, with multiple tournaments per club.
- Swiss tournaments can be handled dynamically, with automatic scheduling of matches.
Live Demo
A demo is available for free at https://www.bracketapp.nl/demo. The demo lasts for 30 minutes, after which your data will de deleted.
Quickstart
To quickly run bracket to see how it works, clone it and run docker compose up:
git clone git@github.com:evroon/bracket.git
cd bracket
sudo docker compose up -d
This will start the backend and frontend of Bracket, as well as a postgres instance. You should now be able to view bracket at http://localhost:3000. You can log in with the following credentials:
- Username:
test@example.org - Password:
aeGhoe1ahng2Aezai0Dei6Aih6dieHoo.
To insert dummy rows into the database, run:
sudo docker exec bracket-backend pipenv run ./cli.py create-dev-db
See also the quickstart docs.
Development setup
Read the development docs for how to run Bracket for development.
Prerequisites are yarn, postgresql and pipenv to run the frontend, database and backend.
Configuration
Read the configuration docs for how to configure Bracket.
Bracket's backend is configured using .env files (prod.env for production, dev.env for development etc.).
But you can also configure Bracket using environment variables directly, for example by specifying them in the docker-compose.yml.
The frontend doesn't can be configured by environment variables as well, as well as .env files using Next.js' way of loading environment variables.
Running Bracket in production
Read the deployment docs for how to deploy Bracket and run it in production.
Bracket can be run in Docker or by itself (using pipenv and yarn).
Translations
Based on your browser settings, your language should be automatically detected and loaded. For now, there's no manual way of choosing a different language.
Supported Languages
- 🇺🇸 English
en- Default - 🇨🇳 Chinese
zh- Contributed by @Sevichecc - 🇳🇱 Dutch
nl- Contributed by @evroon - 🇪🇸 Spanish
es- Autogenerated - 🇩🇪 German
de- Autogenerated
To add/refine translations, Crowdin is used. See the docs for more information.
More screenshots
Help
If you're having trouble getting Bracket up and running, or have a question about usage or configuration, feel free to ask. The best place to do this is by creating a Discussion.
Supporting Bracket
If you're using Bracket and would like to help support its development, that would be greatly appreciated!
Several areas that we need a bit of help with at the moment are:
- ⭐ Star Bracket on GitHub
- 🌐 Translating: Help make Bracket available to non-native English speakers by adding your language (via crowdin)
- 📣 Spread the word by sharing Bracket to help new users discover it
- 🖥️ Submit a PR to add a new feature, fix a bug, extend/update the docs or something else
See the contribution docs for more information on how to contribute
Contributors
Erik Vroon |
Null |
BachErik |
Danny Piper |
SevicheCC |
IzStriker |
License
Bracket is licensed under AGPL-v3.0.
Please note that any contributions also fall under this license.
See LICENSE