* Update view.jet.html
* Update router.go
* Create stats.go
* Update view.jet.html
* Update stats.go
* Update stats.go
* rollback
* returns -1 by default
* Update stats.go
* Update stats.go
* Import goscrape & torrent
* copypaste stats.go from scrapers
* travis
* Update stats.go
* Update stats.go
* Put fresh stats into a <span>
* Background-color for freshly fetched stats
* ditto but for tomorrow
* "Loading..." text in case it gets a bit too long
* Stat fetching in controller (missing DB update)
* Update last scraped date too
* update torrent.Scrape tho it doesn't do anything
* forgot to edit a name
* Update scrape.go
* Update stats.go
* Update stats.go
* flush cache to update stats in listing
* Change function name
* Update stats.go
* Update stats.go
* fix travis
* Update view.jet.html
* Update stats.go
* Update stats.go
* Update stats.go
* Update stats.go
* Update stats.go
* Added configor as a new library
Now config is a singleton. You only need to do config.Get() instead of doing config.Conf.
* Forgot godep save 🐤
* Fix accidental removal of }
Showing how we can remove services, preventing cyclic imports and lessing the number of imports.
Now db is in models. Db and models are highly tightened, according to go standards, you should put them in the same package.
In models, there are folders separating the different methods used to modify the models. For example, if you want to create a user, you have to use /models (for the user struct) and /models/user (for creating a user.
However, if you want to delete a torrent, you just have to import /models and do torrent.Delete(definitely bool).
By the way packages in models are the plural name of a model. For example, you have torrent.go for a torrent model and its package torrents for db stuff related functions (Find, Create, Some helpers)
