Serving my website home page through api-umbrella
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
Start by reviewing the API Umbrella deployment and the mentioned /opt/api-umbrella/embedded/apps/static-site/releases/20190514040459/build/index.html path. Determine whether serving the static home page and configuring the existing NGINX setup are supported, then document the recommended arrangement and configuration guidance for the three questions.
Written by the indexing model from the issue text.
Description
Assume I have a domain xyz.com and I have APIs available at
- xyz.com/service1
- xyz.com/service2
Actually the above services are running at xyz.com:5000/service1 and xyz.com:5001/service2. I have used Nginx to make them accessible through port 80 as mentioned above.
My website's home page is also served through NGINX.
Now, I want to use API umbrella for API management. What I understand is I have to run API umbrella on port 80 as I will be exposing API-Umbrella's end-point instead of NGINX end-point. So I will be running NGINX on another port.
I also want to serve my website's home page(static HTML page) through port 80. I tried to replacing /opt/api-umbrella/embedded/apps/static-site/releases/20190514040459/build/index.html with my website's webpage. It works fine.
But my queries are:
-Is that a standard practice?
-As api-umbrella runs NGINX internally, is it a good practice to run two NGINX services on a single server?
-Can I use the API-Umbrella's internal NGINX to configure my application? if yes, how?
- Dominant language
- Ruby
- Stars
- 2.2k
- Forks
- 373
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from NatLabRockies/api-umbrella
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
NatLabRockies/api-umbrella#687 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
NatLabRockies/api-umbrella#682 · 6 comments · 3 reactions ·
-
MacOS support Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
NatLabRockies/api-umbrella#668 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
NatLabRockies/api-umbrella#659 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
NatLabRockies/api-umbrella#658 ·
All issues in NatLabRockies/api-umbrella
Similar issues
-
バグ
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
voxpupuli/puppet-epel#186 · 1 comment ·
-
external_created_at is no longer used for the message timestamp since the new message UI (v4.4.0) OpenBug Frontend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
TheOdinProject/curriculum#31402 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100