This gem allows you to have a central repository of the assets. The assets can be uploaded well
in advance and can be associated with the products/variants at the time of product/variant
This will also act as a central repository that can be used to access all the assets of the system
and can then be used in different products.
Has default folders “Documents”, “Photos” and “Graphics”
Assets can be uploaded to each folder by using the upload feature
Ability to view assets in List view
Ability to remove / edit / download each asset
Associate assets while creating product / variant
For more features or usage manual go here.
- Add this extension to your Gemfile with this line:
#### Spree >= 3.2
gem 'spree_digital_assets' , github: 'vinsol-spree-contrib/spree_digital_assets'
#### Spree < 3.2
gem 'spree_digital_assets', github: 'vinsol-spree-contrib/spree_digital_assets', branch: 'X-X-stable'
branch option is important: it must match the version of Spree you're using.
For example, use
3-0-stable if you're using Spree
3-0-stable or any
Install the gem using Bundler:
Run the installation generator
bundle exec rails g spree_digital_assets:install
bundle exec rake db:migrate
bundle exec rails g spree_digital_assets:seed
#### Spree >= 3.1
For Building Dependencies:
The dummy app can be regenerated by using:
appraisal spree-3-1 rake test_app
This will run rake test_app using the dependencies configured for Spree 3.1. Similarly you can use spree-3-2 and spree-master for generating dummy applications using dependencies for Spree 3.2 and latest version of Spree ```shell appraisal spree-3-1 rspec
This will run rspec using the dependencies configured for Spree 3.1. Similarly you can use spree-3-2 and spree-master to run rspec using dependencies for Spree 3.2 and latest version of Spree
#### Spree 3.0 and Spree 2.x
First bundle your dependencies, then run
rake will default to building the dummy app if it does not exist, then it will run specs. The dummy app can be regenerated by using
bundle bundle exec rspec spec
- Fork the project
- Make one or more well commented and clean commits to the repository. You can make a new branch here if you are modifying more than one part or feature.
- Add tests for it. This is important so I don’t break it in a future version unintentionally.
- Perform a pull request in github's web interface.
Copyright (c) 2017 vinsol.com, released under the New MIT License