I have a problem when I deploy OSQA to heroku.
Firstly, I clone OSQA source code from https://github.com/dzone/osqa
And I do some steps like the tutorial in https://github.com/joshfinnie/OSQA-Heroku
Finally, when I access to my website, I get the error message such as
ImproperlyConfigured at /
The included urlconf urls doesn't have any patterns in it
And the stack trace is as follow
/app/forum/views/readers.py in index
paginator_context.base_path = reverse('questions')
I don't know what wrong I config. So, I hope anyone can help me resolve my problem.
The link of heroku is http://where-we-go.herokuapp.com/
Thank you so much.
I found the root cause. I downgrade the version of Markdown to 2.4.1 and OSQA works fine
Related
I'm on an old installation of DjangoCMS, namely DjangoCMS 2.4.3 with Django 1.4.3.
This page exists in German and English. When I try to edit or add a plugin I'm getting a 404 error. This only happens in Frontendediting. I can edit all these plugins without any problems in Django backend.
Fun fact: This only happens in English – German pages are fine.
Does anybody have an idea what the problem could be? Or any hints, how to debug that phenomenon?
Thanks in advance
I figured it out myself: Since I've update the cms from an older version, also the static files had to be updated. I forgot to manage.py collectstatic on my server.
I am running into an issue when I am deploying my app to heroku servers. On development (localhost:3000) everything works fine, when I launch the app some of my javascript is not working.
Solved the issue.
Turns out it had to do with bootstap reading the gems that were local on my machine. When I went to go push to heroku it was causing issues since I didnt precompile my assets and having all the gems was causing confusion so I removed them and added the bootstrap CDN and added it to the end of my body tag.
Maybe your assets are not precompiled. Check browser's console for missing files.
Heroku has very thorough documentation on getting the Rails Asset Pipeline working on there. Make sure you also use your browser development tools to help you identify 404 errors with assets or any other issues that can help you diagnose the problem.
I am trying to build a webapp which uses GeoDjango. The app is to be hosted on Heroku, but I am facing issues in it. I am using this buildpack but then this error is coming. Figured out that this is happening because of Cedar 14 but I am not clear as to what should I do next.
Also I tried using this buildpack but as discussed here, this issue can be resolved by using the buildpath as
$ heroku config:add BUILDPACK_URL=https://github.com/cyberdelia/heroku-geo-buildpack.git#1.3
I tried the same but now it is not detecting it as a Python app and now I am facing the issue of "django import error - No module named core.management " missing, which is because its not installing Django.
Any help will be greatly appreciated.
I figured out the solution to this problem myself only.
To add multiple values for a BUILDPACK_URL, one needs to use a buildpack which can add support for mutiple BUILDPACK_URL.
So I used this. One can write like
$ heroku config:add BUILDPACK_URL=https://github.com/ddollar/heroku-buildpack-multi.git
After this create a file .buildpacks and add to it the following
https://github.com/cyberdelia/heroku-geo-buildpack.git#e1b845b
https://github.com/heroku/heroku-buildpack-python.git
Note that #e1845b is because of this comment, which mentions that it is because of some caching issues.
I am following the tutorial for deploying a django project on AWS elastic beanstalk here:
http://docs.amazonwebservices.com/elasticbeanstalk/latest/dg/create_deploy_Python_django.html
My app works when I test locally but when I deploy, I'm getting a 404 error. Looking at the event logs, I see this message:
Error running user's commands : An error occurred running '. /opt/python/ondeck/env && PYTHONPATH=/opt/python/ondeck/app: django-admin.py syncdb --noinput' (rc: 127) /bin/sh: django-admin.py: command not found
That leads me to believe that the tutorial is missing a part about installing django files on the server or at least configuring my project to recognize django-admin.py. I have django installed on my local machine so it works there.
I know python support is brand new for elastic beanstalk but has anyone deployed django to it?
I believe you don't need to put container_commands in .config because there is no database or table at this moment.
Did you made the step?: Freeze the requirements.txt file.
(djangodev)# pip freeze > requirements.txt
Note
Make sure your requirements.txt file contains the following:
Django==1.4.1
MySQL-python==1.2.3
I had the same problem because I skipped it. Once I did it, add, commit and push. It works!
I followed the same tutorial recently and had a similar result.
At step 6, upon seeing the default django 'congrats' page render locally, I deployed to EB as instructed and got a 404 instead of the default 'congrats' page.
I decided to use the code up to that point as a foundation for following the 'getting started with django tutorial' which led me to a successful rendering of a 'home' view. This is a much more useful place to be anyway. I do agree that there is something wrong with the AWS tutorial and posted to the AWS forums here.
If you can, you should try to access the log file; it might give you a better idea of what's going on. Here's a link that might help:
http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.loggingS3.title.html
Does anyone know how to get Django and Subversion to work together on Dreamhost?
I've been following this tutorial to install Django (which uses Passenger WSGI):
http://wiki.dreamhost.com/Django
After I got Django to work, Subversion stopped working. Has anyone ran into this problem?
I had the same problem. My solution for now has been to move the Subversion link to a different subdomain.
In my case, I'm only using Django for 1 subdomain in my whole domain (dom1.myurl.com), so I just created a dom2.myurl.com subdomain, and set my SVN path to use it instead.