MAPBOX_TOKENsetting in the settings.py file (evidence). Clearly they should be loaded if there are any GL layers at all, so this is a bug. As a workaround, I'd recommend setting a
MAPBOX_TOKENvariable in your local settings.
File "/Users/stevenoneill/Projects/shareabouts-cli-tools/shareabouts_tool.py", line 108, in get_places for places_page in places.fetch_all(**self.fetch_params): AttributeError: 'ShareaboutsPlaceSet' object has no attribute 'fetch_all'
migrationsfolder on Shareabouts API. And the South migrations were in a folder named
south_migrations. We deleted the
south_migrationsfolders in our PR, and it doesn't seem like it would affect anything since we aren't using South.
remote_client_userapps by deleting all items in each app's
migrationsfolder, except the
__init__.pyfile, and ran
manage.py makemigrationsusing 1.8. But the other apps in the repo -
apikey, don't have any migrations.
manage.py showmigrationslists these apps as
sites(output here: http://ix.io/qoK/bash), so I think we'll need to recreate Django migrations for these apps as well, using 1.8. We are planning to review these third-party apps and re-make the migrations. Does that seem reasonable? Or let me know if you have other suggestions.
sa_api_v2is migrated, and thus the
auth_usertable is created, before the other apps referencing
auth_userare migrated. But I'm not sure whether this is possible or reasonable, due to foreign key or many-to-many relationships.
"https://github.com/ddollar/heroku-buildpack-multi.git"(like at https://github.com/openplans/shareabouts/blob/master/doc/DEPLOY.md#deploying-to-heroku-manually)?
I got this error trying the 'BUILDPACK_URL'-----> Fetching set buildpack https://github.com/ddollar/heroku-buildpack-multi.git... done
! Push rejected, failed to detect set buildpack https://github.com/ddollar/heroku-buildpack-multi.git
im really sorry for the repeated issues but now im getting this error after uploading .buildpacks -----> Fetching set buildpack https://github.com/ddollar/heroku-buildpack-multi.git... done
-----> Multipack app detected
=====> Downloading Buildpack: https://github.com/heroku/heroku-buildpack-nodejs.git
! Push rejected, failed to compile Multipack app
django-oauth2-provider. We are currently working to upgrade from DRF 2 to DRF 3 - feel free to reach out with any ideas or suggestions!
Also - we're curious if there are plans to work on some of the suggestions that Hadassah posted here:
We are currently working on a GUI editor for admins to edit places from the map itself, and would like to make sure we don't split our efforts in an unproductive way if this is already happening. Or better yet, we could combine efforts and accelerate these much needed improvements :+1:
AttachmentInstanceView. If you look in https://github.com/openplans/shareabouts-api/blob/master/src/sa_api_v2/views/base_views.py you'll find the
AttachmentListViewclass. The relationship between these would be similar to
Hi all - totally new to all of this but I'm looking to build a shareabouts platform for bicycle consultation for a local shire and went the easy route by clicking the 'Deploy to Heroku' button after signing up and paying. It all comes to a halt when deploying the app in the 'Build app' dialogue box: -----> Preparing static assets
Collectstatic configuration error. To debug, run: $ heroku run python ./src/manage.py collectstatic --noinput
-----> Running post-compile hook
-----> In post-compile hook
-----> Collecting static files
Traceback (most recent call last): django.core.exceptions.ImproperlyConfigured: Cannot determine PostGIS version for database "d6g2cig4dkmrbt". GeoDjango requires at least PostGIS version 1.3. Was the database created from a spatial database template?
! Push rejected, failed to compile Multipack app.
! Push failed
@mjumbewu -- hello! I saw on github that there's some activity around upgrading the shareabouts api to django 1.8. I'm not sure how extensive the upgrade plans are, but @modulitos and @dvalp and I have been working on and off on a 1.8 and DRF 3.x upgrade on our fork of the project here: mapseed/api#106. It's mainly the DRF 3.x upgrade that has been ongoing.
Anyway, not sure if it's useful for what you're planning, but thought I'd mention it here.