We've added support for Slack's webhook Payloads (as well as our Discord + Raw Webhook

Depending on which URL you've inserted, we'll modify the webhook to support your preferred notification platform

Additionally, we've added a "Fire" button to test your webhooks

This week we're super excited to launch a feature on the CLI:


 in your directory, and Railway will figure out how to generate your containers locally (build, publish, and run with environment variables

As of last week, we added the ability to fork an environment on a pull request, copying it's config (infrastructure) + variables. 

However, we realized this flow isn't exactly correct. Consider the following:

You make a PR into production. You probably don't want to use your production environment configs; instead you'd want to use your staging configs.

Environment Overrides let you do just that; under Triggers you can now specify an override, which, upon creating a fork of that environment, will copy from the specified source (or the forked branch if nothing is specific)

We're still working on this feature, and we're not going to sit here and claim it's perfect, but we think it is a good start.

Additional environment variable options have been added to the Railway button. Vars can now be optional as well as include a default value.

We've got a few new starters added by the community this week! We'd like to highlight a few.

https://user-images.githubusercontent.com/3044853/110175861-536ed300-7dfa-11eb-9a40-9b7944adee93.png

Slack Webhooks, Environment Forks, and Docker Run

Changelog #0019