Tags: corentin703/firezone
Tags
fix(relay): don't busy-loop on `poll_timeout` (firezone#4497) The value returned from `poll_timeout` needs to only reset the `Sleep` but don't need to go back to the top of the loop. Instead, we move its polling to below the resetting of `Sleep`. This will correctly register a waker in case we did change `Sleep`. This `continue` causes a busy-loop and stops the relay from dealing with the `phoenix-channel` which means the portal will eventually consider it offline. This was first introduced in firezone#4455.
chore(connlib): remove `Mutex` from windows TUN device (firezone#4472) This is a legacy from before the single-threaded connlib design.
fix(portal): Serve static files with digests at root (firezone#4386) Closes firezone#4384
refactor: Reduce log levels for production releases to avoid filling … …customer's… (firezone#3899) Tuning the logging down a bit on our production releases. Prevents gathering data we don't need to be gathering and prevents filling up drive space with debug logs. refs firezone#3618
fix(portal|website): Fix static paths for website and elixir (firezon… …e#3802) Phoenix VerifiedRoutes expects directories for `statics` where we were passing filenames too. These are removed since they're not required -- all of the top level files we need to serve at the root don't need VerifiedRoutes. For the website, the files were named incorrectly. The above issues were causing 404s on both the website and portal.
fix(windows): work around possible keyring multi-threading bug for now ( firezone#3363) Co-authored-by: Jamil <[email protected]>
feat(devops): Add CoreDNS to AWS TF (firezone#3351) Why: * The CoreDNS server that had been running in AWS was not yet ported over to use the new AWS Terraform in the mono repo.
feat(devops): Add AWS terraform (firezone#3298) Why: * Previously the terraform for all of the AWS infra was created and run outside of the mono repo. While this was very quick to setup and work with, keeping the gateway up to date was easy to forget about. Moving all of the AWS infra TF into the mono repo will allow everything to stay up to date and will make sure everyone has easy access to update any of the infra as needed. --------- Co-authored-by: Jamil <[email protected]>
PreviousNext