nunoalexandre / broccoli Goto Github PK

Right now, the root view controller is the Tab VC with the Login / Signup controllers.
I'm not sure this is the best way to go. It seems better to have the launching controller delegating the next controller to present. Not sure this is exactly the best way, but overall the goal is to have an efficient and flexible way to either show the login/signup screens if the user is not logged in or the homepage otherwise.

Depends on #1 issue.
Should give success message or error message / feedback when trying to add an entry twice for the same day.

Now it is called Server, I want it to be called "Broccoli".

Heroku also offers auto deploy, but in order to deploy only after the CI tests have passed , I need to pay. So I want to have Travis deploying to Heroku after a successful build.

I don't want to use Alamofire directly. Instead, I want to have a wrapper that uses Alamofire but that is ready to use whatever else, not affecting the parts using this wrapper.

Following #16, I want to have a dedicated repository holding the phoenix api, and another one for the iOS project.

As Auth0 takes care of Users and their authentication, there is no need to have a User entity.
This involves removing its controller, tests and the relationship from UserDay to User.

Now if heroku pulls from master, it fails, since the buildpacks expect to find an elixir/phoenix project at the root of the pulled repository but it is within the ./server dir.

So either:

1. heroku doesn't auto deploy, but instead Travis triggers it running git subtree push --prefix server heroku master
2. find a way of having heroku building within ./server
3. split the repository: one for the phoenix app, other for the ios (and android later)