aws-amplify / aws-amplify/amplify-hosting
Can we use amplify to deploy strapi (nodejs and javascript based) application
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
### Before opening, please confirm:
- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting questions](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have removed any sensitive information from my code snippets and submission.
### App Id
arn:aws:amplify:ap-south-1:840491667450:apps/d39cxurf47d7az
### AWS Region
ap-south-1
### Amplify Hosting feature
Deployments
### Question
I would like to deploy Strapi, an application based on Node.js and JavaScript, but it appears to get stuck after the post-build command. Could you please let me know if Amplify supports Strapi deployments?
I came across an archived GitHub ticket (https://github.com/aws-amplify/amplify-hosting/issues/1380) related to this issue, but I'm seeking updated information or any insights you might have on deploying Strapi with Amplify.
Below is the amplify.yml
version: 1
frontend:
phases:
preBuild:
commands:
- npm ci
build:
commands:
- npm run build
postBuild:
commands:
- npm start
artifacts:
baseDirectory: build
files:
- '**/*'
cache:
paths:
- node_modules/**/*
Contributor guide
Research direction
Start by reviewing the supplied amplify.yml and the deployment behavior after its postBuild command, then compare the question with archived issue 1380 and the linked FAQ. Done means establishing whether Strapi deployments are supported and recording the current configuration guidance or limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript, node.js
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100