@railway/cli 3.11.4 → 3.17.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +47 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -16,6 +16,7 @@ The Railway CLI allows you to
|
|
|
16
16
|
- Link to an existing Railway project
|
|
17
17
|
- Pull down environment variables for your project locally to run
|
|
18
18
|
- Create services and databases right from the comfort of your fingertips
|
|
19
|
+
|
|
19
20
|
## Status
|
|
20
21
|
Currently pre-release. We are looking for feedback and suggestions. Please join our [Discord](https://discord.gg/railway) to provide feedback.
|
|
21
22
|
|
|
@@ -51,6 +52,52 @@ bash <(curl -fsSL cli.new) -r
|
|
|
51
52
|
scoop install railway
|
|
52
53
|
```
|
|
53
54
|
|
|
55
|
+
### Arch Linux AUR
|
|
56
|
+
|
|
57
|
+
Install using Paru
|
|
58
|
+
```bash
|
|
59
|
+
paru -S railwayapp-cli
|
|
60
|
+
```
|
|
61
|
+
Install using Yay
|
|
62
|
+
```bash
|
|
63
|
+
yay -S railwayapp-cli
|
|
64
|
+
```
|
|
65
|
+
|
|
66
|
+
### Docker
|
|
67
|
+
|
|
68
|
+
Before using the CLI in a non-interactive environment, ensure you have created an access token (only project-tokens are supported as of now) and set it as the `RAILWAY_TOKEN` environment variable. CI environments are automatically detected by the presence of `CI=true` variable. In these environments, only build logs will be streamed, and the CLI will exit with an appropriate code indicating success or failure.
|
|
69
|
+
|
|
70
|
+
Install from the command line
|
|
71
|
+
```bash
|
|
72
|
+
docker pull ghcr.io/railwayapp/cli:latest
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
Use in GitHub Actions
|
|
76
|
+
```yml
|
|
77
|
+
deploy-job:
|
|
78
|
+
runs-on: ubuntu-latest
|
|
79
|
+
container: ghcr.io/railwayapp/cli:latest
|
|
80
|
+
env:
|
|
81
|
+
SVC_ID: my-service
|
|
82
|
+
RAILWAY_TOKEN: ${{ secrets.RAILWAY_TOKEN }}
|
|
83
|
+
steps:
|
|
84
|
+
- uses: actions/checkout@v3
|
|
85
|
+
- run: railway up --service=${{ env.SVC_ID }}
|
|
86
|
+
```
|
|
87
|
+
|
|
88
|
+
Use in GitLab CICD
|
|
89
|
+
```yml
|
|
90
|
+
deploy-job:
|
|
91
|
+
image: ghcr.io/railwayapp/cli:latest
|
|
92
|
+
variables:
|
|
93
|
+
SVC_ID: my-service
|
|
94
|
+
script:
|
|
95
|
+
- railway up --service=$SVC_ID
|
|
96
|
+
```
|
|
97
|
+
|
|
98
|
+
> [!TIP]
|
|
99
|
+
> GitLab can access a protected (secret) variable directly, all you need to do is to add it in CI/CD settings.
|
|
100
|
+
|
|
54
101
|
### From source
|
|
55
102
|
See [CONTRIBUTING.md](https://github.com/railwayapp/cli/blob/master/CONTRIBUTING.md) for information on setting up this repo locally.
|
|
56
103
|
|