## Description
**What issue are you solving (or what feature are you adding) and how
are you doing it?**
`warp-input.yml` workflow was not getting invoked on push. So, I change
the `Github Token` which has broader permissions.
## Description
**What issue are you solving (or what feature are you adding) and how
are you doing it?**
Well, I tried doing a release and it did not go as expected, due to some
issues with the git_token plus concurrency. So, i have fixed that... let
us do a re-release.
## Description
**What issue are you solving (or what feature are you adding) and how
are you doing it?**
We cannot use golang for our input binary as we will be redoing the
Webtransport stack, plus we will have to use CGO in-order to hook into
X11. Like what [neko](https://github.com/m1k1o/neko) does.
However, we could go down the Rust route, where X11 mouse/keyboard
drivers are in pretty, and moq-rs (the MoQ library using Webtransport)
works really well. So, that is what am trying to do here; implement
input using rust.
Bumps
[svenstaro/upload-release-action](https://github.com/svenstaro/upload-release-action)
from 2.7.0 to 2.9.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/svenstaro/upload-release-action/releases">svenstaro/upload-release-action's
releases</a>.</em></p>
<blockquote>
<h2>2.9.0</h2>
<ul>
<li>Allow seeting a release as draft <a
href="https://redirect.github.com/svenstaro/upload-release-action/pull/112">#112</a>
(thanks <a
href="https://github.com/ShonP40"><code>@ShonP40</code></a>)</li>
</ul>
<h2>2.8.0</h2>
<ul>
<li>Bump all deps</li>
<li>Update to node 20</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/svenstaro/upload-release-action/blob/master/CHANGELOG.md">svenstaro/upload-release-action's
changelog</a>.</em></p>
<blockquote>
<h2>[2.9.0] - 2024-02-22</h2>
<ul>
<li>Allow seeting a release as draft <a
href="https://redirect.github.com/svenstaro/upload-release-action/pull/112">#112</a>
(thanks <a
href="https://github.com/ShonP40"><code>@ShonP40</code></a>)</li>
</ul>
<h2>[2.8.0] - 2024-02-21</h2>
<ul>
<li>Bump all deps</li>
<li>Update to node 20</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="04733e069f"><code>04733e0</code></a>
This is 2.9.0</li>
<li><a
href="7b5b755e5b"><code>7b5b755</code></a>
Add CHANGELOG entry for <a
href="https://redirect.github.com/svenstaro/upload-release-action/issues/112">#112</a></li>
<li><a
href="17449a21ea"><code>17449a2</code></a>
Add draft release support (fixes <a
href="https://redirect.github.com/svenstaro/upload-release-action/issues/19">#19</a>)</li>
<li><a
href="ec2ff03a5a"><code>ec2ff03</code></a>
Amend CHANGELOG</li>
<li><a
href="ff23fb2574"><code>ff23fb2</code></a>
This is 2.8.0</li>
<li><a
href="8e438350b0"><code>8e43835</code></a>
Bump all deps</li>
<li><a
href="fe68892921"><code>fe68892</code></a>
Merge pull request <a
href="https://redirect.github.com/svenstaro/upload-release-action/issues/113">#113</a>
from svenstaro/dependabot/npm_and_yarn/babel/traverse...</li>
<li><a
href="a13e7b5d40"><code>a13e7b5</code></a>
Merge pull request <a
href="https://redirect.github.com/svenstaro/upload-release-action/issues/116">#116</a>
from der-eismann/update-to-node20</li>
<li><a
href="a4bae284e7"><code>a4bae28</code></a>
Update to node20</li>
<li><a
href="c19ddf4c20"><code>c19ddf4</code></a>
Bump <code>@babel/traverse</code> from 7.22.8 to 7.23.2</li>
<li>Additional commits viewable in <a
href="https://github.com/svenstaro/upload-release-action/compare/2.7.0...2.9.0">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>
## Description
**What(what issue does this code solve/what feature does it add):**
Dependabot does not have a `build` semver type and it keeps triggering
the autolabeller. So, i added that in there, plus slimmed down the
pull_request_template as it required too much info, which made it too
cumbersome filling it
## Description
**What(what issue does this code solve/what feature does it add):**
Build times for netris:server are way too long. so the idea is to move
warp into it's own container then build from there.
Later on first release we might drop this for a better solution.
**How(how does it solve it):**
1. Added the very own netris:warp
## Required Checklist:
- [x] I have added any necessary documentation and comments in my code
(where appropriate)
- [x] I have added tests to make sure my code runs in all contexts
## Further comments
## Description
**What(what issue does this code solve/what feature does it add):**
We do not need the ffmpeg and recorder all sitting differently, as this
will increase our docker image size
**How(how does it solve it):**
## Required Checklist:
- [ ] I have added any necessary documentation and comments in my code
(where appropriate)
- [ ] I have added tests to make sure my code runs in all contexts
## Further comments
## Description
**What(what issue does this code solve/what feature does it add):**
`Warp` will be used to "trasmit" the video and audio from the container
to the user/viewer wherever they are.
**How(how does it solve it):**
1. Add a Github worker that builds warp on pr, and one that builds and
pushes on release
## Required Checklist:
- [ ] I have added any necessary documentation and comments in my code
(where appropriate)
- [ ] I have added tests to make sure my code runs in all contexts
## Further comments
## Description
**What(what issue does this code solve/what feature does it add):**
**How(how does it solve it):**
## Required Checklist:
- [ ] I have added any necessary documentation and comments in my code
(where appropriate)
- [ ] I have added tests to make sure my code runs in all contexts
## Further comments
## Description
**What(what issue does this code solve/what feature does it add):**
So, we have our simple compositor (`gamescope`), now we need a way to
capture audio and video.
And i have found this "performant" **_citation needed_ ** and minimal
screen recorder, which has the capability to even capture 30 second
screen snippets.
**How(how does it solve it):**
1. Add a minimal step inside the DockerFile to build and install the
gpu-screen-recorder
## Required Checklist:
- [ ] I have added any necessary documentation and comments in my code
(where appropriate)
- [ ] I have added tests to make sure my code runs in all contexts
## Further comments
## Description
**What(what issue does this code solve/what feature does it add):**
Add a way to configure the Nvidia GPU, by installing the necessary
packages for Proton to work.
**How(how does it solve it):**
We made a script `.scripts/gpu` when called like `gpu -c` it will
install Vulkan and proprietry nvidia drivers.
## Required Checklist:
- [ ] I have added any necessary documentation and comments in my code
(where appropriate)
- [ ] I have added tests to make sure my code runs in all contexts
## Further comments
## Description
**What(what issue does this code solve/what feature does it add):**
We are adding the `Dockerfile` with all the scripts and programs to run
our games in.
**How(how does it solve it):**
1. Add `serverDockerfile` which contains all the docker code.
2. Add `.scripts` folder where we will store all the scripts; for
example in our case, where proton installation script will reside.
## Required Checklist:
- [ ] I have added any necessary documentation and comments in my code
(where appropriate)
- [ ] I have added tests to make sure my code runs in all contexts
## Further comments
## Description
**What(what issue does this code solve/what feature does it add):**
We are adding the `Dockerfile` to build a moq-relay
**How(how does it solve it):**
1. Added `relay.Dockerfile` with all the docker code to build
kixelated's moq-relay.
2. Added `relay.yml` in workflows for building and publishing the docker
image
## Required Checklist:
- [ ] I have added any necessary documentation and comments in my code
(where appropriate)
- [ ] I have added tests to make sure my code runs in all contexts
## Further comments
