Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update README to fix persistence config info (it isn't needed!) #7

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README to fix persistence config info (it isn't needed!) #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 2 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,11 +12,6 @@ Create an Heroku app:

heroku create APP_NAME

Add database for persistance:

heroku addons:create heroku-postgresql:hobby-dev
heroku config:set DATABASE_URL=<copy the newly created database url here>

Configure the app by providing your broker url (RabbitMQ, Redis, what have you) and a password for logging into Flower:

heroku config:set BROKER_URL=redis://...
Expand All @@ -27,3 +22,5 @@ Push to heroku:
git push heroku master

Now visit the app. It will ask for a username and a password which you defined above.

Although Flower's persistence is enabled, it depends on writing to the local filesystem, [which is ephemeral on Heroku](http://stackoverflow.com/questions/12416738/how-to-use-herokus-ephemeral-filesystem). Therefore the persisted data will be lost when your Heroku Dyno restarts, for example after deploying config or code changes. However Flower persistence is [mostly a convenience feature](http://flower.readthedocs.io/en/latest/config.html#persistent).