-
Notifications
You must be signed in to change notification settings - Fork 163
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
AMI and VDI wiki walk through #1327
Comments
This is great feedback, thanks! WRT the first three points, I'll update the docs and source code branch accordingly. I have no idea about the last one, but I'll do some digging and see what I can find (ATM, I'm still figuring out how to test this pull request[1], which has slightly higher priority given damage from Monday). [1] #1326 |
@dpapathanasiou I'm happy to do pull req tomorrow when we got some time on the docs as well :) |
Somewhat frustratingly, if you set DEBUG variable in settings to False, bringing up the homepage results in a 500 error, and there are no traces of what's wrong in any of the logs! So I've left it as-is, for now. I've updated the instructions to use an S3 bucket, just like formhub.org and I think that should resolve the API issue. Let me know if this version (revision 2) is better: https://github.com/SEL-Columbia/formhub/wiki/How-To-Run-Your-Own-Formhub-Instances-on-Amazon-Web-Services |
added a client_max_body_size setting to nginx.conf and confirmed the configuration.
* slim_dedicated_server: (44 commits) adding postgres dependencies adding travis_test setting switch travis from mysql to postgres createdb irc server test failed because no requirement-mysql.pip, remove from travis.yml Updated the fabric file for this branch: uwsgi, not gunicorn, nginx, not apache, and no virtualenv. In response to upload issue SEL-Columbia#1327 reported by @myf and @donfizachi added a client_max_body_size setting to nginx.conf and confirmed the configuration. Added placeholders in default_settings for using S3 as the default file store (strongly recommened for the public AMI). Update to the docs for the new public VirtualBox (VDI) option Fixed a wiki link reference in the main README Updated the install from source document to include the public AMI on AWS as an alternative; also added a reference to /etc/rc.local for celery on AWS Updated main README to point to correct & complete instructions for this branch, including a link to how to use the public Formhub AMI on AWS, and added better explanations and links about the code structure. Removed reference to 'https://testserver.com/bob' (now a spam blog) which was being used as the form url if 'TESTING_MODE' were true. Added the 'TESTING_MODE' definition to settings (which, frustratingly enough, was undefined anywhere except in a staging example, and otherwise unexplained at all) Updated the default settings file to accept parameters for AWS/django_ses.SESBackend so that email will work (necessary for new account signup, among other things) Fixed typo in install doc Confirmed uwsgi.ini settings which will work on debian, either directly, or virtualbox vm The mongodb repo maintainers made 2.6.1 available for debian, so removed the corresponding install doc note Tweaks to uwsgi.ini Fixed the do_reload() function for formhub-uwsgi to use uwsgi's --reload switch ... Conflicts: .travis.yml README.rst extras/celeryd/etc/default/celerybeat extras/celeryd/etc/default/celeryd formhub/local_settings.py.example formhub/preset/dbrouter_example.py formhub/preset/default_settings.py formhub/preset/example_gis.py formhub/preset/example_sqlite.py formhub/preset/mysql_test.py formhub/preset/production_example.py formhub/preset/staging_example.py formhub/settings.py formhub/wsgi.py odk_logger/views.py requirements-dev.pip requirements-latest.pip requirements.pip utils/logger_tools.py
hi @dpapathanasiou and all,
@myf and @donfizachi spent the day here in abuja walked through a large portion of the VirtualBox VDI file and the Amazon AMI in order to host own formhub instance. Here are the bugs / comments we found:
AMI
nginx.conf
client_max_body_size 20M;
The text was updated successfully, but these errors were encountered: