Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Resolve PostgreSQL issues #38

Closed
olasitarska opened this issue Jul 21, 2014 · 1 comment · Fixed by #57
Closed

Resolve PostgreSQL issues #38

olasitarska opened this issue Jul 21, 2014 · 1 comment · Fixed by #57
Assignees
@oinopion

Comments

@olasitarska
Copy link
Member

Possibly doing a sqlite setup on local and using Postgres only for Heroku as suggested by @lukaszb and few others would be a much (much, much!) better way.
@keimlink
Copy link
Contributor

Agreed! Two members of my group successfully used SQlite locally and deployed to Heroku using PostgreSQL there.

@oinopion oinopion self-assigned this Jul 26, 2014
@EdgyEdgemond EdgyEdgemond mentioned this issue Jul 26, 2014
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@oinopion oinopion

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use SQLite as default database EdgyEdgemond/tutorial
3 participants
@oinopion @keimlink @olasitarska