Skip to content
This repository has been archived by the owner on Feb 26, 2019. It is now read-only.

Figure out deployment #3

Open
spotlightishere opened this issue Feb 23, 2018 · 2 comments
Open

Figure out deployment #3

spotlightishere opened this issue Feb 23, 2018 · 2 comments
Labels
help wanted Extra attention is needed

Comments

@spotlightishere
Copy link

How are we going to run this?

Some options:

  • Deploy to App Engine with generated files off of Cloud Storage, some type of proxy? Keys could be hosted with Cloud KMS.
  • Self hosted App Engine with something akin to AppScale so we could keep in bandwidth, this'd save a lot of trouble managing VPS.
  • Some homegrown solution which could work, we'd just need to figure it out.
@spotlightishere spotlightishere added the help wanted Extra attention is needed label Feb 23, 2018
@spotlightishere
Copy link
Author

Another suggestion is to use Docker or Vagrant, in order to keep all dependencies together and still be able to both develop and deploy. apache2 on a server could be reverse proxying an exposed port making it easy to update and co-exist.

We'd want to use something with memcache for forecast cache which all currently suggested solutions would cooperate well with.

@t27duck
Copy link

t27duck commented Feb 24, 2018

It was also discussed that redis or flat files might be a better alternative to memcache as those would persist to disk

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants