-
Notifications
You must be signed in to change notification settings - Fork 36
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
How to host in my own server #12
Comments
I'm going to assume the question here is what it would take to run PeopleMath as a production application on a private server, rather than on Google App Engine, which is what the README instructions tell you how to do. This should certainly be possible, but it would require some more work, probably including some changes to the application. Firstly, you'll need to decide what persistent storage mechanism you're going to use for your data. The current backend (in the backend folder) supports only Google Cloud Datastore, so assuming that won't be available to you in your environment, you'll need to write a new implementation of the Go Then, you'll either need to add command-line parameters to Then, you'll need to write configuration for whatever web server you're going to use, to achieve the same thing as the App Engine app.yaml file, i.e. I'd be happy to accept a pull request along these lines, provided the data store and web server you intend to use are reasonably mainstream (please read CONTRIBUTING.md first). If you're going to do this, please add a section to the README describing how to deploy in your chosen environment. It's also important that the README's existing instructions for deploying on Google App Engine remain correct. I hope this helped! |
Closing this issue as I believe the question is answered. If you'd like to contribute backend code for a specific persistent storage mechanism, and/or configuration and instructions for a specific web server, please feel free to open issues specific to those features. Many thanks! |
No description provided.
The text was updated successfully, but these errors were encountered: