json_voorhees 0.4.0 → 0.4.1
Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 945f02ea35215e8375a27e6c40e1681dae1fdcba
|
|
4
|
+
data.tar.gz: 9f9c4b49624b87324e1ff8a948ad787c030b4a23
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 866d04ebe89f94d9023d7c05592ae974ad73239bc9fa9e0c9eb84c6c9fca53a418a820805b5eac94f262900d0e23a0e7a71a21454f3f33c8f4a9ad5e4a486f24
|
|
7
|
+
data.tar.gz: 45dd9bd147287895e8a9cb019d974c0487e7271a5b136492ccdff6c0093126e833ad969ed7f1e7d1ee3d427426d7d63e6d3cf4266854cc94b4c9231425458163
|
data/README.md
CHANGED
|
@@ -65,6 +65,8 @@ running rspec from the main app.
|
|
|
65
65
|
Steps 1 through 2 are only done once. You need to run massive_scaffold for each
|
|
66
66
|
resource.
|
|
67
67
|
|
|
68
|
+
I usually set the app up, and then design the database. I make a list of all the models I need, then separate them into engines. Then I run 20 or so massive scaffolds using "&&". The result is a functioning backend that only needs the model relationships wired together. The default tests get you pretty far.
|
|
69
|
+
|
|
68
70
|
## Individual Generator Use
|
|
69
71
|
|
|
70
72
|
If massive scaffold is too bulky for you, you have the option of running the
|
|
@@ -108,3 +110,5 @@ gem file to that. Edit what you want.
|
|
|
108
110
|
To setup admin restrictions, use the attributes for the admin
|
|
109
111
|
class and put before_filters before all of the CRUD actions.
|
|
110
112
|
Make sure the current_user has the correct permissions.
|
|
113
|
+
|
|
114
|
+
If active admin is used (it is by default) the admin section username is admin and password is password. Otherwise the password is password123.
|