aboutsummaryrefslogtreecommitdiffstats
path: root/activestorage
diff options
context:
space:
mode:
authorOleg <oleg@khabarov.ca>2017-10-06 12:50:05 -0700
committerOleg <oleg@khabarov.ca>2017-10-06 12:54:23 -0700
commit2ab561932e7ba76f4b39e9e32e1163567a0dc3fe (patch)
tree31165ce63c9dc19aa4d946481d0ec64197802a91 /activestorage
parent6375c9a3ae34cadd0d98e31ae1474fee26cf92ea (diff)
downloadrails-2ab561932e7ba76f4b39e9e32e1163567a0dc3fe.tar.gz
rails-2ab561932e7ba76f4b39e9e32e1163567a0dc3fe.tar.bz2
rails-2ab561932e7ba76f4b39e9e32e1163567a0dc3fe.zip
how do we install active_storage? [skip ci]
Diffstat (limited to 'activestorage')
-rw-r--r--activestorage/README.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/activestorage/README.md b/activestorage/README.md
index 8814887950..78e4463c5a 100644
--- a/activestorage/README.md
+++ b/activestorage/README.md
@@ -12,6 +12,10 @@ A key difference to how Active Storage works compared to other attachment soluti
`Blob` models store attachment metadata (filename, content-type, etc.), and their identifier key in the storage service. Blob models do not store the actual binary data. They are intended to be immutable in spirit. One file, one blob. You can associate the same blob with multiple application models as well. And if you want to do transformations of a given `Blob`, the idea is that you'll simply create a new one, rather than attempt to mutate the existing one (though of course you can delete the previous version later if you don't need it).
+## Installation
+
+Run `rails active_storage:install` to copy over active_storage migrations.
+
## Examples
One attachment: