https://github.com/maxpleaner/bandcamp_utilities
https://github.com/maxpleaner/bandcamp_utilities
Last synced: 11 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/maxpleaner/bandcamp_utilities
- Owner: MaxPleaner
- Created: 2019-11-23T22:59:28.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2023-01-20T20:56:35.000Z (over 3 years ago)
- Last Synced: 2025-01-29T12:15:23.627Z (over 1 year ago)
- Language: JavaScript
- Size: 274 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 5
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
## Bandcamp Utils
This project is split into two parts - a chrome extension and a Sinatra backend.
---
### Backend - Setup
1. Make sure you have Ruby, Bundler, Python, Pip, and Redis installed.
2. `cd backend`
2. Install Ruby dependencies with `bundle install`.
3. Install Python dependencies with `pip install -r requirements.txt`
5. start server with `rackup`
### Frontend - Setup
No setup is necessary for the front end:
1. Go to `about://extensions`
2. Enable developer mode
3. Press "load unpacked extension" (button is on the top left of the screen)
4. Double click into the `chrome_extension/` directory and press OK
### Todos
- (X) Clean up code
- (X) Remove `clear_db` endpoint
- (X) Remove injection vulnerability
- (X) Add accounts system
- (X) Add backend for reviews system
- (X) get redis deployment working with heroku
- (X) auto add items to wishlist
- (X) implement designs from Thyphex
- (X) make it work with more bandcamp locations
- (X) Go through TODOS in source code
### Backend - Deployment
**Note, this is not working currently, I need to update after adding the Redis dependency**
It can be deployed to Heroku, if you follow these steps:
1. Make a new git repo and move the `backend/` folder there (add and commit everything).
2. Add the heroku remote
3. Setup buildpacks:
```
heroku buildpacks:add heroku/ruby
heroku buildpacks:add --index 1 heroku/python
heroku buildpacks:set heroku/ruby
```
_Note, that last line is necessary, to declare which one is the "primary" buildpack._
4. Deploy with `git push heroku master`