serverless / serverless/examples

Multiple Websites with one Service

Open
#246 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
11.5k
Forks
4.4k
Avg merge
2h 55m
Merged PRs (30d)
3

Description

Hi, I'm new to Serverless Architecture but would like to build a website using it. If this is not the correct place to ask such questions, please let me know where to go.

My goal is to minimize the amount of work I have to do, should I need to do any changes either with UI or backend.

I want to make multiple sports websites which are all pretty similar but obviously will have some differences since they will be specific to either baseball, football, etc... Now if I come up with a new feature, I would like to implement the change only once and make sure all websites have it, like for example showing users who are online.

Now, is it possible to create a sort of a template website where CSS and other controls are then loaded based on the website URL? So, basketball url would load the basketball website components, while the baseball url would load the baseball website components.

Also, the users would not be the same on all websites. They may register on several or only one website. The point is, different URLs should point to the same serverless app.

Would this plugin be of any help?

https://github.com/serverless/examples/tree/master/aws-node-serve-dynamic-html-via-http-endpoint

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name a repository file, test, or implementation entry point. Start by reviewing the linked aws-node-serve-dynamic-html-via-http-endpoint example and clarify the required routing, per-site UI, and user separation before proposing a change. Done would require agreed requirements and a concrete implementation scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, javascript
Domain
backend, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.