aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRolandas Barysas <rb@atomicflow.org>2017-07-27 18:47:26 +0300
committerGeorge Claghorn <george.claghorn@gmail.com>2017-07-27 11:47:26 -0400
commit293db49b7f5969d11d5599f97bd968dbe64c7f8b (patch)
tree3c51e4a28de1190a84d0eab50dd812c8d1c360d8
parentc68bdcd209f7568c1dde91a4a6a967571222d2fa (diff)
downloadrails-293db49b7f5969d11d5599f97bd968dbe64c7f8b.tar.gz
rails-293db49b7f5969d11d5599f97bd968dbe64c7f8b.tar.bz2
rails-293db49b7f5969d11d5599f97bd968dbe64c7f8b.zip
Fix broken links in README
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 705659b9aa..328bf01672 100644
--- a/README.md
+++ b/README.md
@@ -11,7 +11,7 @@ MiniMagick supported transformation.
## Compared to other storage solutions
-A key difference to how Active Storage works compared to other attachment solutions in Rails is through the use of built-in [Blob](https://github.com/rails/activestorage/blob/master/lib/active_storage/blob.rb) and [Attachment](https://github.com/rails/activestorage/blob/master/lib/active_storage/attachment.rb) models (backed by Active Record). This means existing application models do not need to be modified with additional columns to associate with files. Active Storage uses polymorphic associations via the join model of `Attachment`, which then connects to the actual `Blob`.
+A key difference to how Active Storage works compared to other attachment solutions in Rails is through the use of built-in [Blob](https://github.com/rails/activestorage/blob/master/app/models/active_storage/blob.rb) and [Attachment](https://github.com/rails/activestorage/blob/master/app/models/active_storage/attachment.rb) models (backed by Active Record). This means existing application models do not need to be modified with additional columns to associate with files. Active Storage uses polymorphic associations via the join model of `Attachment`, which then connects to the actual `Blob`.
These `Blob` models 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 (though of course you can delete that later if you don't need it).