-
-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Have a backend #55
Comments
Definitely agree.
I don't know if it could be useful, but few months ago i started to work on a small restservice for mtg (to return information about a single set/all sets in xml and json format (just as an exercise to learn golang) This approach has some cons:
Anyway from my perspective i worked/i'm working with java and javascript (server and client side) and in the past i worked a little with php, so i can definetely help with the backend part. I think that this issue should be an initial design discussion on what the api backend will be. And what kind of services we want to offer. I.e.:
|
We are now off GitHub Pages! Thanks to inspiration from #78 I've moved us to Google Cloud Storage (equivalent to AWS S3). There's a This is a bit more restrictive than having an actual backend, but I think the shoe fits considering our content stays more or less the same for three months at a time. The $$$ costs will be negligible compared to a full backend, and we get what we need. Next step will be to add a cron to re-generate the API once an hour or so, which will let us provide an actual sets-currently-in-Standard API. |
We're currently hosted on GitHub Pages, so there's no possibility for backend code. We'll probably eventually want to move, because the advantages are growing with time. This is a list of them.
The text was updated successfully, but these errors were encountered: