What's the advantage of using AMP Server vs the traditional route (Niginx, Apache etc.)?
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 1.3k
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I'm looking to create a new app with AMP integrated and I wasn't sure what the advantage of using PHP to serve directly with AMP server vs the FastCGI approach. Are there any major pros or cons?
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. First determine whether the project has documentation describing direct AMP serving and FastCGI deployment, then document the relevant advantages and trade-offs so the comparison answers the question.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100