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

Reservations on Heroku #110

Closed
caseywatts opened this issue Jun 21, 2012 · 7 comments
Closed

Reservations on Heroku #110

caseywatts opened this issue Jun 21, 2012 · 7 comments
Assignees
Milestone

Comments

@caseywatts
Copy link
Collaborator

We want to be able to show off our work to the internet so they can see it~

We need:

  1. Host our site on Heroku
  2. Create non-CAS login or at least view
  3. Update our README file to actually convey information
  4. Maybe create a github public page?
@ghost ghost assigned caseywatts Jun 21, 2012
@caseywatts
Copy link
Collaborator Author

Our site is on heroku!
http://yalereservations.herokuapp.com/

@caseywatts
Copy link
Collaborator Author

I just want to note:
I had to comment out our add_index lines in each migration that had it because of how postgresql works (and Heroku requires we use that)
We should definitely find a way to re-add add_index in there - maybe in a new, migration file that'd work?

@noreaster
Copy link
Contributor

Hey look everyone, you can be Casey Watts on heroku....

@caseywatts
Copy link
Collaborator Author

This is definitely an underlying problem with the current_user function
:x
we went through that stuff quite quickly, it's not a good implementation yet. Is there a tutorial for how current_user is supposed to work? lolol

@caseywatts
Copy link
Collaborator Author

Opened #111 for the login problem

@caseywatts
Copy link
Collaborator Author

#111 is done >:D

@caseywatts
Copy link
Collaborator Author

This long list of things to do actually deserves its own mini-milestone methinks.
This particular issue managed to get Heroku working, so I'll close this one and make 3 more.

@orenyk orenyk mentioned this issue Jul 15, 2014
13 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants