Sync with main repo @ c1b92d08 #39
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: JuanM04 <me@juanm04.com> Co-authored-by: Andreas Bollig <andreas.bollig@gmail.com> Co-authored-by: Abu Uzayr <abu.uzayr@builtforfifty.com> Co-authored-by: François Best <francois@francoisbest.com> Co-authored-by: Faraz Patankar <farazpatankar@gmail.com> Co-authored-by: Eric Vicenti <ericvicenti@users.noreply.github.com> Co-authored-by: Alex <alex@dolo.dev>
Co-authored-by: JuanM04 <me@juanm04.com> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com> Co-authored-by: Brandon Bayer <b@bayer.ws> Co-authored-by: Andreas Bollig <andreas.bollig@gmail.com> Co-authored-by: Abu Uzayr <abu.uzayr@builtforfifty.com> Co-authored-by: François Best <francois@francoisbest.com> Co-authored-by: Faraz Patankar <farazpatankar@gmail.com> Co-authored-by: Eric Vicenti <ericvicenti@users.noreply.github.com> Co-authored-by: Layne Geck <layne.geck@gmail.com> Co-authored-by: gstranger <36181416+gstranger@users.noreply.github.com> Co-authored-by: Andrea Rizzello <10348930+andrearizzello@users.noreply.github.com>
Co-authored-by: Brandon Bayer <b@bayer.ws> Co-authored-by: Jahred Hope <jahredhope@gmail.com> Co-authored-by: Fran Zekan <zekan.fran369@gmail.com>
* new maintainer TommasoBruno added * href TommasoBruno maintainer changed
Added to `cli-start.mdx` & `cli-dev.mdx`
* typo fix Small typo fix: you'll need to do the chech => you'll need to do the check * Update session.create > session.$create * Update api routes doc examples - no anon exports * Edit preview mode doc examples - no anon exports * Change export name to handler * Change export name to handler
Typo removed
Co-authored-by: Brandon Bayer <b@bayer.ws>
Co-authored-by: Brandon Bayer <b@bayer.ws> Co-authored-by: Lukas Neumann <l.neumann@layer9.berlin>
Co-authored-by: Nicolas <ntorres.dev@gmail.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: JuanM04 <me@juanm04.com>
I'm just getting started with Blitz. Following the Getting Started Guide and the this section about deployment on Railway I ran into an HTTP 502 Bad Gateway error. I figured out that the port the Blitz server is running on must be configured manually for Railway. One way is to modify the start script as already [described in a discussion](blitz-js/blitz#2335). Another way is to add a `PORT` variable to the railway environment. Maybe it would be a good idea to add this piece of information to the Railway Deployment section?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically generated.
Merge changes from blitzjs.com at c1b92d0
The following files have conflicts and may need new translations:
Please fix the conflicts by pushing new commits to this pull request, either by editing the files directly on GitHub or by checking out this branch.
DO NOT SQUASH MERGE THIS PULL REQUEST!
Doing so will "erase" the commits from main and cause them to show up as conflicts the next time we merge.