Skip to content
This repository has been archived by the owner on Jul 24, 2020. It is now read-only.

Don't require seed gems in production #1165

Closed
orenyk opened this issue Feb 22, 2015 · 3 comments · Fixed by #1204
Closed

Don't require seed gems in production #1165

orenyk opened this issue Feb 22, 2015 · 3 comments · Fixed by #1204
Assignees
@orenyk
Labels
diff: 2 pri: 3 type: enhancement
Milestone
5.2.0

Comments

@orenyk
Copy link
Contributor

orenyk commented Feb 22, 2015

See #1164
@orenyk orenyk added this to the 5.2.0 milestone Feb 22, 2015
@orenyk
Copy link
Contributor Author

orenyk commented Mar 27, 2015

Working on this, let's see what needs to be tweaked to make it work with them for Heroku.

@orenyk
Copy link
Contributor Author

orenyk commented Mar 27, 2015

Awesome, apparently nothing?

@orenyk
Copy link
Contributor Author

orenyk commented Mar 27, 2015

Sweet 😄

@orenyk orenyk closed this as completed Mar 27, 2015
@orenyk orenyk reopened this Mar 27, 2015
orenyk added a commit that referenced this issue Mar 27, 2015
@orenyk
Move seed script gems out of default group
59f325c 
Resolves #1165
- undid changes from Heroku implementation (#275)
@orenyk orenyk self-assigned this Mar 27, 2015
@orenyk orenyk mentioned this issue Mar 27, 2015
Merged
orenyk added a commit that referenced this issue Mar 30, 2015
@orenyk
add #1165
5e954ad
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@orenyk orenyk

Labels
diff: 2 pri: 3 type: enhancement
Projects
None yet
Milestone
5.2.0
Development

Successfully merging a pull request may close this issue.

[1165] Move seed script gems out of default group YaleSTC/reservations
1 participant
@orenyk