meso/Deploy Node.js to Sakura AppRun
Build and deploy Node.js applications to Sakura AppRun
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Jul 16, 2025
- License
- None
Pinned Snippet
uses: meso/sakura-apprun-action@1a6e95b139514a2ec3f33128ca045e5337a68c10 # v3tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| sakura-api-key | Sakura Cloud API Key | yes | — |
| sakura-api-secret | Sakura Cloud API Secret | yes | — |
| container-registry | Container registry URL (e.g., myregistry.sakuracr.jp) | yes | — |
| container-registry-user | Container registry username | yes | — |
| container-registry-password | Container registry password | yes | — |
| app-name | Application name (defaults to repository name) | no | "" |
| port | Application port | no | 3000 |
| max-cpu | Maximum CPU (e.g., "1", "0.5") | no | 0.4 |
| max-memory | Maximum memory (e.g., "512Mi", "1Gi") | no | 256Mi |
| timeout-seconds | Request timeout in seconds | no | 300 |
| object-storage-bucket | Sakura Object Storage bucket name for SQLite backup (enables Litestream when all S3 credentials are provided) | no | "" |
| object-storage-access-key | Sakura Object Storage access key | no | "" |
| object-storage-secret-key | Sakura Object Storage secret key | no | "" |
| sqlite-db-path | Path to SQLite database file (required when using Litestream backup) | no | "" |
| litestream-replicate-interval | Litestream replication interval (e.g., "1s", "10s") | no | 10s |
| use-repository-dockerfile | Use repository Dockerfile instead of optimized one | no | true |
Outputs
| name | description |
|---|---|
| public-url | The public URL of the deployed application |
| app-id | The AppRun application ID |