Explorar el Código

Merge pull request #158 from tobiasmcnulty/heroku-fixes

Add instructions & requirements for populating S3 bucket with demo data
Tobias McNulty hace 7 años
padre
commit
78825efe4b
Se han modificado 2 ficheros con 7 adiciones y 0 borrados
  1. 5 0
      readme.md
  2. 2 0
      requirements/production.txt

+ 5 - 0
readme.md

@@ -159,6 +159,11 @@ environment, set the same environment variables there using the method appropria
 
 
 Once Heroku restarts your application or your Docker container is refreshed, you should have persistent media storage!
 Once Heroku restarts your application or your Docker container is refreshed, you should have persistent media storage!
 
 
+To copy the initial data included with this demo to the S3 bucket (assuming you ran `./manage.py load_initial_data` per
+the above), you can use the AWS CLI included with the requirements:
+
+    heroku run aws s3 sync bakerydemo/media/original_images/ s3://<bucket-name>/original_images/
+
 # Next steps
 # Next steps
 
 
 Hopefully after you've experimented with the demo you'll want to create your own site. To do that you'll want to run the `wagtail start` command in your environment of choice. You can find more information in the [getting started Wagtail CMS docs](http://wagtail.readthedocs.io/en/latest/getting_started/index.html).
 Hopefully after you've experimented with the demo you'll want to create your own site. To do that you'll want to run the `wagtail start` command in your environment of choice. You can find more information in the [getting started Wagtail CMS docs](http://wagtail.readthedocs.io/en/latest/getting_started/index.html).

+ 2 - 0
requirements/production.txt

@@ -11,3 +11,5 @@ botocore==1.7.10
 aws-requests-auth==0.4.0
 aws-requests-auth==0.4.0
 django-redis==4.8.0
 django-redis==4.8.0
 django_cache_url==2.0.0
 django_cache_url==2.0.0
+# For copying initial media to S3 bucket
+awscli==1.11.23