sequelizer 0.0.2 → 0.0.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/CHANGELOG.md +15 -0
- data/README.md +10 -2
- data/lib/sequelizer/cli.rb +6 -0
- data/lib/sequelizer/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 850cd00d16c6c1ffa076c95ac826cf48322ff678
|
4
|
+
data.tar.gz: fa352fe12ffb3d6affc33402ea40f3492af5349a
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 8401cda3328933d79d078bbc20143d9089db5faa638a476eae64ce3fc4bf50dfe7b08fe50c04de0e2e9cee4f0628f55371d4138d7d98dcaf9e816857c18a879d
|
7
|
+
data.tar.gz: 57a62e5da3227d41f3825e5ba75aad372b9ebd54d8fa72e798e0c7de9ee53e1568909863a9e15e0825373768043059e9ad4ca41bce729be39d1c049d2e9b7f9d
|
data/CHANGELOG.md
CHANGED
@@ -1,5 +1,20 @@
|
|
1
1
|
# Changelog
|
2
2
|
All notable changes to this project will be documented in this file.
|
3
|
+
|
4
|
+
## 0.0.3 - 2014-07-10
|
5
|
+
|
6
|
+
### Added
|
7
|
+
- Ability to view configuration by running `sequelizer config`
|
8
|
+
|
9
|
+
### Deprecated
|
10
|
+
- Nothing.
|
11
|
+
|
12
|
+
### Removed
|
13
|
+
- Nothing.
|
14
|
+
|
15
|
+
### Fixed
|
16
|
+
- Nothing.
|
17
|
+
|
3
18
|
## 0.0.2 - 2014-07-10
|
4
19
|
|
5
20
|
### Added
|
data/README.md
CHANGED
@@ -26,9 +26,17 @@ Or install it yourself as:
|
|
26
26
|
|
27
27
|
To get the most out of Sequelizer, you'll need to create a config/database.yml file or a .env file and specify your database configuration options in that file.
|
28
28
|
|
29
|
-
|
29
|
+
Sequelizer comes with a handy command that will print out your connection parameters. Just run:
|
30
30
|
|
31
|
-
|
31
|
+
bundle exec sequelizer config
|
32
|
+
|
33
|
+
You'll also need to make sure the gem for your database is installed. You can do this by adding the gem to your application's Gemfile.
|
34
|
+
|
35
|
+
Sequelizer comes with a handy command that will update your Gemfile for you. Once you've specified your database configuration, run
|
36
|
+
|
37
|
+
bundle exec sequelizer update_gemfile
|
38
|
+
|
39
|
+
The command will look up the right gem to use with the adapter you've specified, add a line to your Gemfile specifying that gem, and run `bundle install` to install the gem for you.
|
32
40
|
|
33
41
|
Once you've specified your options and made sure your database's gem is installed, simply include the Sequelizer module in any class that needs a database connection and you'll get two handy-dandy methods: `db` and `new_db`
|
34
42
|
|
data/lib/sequelizer/cli.rb
CHANGED
@@ -1,4 +1,5 @@
|
|
1
1
|
require 'thor'
|
2
|
+
require 'pp'
|
2
3
|
require_relative 'gemfile_modifier'
|
3
4
|
|
4
5
|
module Sequelizer
|
@@ -9,5 +10,10 @@ module Sequelizer
|
|
9
10
|
def update_gemfile
|
10
11
|
GemfileModifier.new(options).modify
|
11
12
|
end
|
13
|
+
|
14
|
+
desc 'config', 'prints out the connection parameters'
|
15
|
+
def config
|
16
|
+
pp Options.new.to_hash
|
17
|
+
end
|
12
18
|
end
|
13
19
|
end
|
data/lib/sequelizer/version.rb
CHANGED