Choose a deployment platform for portfolio sites #434
illicitonion
started this conversation in
General
Replies: 1 comment
-
Other assessed options (see Slack): Frontend:
Backend:
Database:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We have ~hundreds of trainees and graduates who typically have 2-10 projects in a portfolio.
Portfolio sites typically have three components:
Each of these typically has very low resource requirements (Fontend consumes <50MB disk, backend consumes <100MB RAM, database stores <10MB of data) and low access rates (averaging <1 request per day, with likely peaks around 50 requests across a few minutes).
Key requirements are:
Ideally our trainees could host a number of these portfolio sites independently (e.g. create independent databases for each, having different DNS names or at least ports for each backend), but we've made sharing work when needed (e.g. independent tables in the same database).
Other useful features:
Ideally there would be a hosted service we could use for this, but if not, we could potentially spec out running something ourselves (ideally something out of the box rather than something we'd need to develop).
In the past we have used:
For frontends:
For backends:
For databases:
Beta Was this translation helpful? Give feedback.
All reactions