internlm/SWE-Fixer-Train-110K huggingface dataset:
Repository: OpenEnergyPlatform/oeplatform

Issue:
Link to api tutorial on oep homepage is broken.
## Description of the issue

This button leads to a 404 page on the academy page.
![image](https://github.com/OpenEnergyPlatform/oeplatform/assets/38939526/876abc57-593d-4625-a58d-3cfc1fae57a1)

## Steps to Reproduce


## Ideas of solution
- [x] Find updated tutorial URI and update link.

Describe possible ideas for solution and evaluate advantages and disadvantages.

## Context and Environment
* Version used: 
* Operating system: 
* Environment setup and (python) version: 

## Workflow checklist
- [x] I am aware of the workflow in [CONTRIBUTING.md](https://github.com/OpenEnergyPlatform/oeplatform/blob/develop/CONTRIBUTING.md)



Discussion:
The tutorials on the Academy have been restructured and updated.
It should be this link: 
https://openenergyplatform.github.io/academy/tutorials/01_api/01_api_download/

Resolving patch:
diff --git a/oeplatform/settings.py b/oeplatform/settings.py
--- a/oeplatform/settings.py
+++ b/oeplatform/settings.py
@@ -78,7 +78,7 @@
 EXTERNAL_URLS = {
     "tutorials_index": "https://openenergyplatform.github.io/academy/",
     "tutorials_faq": "https://openenergyplatform.github.io/academy/",
-    "tutorials_api1": "https://openenergyplatform.github.io/academy/tutorials/api/OEP_API_tutorial_part1/",  # noqa E501
+    "tutorials_api1": "https://openenergyplatform.github.io/academy/tutorials/01_api/01_api_download/",  # noqa E501
     "tutorials_licenses": "https://openenergyplatform.github.io/academy/tutorials/metadata/tutorial_open-data-licenses/",  # noqa E501
     "readthedocs": "https://oeplatform.readthedocs.io/en/latest/?badge=latest",
     "compendium": "https://openenergyplatform.github.io/organisation/",


Test patch:
Repository: OpenEnergyPlatform/oeplatform

Issue:
Steps to Production: Release scenario bundle and qualitative comparison
## Description of the issue

We want to release the new scenario bundle (aka scenario factsheets) on the production OEP. To be able to do this we need to finalize the implementation and install the necessary infrastructure.


## Ideas of solution

- [x] Store all oeo.owl files in a centralized directory
- [x] create Apache Jenna db for production oep
- [x] #1393
- [x] add link to scenario bundle application to nav bar
- [x] activate access controls
- [x] fix nav bar dropdowns in base-wide-react template
- [x] Code formatting
- [x] #1394
- [x] Release hotfix for updated scenario bundle api url (relevant to fix CORS errors)

## Workflow checklist
- [x] I am aware of the workflow in [CONTRIBUTING.md](https://github.com/OpenEnergyPlatform/oeplatform/blob/develop/CONTRIBUTING.md)



Discussion:

Resolving patch:
diff --git a/factsheet/views.py b/factsheet/views.py
--- a/factsheet/views.py
+++ b/factsheet/views.py
@@ -58,11 +58,11 @@
 
 oeo_owl = get_ontology(Ontology_URI_STR).load()
 
-# query_endpoint = 'http://localhost:3030/ds/query'
-# update_endpoint = 'http://localhost:3030/ds/update'
+#query_endpoint = 'http://localhost:3030/ds/query'
+#update_endpoint = 'http://localhost:3030/ds/update'
 
-# query_endpoint = 'https://toekb.iks.cs.ovgu.de:3443/oekg/query'
-# update_endpoint = 'https://toekb.iks.cs.ovgu.de:3443/oekg/update'
+#query_endpoint = 'https://toekb.iks.cs.ovgu.de:3443/oekg/query'
+#update_endpoint = 'https://toekb.iks.cs.ovgu.de:3443/oekg/update'
 
 query_endpoint = 'https://oekb.iks.cs.ovgu.de:3443/oekg_main/query'
 update_endpoint = 'https://oekb.iks.cs.ovgu.de:3443/oekg_main/update'
diff --git a/oeplatform/__init__.py b/oeplatform/__init__.py
--- a/oeplatform/__init__.py
+++ b/oeplatform/__init__.py
@@ -1 +1 @@
-__version__ = "0.15.0"
+__version__ = "0.15.1"


Test patch:
Repository: OpenEnergyPlatform/oeplatform

Issue:
toep: wrong FAQ link 
## Description of the issue

On toep there is now a drop down menu including a link to "FAQs". 
The link however goes to the main page of the OEA instead of going to the questions section: https://openenergyplatform.github.io/academy/questions/

## Steps to Reproduce
1. Visit toep and click FAQ in "About" drop-down

## Ideas of solution

Link directly to https://openenergyplatform.github.io/academy/questions/

FYI @wingechr 


Discussion:

Resolving patch:
diff --git a/oeplatform/settings.py b/oeplatform/settings.py
--- a/oeplatform/settings.py
+++ b/oeplatform/settings.py
@@ -81,7 +81,7 @@
 
 EXTERNAL_URLS = {
     "tutorials_index": "https://openenergyplatform.github.io/academy/",
-    "tutorials_faq": "https://openenergyplatform.github.io/academy/",
+    "tutorials_faq": "https://openenergyplatform.github.io/academy/questions/",
     "tutorials_api1": "https://openenergyplatform.github.io/academy/tutorials/01_api/01_api_download/",  # noqa E501
     "tutorials_licenses": "https://openenergyplatform.github.io/academy/tutorials/metadata/tutorial_open-data-licenses/",  # noqa E501
     "readthedocs": "https://oeplatform.readthedocs.io/en/latest/?badge=latest",


Test patch:
Repository: OpenEnergyPlatform/oeplatform

Issue:
Scenario bundles: Output datasets render weirdly
## Description of the issue

I added an output dataset for the WAM scenario for this factsheet: https://openenergy-platform.org/scenario-bundles/id/95a65aca-6915-b64a-cac7-3831c12885b4

![grafik](https://github.com/OpenEnergyPlatform/oeplatform/assets/36844029/fa43133d-3cd7-4a22-80a0-384cbf6514e3)

It reads wrongly and shows more than only the title of the dataset, i.e. it should only be rendered as: Rahmendaten für den Projektionsbericht 2023 (Datentabelle) - as it does for the WEM scenario (this was already existing before the new release). 


## Steps to Reproduce
1. Add a dataset to a scenario
2.
3.

## Ideas of solution

Describe possible ideas for solution and evaluate advantages and disadvantages.

## Context and Environment
* Version used: 
* Operating system: 
* Environment setup and (python) version: 

## Workflow checklist
- [ ] I am aware of the workflow in [CONTRIBUTING.md](https://github.com/OpenEnergyPlatform/oeplatform/blob/develop/CONTRIBUTING.md)



Discussion:

Resolving patch:
diff --git a/oeplatform/__init__.py b/oeplatform/__init__.py
--- a/oeplatform/__init__.py
+++ b/oeplatform/__init__.py
@@ -1 +1 @@
-__version__ = "0.16.1"
+__version__ = "0.16.2"


Test patch:
Repository: OpenEnergyPlatform/oeplatform

Issue:
Implement qualitative Scenario Comparison UI
## Description of the issue

The qualitative comparison of scenarios is already available and we need to create and implement a UI.

## Ideas of solution

[We agreed on a mockup and can implement it.](https://www.figma.com/file/rWzNf643RnQmI8ODk0zlfO/Database-pages-view?type=design&node-id=2241-927&mode=design&t=hvkHkoDZCRp4FVYq-0) 

## Workflow checklist
- [x] I am aware of the workflow in [CONTRIBUTING.md](https://github.com/OpenEnergyPlatform/oeplatform/blob/develop/CONTRIBUTING.md)



Discussion:

Resolving patch:
diff --git a/factsheet/views.py b/factsheet/views.py
--- a/factsheet/views.py
+++ b/factsheet/views.py
@@ -1119,7 +1119,7 @@ def query_oekg(request, *args, **kwargs):
     return response
 
 
-# @login_required
+@login_required
 @csrf_exempt
 def delete_factsheet_by_id(request, *args, **kwargs):
     id = request.GET.get("id")
@@ -1173,7 +1173,7 @@ def get_entities_by_type(request, *args, **kwargs):
     return response
 
 
-# @login_required
+@login_required
 @csrf_exempt
 def add_entities(request, *args, **kwargs):
     request_body = json.loads(request.body)
@@ -1203,7 +1203,7 @@ def add_entities(request, *args, **kwargs):
     return response
 
 
-# @login_required
+@login_required
 @csrf_exempt
 def add_a_fact(request, *args, **kwargs):
     request_body = json.loads(request.body)
@@ -1230,7 +1230,7 @@ def add_a_fact(request, *args, **kwargs):
     return response
 
 
-# @login_required
+@login_required
 @csrf_exempt
 def delete_entities(request, *args, **kwargs):
     entity_type = request.GET.get("entity_type")
@@ -1250,7 +1250,7 @@ def delete_entities(request, *args, **kwargs):
     return response
 
 
-# @login_required
+@login_required
 @csrf_exempt
 def update_an_entity(request, *args, **kwargs):
     request_body = json.loads(request.body)


Test patch:
Repository: OpenEnergyPlatform/oeplatform

Issue:
Scenario Bundles: Displays countries in selection order
## Description of the issue
The scenario bundles show the selected countries in the order the user picked them while entering the sheet
![grafik](https://github.com/OpenEnergyPlatform/oeplatform/assets/36844029/bf86fd69-54e0-4a49-b657-d379d693c6e9)


## Ideas of solution

It would be great to list them alphabetically

## Workflow checklist
- [x ] I am aware of the workflow in [CONTRIBUTING.md](https://github.com/OpenEnergyPlatform/oeplatform/blob/develop/CONTRIBUTING.md)

FYI @stap-m @l-emele @wingechr 


Discussion:

Resolving patch:
diff --git a/factsheet/views.py b/factsheet/views.py
--- a/factsheet/views.py
+++ b/factsheet/views.py
@@ -893,10 +893,6 @@ def factsheet_by_id(request, *args, **kwargs):
     study_URI = URIRef("http://openenergy-platform.org/ontology/oekg/" + uid)
     factsheet = {}
 
-    print("############################start")
-    print(study_URI)
-    print(oekg.value(study_URI, OEKG["date_of_publication"]))
-
     acronym = ""
     study_name = ""
     abstract = ""
@@ -1101,7 +1097,6 @@ def factsheet_by_id(request, *args, **kwargs):
     response = JsonResponse(factsheet, safe=False, content_type="application/json")
     patch_response_headers(response, cache_timeout=1)
 
-    print("#####update#####")
     scenario_region = URIRef(
         "http://openenergy-platform.org/ontology/oekg/region/Germany"
     )


Test patch:
Repository: OpenEnergyPlatform/oeplatform

Issue:
Scenario Bundles: DOI seems to be repeated
## Description of the issue

When inserting a DOI in the publications it seems to be repeated.
![grafik](https://github.com/OpenEnergyPlatform/oeplatform/assets/54852694/a8ae5354-61ce-4e8b-925c-14b6797cafbd)



## Steps to Reproduce
1. insert DOI in field 
2. save

## Ideas of solution

Describe possible ideas for solution and evaluate advantages and disadvantages.

## Context and Environment
* Version used: 
* Operating system: 
* Environment setup and (python) version: 

## Workflow checklist
- [ ] I am aware of the workflow in [CONTRIBUTING.md](https://github.com/OpenEnergyPlatform/oeplatform/blob/develop/CONTRIBUTING.md)



Discussion:
Good catch! Seems like no one ever used the DOI :)

Resolving patch:
diff --git a/factsheet/views.py b/factsheet/views.py
--- a/factsheet/views.py
+++ b/factsheet/views.py
@@ -61,11 +61,11 @@
 # query_endpoint = "http://localhost:3030/ds/query"
 # update_endpoint = "http://localhost:3030/ds/update"
 
-# query_endpoint = 'https://toekb.iks.cs.ovgu.de:3443/oekg/query'
-# update_endpoint = 'https://toekb.iks.cs.ovgu.de:3443/oekg/update'
+query_endpoint = 'https://toekb.iks.cs.ovgu.de:3443/oekg/query'
+update_endpoint = 'https://toekb.iks.cs.ovgu.de:3443/oekg/update'
 
-query_endpoint = "https://oekb.iks.cs.ovgu.de:3443/oekg_main/query"
-update_endpoint = "https://oekb.iks.cs.ovgu.de:3443/oekg_main/update"
+#query_endpoint = "https://oekb.iks.cs.ovgu.de:3443/oekg_main/query"
+#update_endpoint = "https://oekb.iks.cs.ovgu.de:3443/oekg_main/update"
 
 sparql = SPARQLWrapper(query_endpoint)
 


Test patch:
Repository: OpenEnergyPlatform/oeplatform

Issue:
Scenario Bundles: Display scenario years in ascending order
## Description of the issue

Scenario years are not displayed in ascending order. 
![grafik](https://github.com/OpenEnergyPlatform/oeplatform/assets/54852694/82c7fff1-0848-4bf6-9ba1-2e5e74db39e5)


## Ideas of solution

It would be great to sort them in ascending order.

Solution could be similar to the alphabetical sorting here https://github.com/OpenEnergyPlatform/oeplatform/issues/1423

## Workflow checklist
- [x] I am aware of the workflow in [CONTRIBUTING.md](https://github.com/OpenEnergyPlatform/oeplatform/blob/develop/CONTRIBUTING.md)



Discussion:
Yes we should introduce ascending order.

Resolving patch:
diff --git a/factsheet/views.py b/factsheet/views.py
--- a/factsheet/views.py
+++ b/factsheet/views.py
@@ -61,11 +61,11 @@
 # query_endpoint = "http://localhost:3030/ds/query"
 # update_endpoint = "http://localhost:3030/ds/update"
 
-# query_endpoint = 'https://toekb.iks.cs.ovgu.de:3443/oekg/query'
-# update_endpoint = 'https://toekb.iks.cs.ovgu.de:3443/oekg/update'
+query_endpoint = 'https://toekb.iks.cs.ovgu.de:3443/oekg/query'
+update_endpoint = 'https://toekb.iks.cs.ovgu.de:3443/oekg/update'
 
-query_endpoint = "https://oekb.iks.cs.ovgu.de:3443/oekg_main/query"
-update_endpoint = "https://oekb.iks.cs.ovgu.de:3443/oekg_main/update"
+#query_endpoint = "https://oekb.iks.cs.ovgu.de:3443/oekg_main/query"
+#update_endpoint = "https://oekb.iks.cs.ovgu.de:3443/oekg_main/update"
 
 sparql = SPARQLWrapper(query_endpoint)
 


Test patch:
Repository: OpenEnergyPlatform/oeplatform

Issue:
Scenario bundles: Access denied error for edit mode in create new
When we use the "create new" button to make a new bundle, we are in edit mode, but if we click the view button, we can not go back to the edit mode again. An error with "Access denied! You cannot edit scenario bundles that you do not own!" message  prevents editing the new un-saved bundle 

## Solution

Disable the save and edit button until the bundle is saved!



## Workflow checklist
- [ ] I am aware of the workflow in [CONTRIBUTING.md](https://github.com/OpenEnergyPlatform/oeplatform/blob/develop/CONTRIBUTING.md)



Discussion:
I noticed that too, thanks for pointing it out. This is because there is no entry in the database because the scenario bundle has not yet been created. We need a different status that indicates that the current scenario bundle is being created and avoids the access rights check.

Resolving patch:
diff --git a/login/views.py b/login/views.py
--- a/login/views.py
+++ b/login/views.py
@@ -53,7 +53,7 @@ def get(self, request, user_id):
             }
 
             if permission_level >= models.WRITE_PERM:
-                if table.is_publish or table.schema.name not in UNVERSIONED_SCHEMAS:
+                if table.is_publish and table.schema.name not in UNVERSIONED_SCHEMAS:
                     published_tables.append(table_data)
                 else:
                     draft_tables.append(table_data)
diff --git a/oeplatform/settings.py b/oeplatform/settings.py
--- a/oeplatform/settings.py
+++ b/oeplatform/settings.py
@@ -89,7 +89,6 @@
     "compendium": "https://openenergyplatform.github.io/organisation/",
     "tib_terminology_service": "https://terminology.tib.eu/ts/collections",
     "spdx_licenses": "https://spdx.github.io/license-list-data/",
-
 }
 
 # Kept this separate for now to avoid messing with the other list ... TODO move to EXTERNAL_URLS if possible


Test patch:
Repository: OpenEnergyPlatform/oeplatform

Issue:
OEP server error log show attempt to connect to external service which is forbidden 
## Description of the issue

The model / framework factsheets include a feature that attempts to generate a git commit graph to show the commit activitie in case the facthseet includes a github url. The OEP server infrastructure denies all requests from the oep network to the outside world (WAN). This leads to severals enties in the OEP server error log.

## Steps to Reproduce
1. Create a modle or framework factsheet on the oep
2. Provide a github link
3. Have a look at the interal server logs.

Example:

```
 Failed to establish a new connection: [Errno 111] Connection refused',)': /repos/calliope-project/euro-calliope/stats/commit_activity
```

## Ideas of solution

Deactivate the functionality in modelview/views.py called `_handle_github_contributions`.

## Context and Environment
* Version used: v0.18
* Operating system: -
* Environment setup and (python) version: -

## Workflow checklist
- [ ] I am aware of the workflow in [CONTRIBUTING.md](https://github.com/OpenEnergyPlatform/oeplatform/blob/develop/CONTRIBUTING.md)



Discussion:

Resolving patch:
diff --git a/modelview/views.py b/modelview/views.py
--- a/modelview/views.py
+++ b/modelview/views.py
@@ -143,7 +143,7 @@ def show(request, sheettype, model_name):
             )
             org = match.group("org")
             repo = match.group("repo")
-            _handle_github_contributions(org, repo)
+            # _handle_github_contributions(org, repo)
         except Exception:
             org = None
             repo = None
@@ -343,8 +343,8 @@ def _handle_github_contributions(org, repo, timedelta=3600, weeks_back=8):
     If the image is not present or outdated it will be reconstructed
 
     Note:
-        Keep in mind that a external (GitHub) API is called and you server need to allow
-        such connections.
+        Keep in mind that a external (GitHub) API is called and your server 
+        needs to allow such connections.
     """
     path = "GitHub_{0}_{1}_Contribution.png".format(org, repo)
     full_path = os.path.join(djangoSettings.MEDIA_ROOT, path)


Test patch:
Repository: OpenEnergyPlatform/oeplatform

Issue:
Metadata is not always availabe for download even if visible in the database & metadata widget
## Description of the issue

For some tables, the metadata cannot be downloaded, even if it is visible in the metadata widget (on the ‘Meta information’ tab on the table details page).

## Steps to Reproduce

1. https://openenergyplatform.org/dataedit/view/model_draft/ind_source_steel_coke
2. Click Download metadata / look at https://openenergyplatform.org/api/v0/schema/model_draft/tables/ind_source_steel_coke/meta/
3. You only see an empyt {}

## Ideas of solution

Some time ago, we introduced a new approach to storing metadata. Previously, metadata was stored as an SQL comment to a table. Now the metadata is stored in the database (internal to django). 

The metadata view (api) provides the GET method to retrieve the metadata, but the code still fetches the metadata from the comment-on table. We still store it there as we have decided to keep the bot memory for some time. In some cases (when no cursor is passed) the metadata is not stored as a comment in the table. This leads to the current problem. 

We always have to retrieve the metadata from the database.

## Context and Environment

- Version used:
- Operating system:
- Environment setup and (python) version:

## Workflow checklist

- [x] I am aware of the workflow in [CONTRIBUTING.md](https://github.com/OpenEnergyPlatform/oeplatform/blob/develop/CONTRIBUTING.md)



Discussion:

Resolving patch:
diff --git a/api/actions.py b/api/actions.py
--- a/api/actions.py
+++ b/api/actions.py
@@ -1114,9 +1114,9 @@ def _get_table(schema, table):
 
 
 def get_table_metadata(schema, table):
-    table_obj = _get_table(schema=schema, table=table)
-    comment = table_obj.comment
-    return json.loads(comment) if comment else {}
+    django_obj = DBTable.load(schema=schema, table=table)
+    oemetadata = django_obj.oemetadata
+    return oemetadata if oemetadata else {}
 
 
 def __internal_select(query, context):


Test patch:
Repository: agconti/cookiecutter-django-rest

Issue:
Handle "/" routing



Discussion:

Resolving patch:
diff --git a/{{cookiecutter.github_repository_name}}/{{cookiecutter.app_name}}/config/common.py b/{{cookiecutter.github_repository_name}}/{{cookiecutter.app_name}}/config/common.py
--- a/{{cookiecutter.github_repository_name}}/{{cookiecutter.app_name}}/config/common.py
+++ b/{{cookiecutter.github_repository_name}}/{{cookiecutter.app_name}}/config/common.py
@@ -91,6 +91,7 @@ class Common(Configuration):
     USE_I18N = True
     USE_L10N = True
     USE_TZ = True
+    LOGIN_REDIRECT_URL = '/'
 
     # Static Files
     STATIC_ROOT = join(os.path.dirname(BASE_DIR), 'staticfiles')
diff --git a/{{cookiecutter.github_repository_name}}/{{cookiecutter.app_name}}/urls.py b/{{cookiecutter.github_repository_name}}/{{cookiecutter.app_name}}/urls.py
--- a/{{cookiecutter.github_repository_name}}/{{cookiecutter.app_name}}/urls.py
+++ b/{{cookiecutter.github_repository_name}}/{{cookiecutter.app_name}}/urls.py
@@ -2,8 +2,10 @@
 
 from django.conf import settings
 from django.conf.urls import include, url
+from django.core.urlresolvers import reverse_lazy
 from django.conf.urls.static import static
 from django.contrib import admin
+from django.views.generic.base import RedirectView
 
 urlpatterns = [
     url(r'^admin/', include(admin.site.urls)),
@@ -11,4 +13,8 @@
     url(r'^api/v1/', include('users.urls')),
     url(r'^api/v1/notifications/', include('push_notifications.urls')),
 
+    # the 'api-root' from django rest-frameworks default router
+    # http://www.django-rest-framework.org/api-guide/routers/#defaultrouter
+    url(r'^$', RedirectView.as_view(url=reverse_lazy('api-root'))),
+
 ] + static(settings.MEDIA_URL, document_root=settings.MEDIA_ROOT)


Test patch:
Repository: agconti/cookiecutter-django-rest

Issue:
Add django-storages-redux config to production. 



Discussion:

Resolving patch:
diff --git a/{{cookiecutter.github_repository_name}}/{{cookiecutter.app_name}}/config/production.py b/{{cookiecutter.github_repository_name}}/{{cookiecutter.app_name}}/config/production.py
--- a/{{cookiecutter.github_repository_name}}/{{cookiecutter.app_name}}/config/production.py
+++ b/{{cookiecutter.github_repository_name}}/{{cookiecutter.app_name}}/config/production.py
@@ -40,6 +40,25 @@ class Production(Common):
         )),
     )
 
+    # Media files
+    # http://django-storages.readthedocs.org/en/latest/index.html
+    INSTALLED_APPS += ('storages',)
+    DEFAULT_FILE_STORAGE = 'storages.backends.s3boto.S3BotoStorage'
+    AWS_ACCESS_KEY_ID = values.Value('DJANGO_AWS_ACCESS_KEY_ID')
+    AWS_SECRET_ACCESS_KEY = values.Value('DJANGO_AWS_SECRET_ACCESS_KEY')
+    AWS_STORAGE_BUCKET_NAME = values.Value('DJANGO_AWS_STORAGE_BUCKET_NAME')
+    AWS_AUTO_CREATE_BUCKET = True
+    MEDIA_URL = 'https://s3.amazonaws.com/{}/'.format(AWS_STORAGE_BUCKET_NAME)
+    from boto.s3.connection import OrdinaryCallingFormat
+    AWS_S3_CALLING_FORMAT = OrdinaryCallingFormat()
+
+    # https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/http-caching#cache-control
+    # Response can be cached by browser and any intermediary caches (i.e. it is "public") for up to 1 day
+    # 86400 = (60 seconds x 60 minutes x 24 hours)
+    AWS_HEADERS = {
+        'Cache-Control': 'max-age=86400, s-maxage=86400, must-revalidate',
+    }
+
     # Static files
     STATICFILES_STORAGE = 'whitenoise.django.GzipManifestStaticFilesStorage'
 


Test patch:
Repository: agconti/cookiecutter-django-rest

Issue:
Update pg backups with schedule time
`heroku pg:backups schedule DATABASE --at '04:00 UTC' --remote dev`



Discussion:

Resolving patch:
diff --git a/{{cookiecutter.github_repository_name}}/fabfile.py b/{{cookiecutter.github_repository_name}}/fabfile.py
--- a/{{cookiecutter.github_repository_name}}/fabfile.py
+++ b/{{cookiecutter.github_repository_name}}/fabfile.py
@@ -90,7 +90,7 @@ def configure_sever():
     """
     require('environment')
     local('heroku addons:create heroku-postgresql:dev --remote {}'.format(env.environment))
-    local('heroku pg:backups schedule DATABASE_URL --remote {}'.format(env.environment))
+    local('heroku pg:backups schedule DATABASE --at "04:00 UTC" --remote {}'.format(env.environment))
     local('heroku pg:promote DATABASE_URL --remote {}'.format(env.environment))
     local('heroku addons:create redistogo:nano --remote {}'.format(env.environment))
     local('heroku addons:create zeropush:inception --remote {}'.format(env.environment))


Test patch: