---
title: "Config as Code Beta, Redeploy Button, Updated Context Menu GA"
date: 2022-10-21T15:00:00.000+00:00
number: 0104
url: https://railway.com/changelog/2022-10-21-config-as-code-beta
---

# Config as Code Beta, Redeploy Button, Updated Context Menu GA

Have you [joined Priority Boarding](https://docs.railway.app/reference/priority-boarding) yet? No? Well, what are you waiting for? Are you waiting for us to invite you? You’re already invited!

## Config as Code

[Image: Untitled]

Up to this point, we’ve only supported configuration within the service settings panel in the UI. 

In this release, which is now available to Priority Boarding users, we’ve added support for configuration as code to build and deploy settings. This opens the door to powerful new workflows, versioning, and much more.

When you add a `railway.toml` or `railway.json` file to your repo, Railway will now read the file and map each build and deploy value to the settings of the service.

Will having a config in the repo conflict with settings that you defined in the UI? Good question! Railway will perform intelligent conflict resolution in this priority order:

1. Environment specific config in code
2. Base config in code
3. Dashboard

Want more details? We put together some [docs](https://docs.railway.app/deploy/config-as-code) which should help explain this further.

## Redeploy Button Beta

[Image: Untitled]

A successful or failed deployment can now be redeployed for Priority Boarding users. 

If you click the three dots menu on a selected deploy, it will now trigger a rebuild with the same build/deploy config. No need to slam through a sham variable to get a redeploy.

Longtime passengers of Railway know that we were hesitant to ship this feature. After discussions on [Canny](https://feedback.railway.app/feature-requests/p/redeploy-button) and [Discord](https://discord.gg/railway), we finally saw the light. Allow us to explain ourselves.

Deployments on Railway follow the immutability principle — your commits should represent a working (or not working) state of your code. We didn’t want to introduce an anti-pattern where a user had to press the “build” button a few times to finally get a working build. Railway ideally should be aware of the issue and resolve it “automagically.” The key word here is ideally.

Unfortunately, most software isn’t ideal. Events like network outages and scaling troubles sometimes makes it so that the issue isn’t with your code, it’s us.

Redeploy away! (…And let us know how it’s working on the [#priority-boarding](https://discord.com/channels/713503345364697088/921233523719946260) channel.)

## Updated Context Menu

We’ve been tinkering with a context menu in Priority Boarding for [quite a while](https://railway.app/changelog/2022-05-27#priority-boarding-context-menu). We’re happy to let you know the context menu is now live in GA!

[Image: Untitled]

## Improvements and Fixes

- Added support for Yarn Berry
- The app is now lazier, well, it lazy-loads. Smoothed the loading experience when you view your project that you haven’t looked at in a long time
- Added additional infrastructure to support more users (wow theres more of you huh?)
- [Bumped the Nixpacks version to 0.10.4](https://github.com/railwayapp/nixpacks/releases/tag/v0.10.4)
- Our party grows in strength! David Banys joins us as our first Product Marketing Manager
- We fixed a bug where if you transferred a project from a user who ran out of credits to a team, the project still wouldn’t unlock.