No description
- Elixir 97.3%
- Python 1.3%
- Nix 1.2%
- Shell 0.2%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
Renovate
96f15684a4
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [hackney](https://hex.pm/packages/hackney) ([source](https://github.com/benoitc/hackney)) | prod | patch | `4.8.1` → `4.8.2` | --- ### Release Notes <details> <summary>benoitc/hackney (hackney)</summary> ### [`v4.8.2`](https://github.com/benoitc/hackney/releases/tag/4.8.2): hackney 4.8.2 [Compare Source](https://github.com/benoitc/hackney/compare/4.8.1...4.8.2) ##### Fixed - A connection opened without a pool is owned by the process that opened it and closes when that process dies. It was started under `hackney_conn_sup` and owned by it, so a killed caller left the connection and its socket open until the server closed it (`idle_timeout` defaults to `infinity`). Covers `request/5` and `connect/*` with `{pool, false}`, streamed request bodies, async responses, HTTP proxies, CONNECT and SOCKS5 tunnels, HTTP/2 and HTTP/3, and `h2_open/*` streams. With `stream_to`, the `stream_to` process owns the connection, as before. `hackney_conn:set_owner/2` still moves ownership. - An HTTP/1.1 connection waiting for a response closes within a second of its owner dying. It was blocked in the socket read and noticed only when the response came, the server closed, or `recv_timeout` expired. - A CONNECT or SOCKS5 tunnel socket belongs to its connection. It stayed with the process that opened it, so after `hackney_conn:set_owner/2` it still closed when that process died. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMTUuMTAiLCJ1cGRhdGVkSW5WZXIiOiI0NC4xMTUuMTAiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbXX0=--> Reviewed-on: #85 |
||
| .forgejo/workflows | ||
| .vscode | ||
| config | ||
| lib | ||
| priv/repo | ||
| test | ||
| .credo.exs | ||
| .editorconfig | ||
| .formatter.exs | ||
| .gitignore | ||
| deps-hash.txt | ||
| deps-hash.txt.doc | ||
| flake.lock | ||
| flake.nix | ||
| mix.exs | ||
| mix.lock | ||
| README.md | ||
| register_discord_command.py | ||
| renovate.json | ||
| run.sh | ||
SpaceAgeApi
To start your Phoenix server:
- Install dependencies with
mix deps.get - Create and migrate your database with
mix ecto.setup - Start Phoenix endpoint with
mix phx.server
Now you can visit localhost:4000 from your browser.
Ready to run in production? Please check our deployment guides.
Learn more
- Official website: http://www.phoenixframework.org/
- Guides: https://hexdocs.pm/phoenix/overview.html
- Docs: https://hexdocs.pm/phoenix
- Mailing list: http://groups.google.com/group/phoenix-talk
- Source: https://github.com/phoenixframework/phoenix