Claude/fix railway deployment 01 p4 x3cxtft9bbo2g w mrm1y p #661
Conversation
This file contains hidden or 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
- Add Dockerfile at root with multi-stage build that clones submodules - Add railway.toml to configure Docker-based build instead of Railpack - Update .gitmodules to use HTTPS URLs for Railway compatibility This resolves the "Railpack could not determine how to build" error by explicitly using Docker for the build process.
Add comprehensive Railway deployment support with documentation: ## New Files - railway/README.md: Complete deployment guide (all-in-one & multi-service) - railway/QUICKSTART.md: 5-minute deployment guide - railway/.env.example: All environment variables with descriptions - railway/generate-keys.sh: Script to generate security keys - railway/runner-railway.sh: Optimized runner for Railway (no Docker-in-Docker) - railway/railway.json: Alternative JSON configuration - railway/template.json: Railway template for one-click deploy ## Modified Files - Dockerfile: Auto-detects Railway and uses optimized runner - railway.toml: Enhanced configuration with build args and docs ## Features - Automatic security key generation if not provided - Support for external PostgreSQL/Redis (Railway plugins) - Optional embedded DB mode for simple deployments - Health checks and restart policies configured - Volume mount support for data persistence
Le fichier de configuration Railway avait la commande de démarrage commentée. Sans cela, le conteneur ne savait pas quel script lancer pour démarrer tous les services (Nginx, Rails, Sidekiq). Modification : J'ai décommenté startCommand = [runner-railway.sh](http://_vscodecontentref_/1)". Permissions du script (Dockerfile) : Le script runner-railway.sh est copié dans l'image Docker mais n'était pas rendu exécutable, ce qui aurait provoqué une erreur "Permission denied" au démarrage. Modification : J'ai ajouté RUN chmod +x ./runner-railway.sh dans le Dockerfile. 3. Comment déployer sur Railway Le projet est maintenant prêt. Voici comment procéder sur Railway : Créer un nouveau projet sur Railway à partir de ce dépôt GitHub. Railway détectera automatiquement le fichier railway.toml et utilisera le Dockerfile à la racine. Configuration des services (Base de données & Redis) : Option Recommandée (Production) : Ajoutez un service PostgreSQL et un service Redis dans votre projet Railway. Railway injectera automatiquement les variables DATABASE_URL et REDIS_URL. Le script de démarrage les utilisera par défaut. Option "Tout-en-un" (Test/Démo) : Si vous ne voulez pas ajouter de services externes et tout faire tourner dans le même conteneur (moins performant, données volatiles si pas de volume), ajoutez ces variables d'environnement dans Railway :
Contributor
|
Hello @charlesvdd This PR looks strange, can you add some context? Otherwise I'll close it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Pull Request template
Please, go through these steps before you submit a PR.
Make sure that your PR is not a duplicate.
If not, then make sure that:
a. You have done your changes in a separate branch. Branches MUST have descriptive names that start with either the
fix/orfeature/prefixes. Good examples are:fix/signin-issueorfeature/issue-templates.b. You have a descriptive commit message with a short title (first line).
c. You have only one commit (if not, squash them into one commit).
d.
pnpm testdoesn't throw any error. If it does, fix them first and amend your commit (git commit --amend).After these steps, you're ready to open a pull request.
a. Give a descriptive title to your PR.
b. Describe your changes.
c. Put
closes #XXXXin your comment to auto-close the issue that your PR fixes (if such).d. Add the corresponding labels to your pull request (ex: feature, improvement, bug...)
IMPORTANT: Please review the CONTRIBUTING.md file for detailed contributing guidelines.
PLEASE REMOVE THIS TEMPLATE BEFORE SUBMITTING