---
title: "2FA Recovery Codes, Nixpacks Beta, and Community Call Summary"
date: 2022-05-06T14:00:00.000-04:00
number: 0080
url: https://railway.com/changelog/2022-05-06
---

# 2FA Recovery Codes, Nixpacks Beta, and Community Call Summary

## 2FA Recovery Codes

If you have ever lost access to an authentication app then we have the feature for you! You can now generate and save 2FA recovery codes that can be used in place of the standard 2FA code. The codes are only visible to you once and afterwards are fully encrypted on our side. Codes can only be used a single time and you can regenerate all codes which will invalidate all previous ones.

When setting up 2FA for the first time you are prompted to save the codes. But if you already have 2FA setup then you can go to [railway.app/account/security](https://railway.app/account/security) to generate recovery codes for the first time.

[Image: Untitled]

## Nixpacks Beta

Nixpacks, our alternative to the Heroku and Paketo buildpacks, is now available for priority boarding users as a builder on Railway. Just go to the service settings and select it.

There are still a lot of improvements we would like to make, such as smaller image sizes,  more fine-grained package versions, support for more languages, and much more. But we know there is stuff that we are missing which is why we would like your feedback! Please submit bug reports and feature requests to the #priority-boarding channel on Discord or create an issue on [the Nixpacks repo](https://github.com/railwayapp/nixpacks/issues). The project is also open-source and contributions are welcome 😄. There are also some docs and [getting started instructions](https://github.com/railwayapp/nixpacks#getting-started) for those who want to run Nixpacks locally.

Over the next few weeks, we will continue to add features and make the UX of using Nixpacks top-notch.

[Image: Untitled]

As a reminder, you can join the priority boarding program by going to [our Discord](https://discord.gg/railway) and typing `/beta`.

## Community Call Summary

This morning we hosted our first community call and we thank every last person who made it out (bright and early on PST).

We covered a lot of ground and you can see a list of the questions [here](https://app.sli.do/event/cR93Fb2ohppvVw7Dd2pveH/live/questions). Additionally mentioned is we’re well aware of the “disjoint-ness” between the Canny and the our roadmap. We’ve gone ahead and moved all our roadmap over to our internal knowledge base in Notion, and will be making this more publicly available in the future. Stay tuned!

[For those unable to attend: we have a blog post that summarizes the common questions asked and offers a state of our roadmap. ](https://blog.railway.app/p/community-call-wrap)

## Improvements and Fixes

- Do not require project PR deploys to be enabled to update service from upstream
- Enable branch deletion when updating starters via PR
- Fix confirmation modal on mobile devices
- Improve team discord channel creation experience
- Improved feedback when adding a service domain fails
- Show team projects above user projects on dashboard
- Reduce number of requests the dashboard makes