--- title: "Google Auth, Service Startup Order, Microsoft Container Registry" date: 2024-11-22 number: 0213 url: https://railway.com/changelog/2024-11-22-google-auth --- # Google Auth, Service Startup Order, Microsoft Container Registry Happy Ignite, Re: invent, WorkOS launch week, and SC24 to those who celebrate! This conference season, we are conferencing with our code editors to give you features you should really wear a tie for. So safely park your Saab 900 Turbos and read this edition that demolishes any and all corporate adoption blocker(s). This one is a doozy. Let’s get into it! ## Deploy Microsoft Container Registry Images This one is a pretty simple request brought by customers who are using Azure DevOps or pulling from DotNet Core. Railway has always had the ability for you to deploy a docker image directly to Railway, and now we are adding just one extra source where you can pull those images from. You can now enter a URL from Microsoft container registry and deploy on our platform. As long as the url follows [`mcr.microsoft.com`](http://mcr.microsoft.com/) - we’ll waive the image through, no ticket needed. ## Google Login Speaking of waiving through on Railway- you can be on Railway too, with Google. The Railway team is thinking about how we do identity. We hear from some of you that you're not necessarily a fan of the Magic links sent to your inbox. While we work on improvements to that experience in general, we made it so that you can now login with your Google account onto Railway. Some people on our Discord community and Help Station asked us: Why now? Railway primarily serves two different types of users: - Companies - Hobby developers There have been a lot of companies now joining onto the platform, and many of them use Google Workspace as a way to primarily handle their productivity tools and authentication. For some users on the platform, it was actually quite difficult to support both a personal use-case and a work use-case on Railway. You would have an email like: “kingdomheartslover@gmail.com” but then also try to link your company account that was “angelo@railway.com” - Google SSO now allows us to support those two accounts side by side. Not to mention the obvious, **it’s just faster.** We have more identity related goodness coming through from both Angelo and T- but in the meantime, we will revel in the new signups we just got. All aboard! ## Control Service Startup Order Tell me if you heard this one before. *I have two services, one’s called Deathstar, and Deathstar depends on Bingo before Deathstar should run. So that means I have to add a delay to Deathstar to ensure that Bingo is running or else it would crash- but what happens if Bingo has an issue?* Overthink no more! Now, services on Railway that use a variable reference from another service signal a dependency. This tells Railway to start your deployments in the order of your dependencies. That’s word soup. Let’s break it down. `ServiceA` has a variable from `ServiceB` In Railway, this would be done by our variable reference feature- so in `ServiceA`, you would have something like: variable = `${{ServiceB.VALUE}}` This means that `ServiceA` will wait to start until `ServiceB` is done building and deploying. For many projects on the platform, this means that you will no longer have to rely on hacks such as `sleep(30)` in your start command to try to enforce a start up order. Let us know what you think in our community! ## Copy log lines as JSON [Video: Copying log lines as JSON and pasting to another interface] Structured loggers, rejoice! We are committed to maintaining structure and what better tool to maintain structure than JSON. You now have the option within the log viewer to copy a log as JSON. I don’t think we can say much else about this feature. Keep reading. ## Add Custom Domains via Railway CLI This week, one of our community members, Alex, contributed an amazing feature to the Railway CLI—***Custom Domains!*** We've always had custom domain support on Railway, but now you can do it from the CLI. Hands, meet keyboard. *Butler! Usage block!* ```javascript railway domain [domain] [-p | --port] ``` It's always been a desire from the Railway team to improve the CLI- but as they say talk is cheap, show me *(sic: us)* the code. If you have an idea or a nit- [our CLI is completely open source](https://github.com/railwayapp/cli), we’d be more than happy to help you get started on a contribution. Try it out now by updating your CLI and following the steps in our [docs](https://docs.railway.com/reference/cli-api#domain). ## Improvements and Fixes - CLI: [Made it possible to skip linking the service with ](https://github.com/railwayapp/cli/pull/573)[`railway link`](https://github.com/railwayapp/cli/pull/573) - Fix an issue where running “Deploy latest commit” would deploy from the incorrect branch - Updated the CI action within our blog posts with GitHub Actions - Support for deploying Railway deployments that were marked as skipped because GitHub CI failed when waiting for CI is toggled on - Service name is now inferred from the Docker image - Fix accepting team invites when logging in with email - Fixed some instances where the incorrect `RAILWAY_PUBLIC_DOMAIN` variable was provided to a new deploy (typically when spinning up new environments) - Added pagination when viewing HTTP Logs - Nixpacks support for Node 23 - Nixpacks: fix when running binaries built with Clojure luminus - Nixpacks: Fix installing packages for PHP apps that use ext-zend-opcache - Nixpacks: Added support for `uv` (ty @iLoveItaly)