Signed-off-by: a9 <email@example.com>
|9 months ago|
|samples||1 year ago|
|src||9 months ago|
|static/css||1 year ago|
|templates||1 year ago|
|.dockerignore||1 year ago|
|.eslintrc||1 year ago|
|.gitignore||1 year ago|
|Dockerfile||1 year ago|
|FUNDING.yml||1 year ago|
|LICENSE||1 year ago|
|README.md||9 months ago|
|package-lock.json||1 year ago|
|package.json||1 year ago|
|tsconfig.json||1 year ago|
rimgu: image host alternative frontend
rimgu is an alternative frontend / proxy for imgur
NOTICE: While rimgu development may be picked up again at some point, users are currently better serviced with the (unaffiliated) golang rewrite rimgo. Contributions are still welcome but please don't expect maintainer development for the time being.
It's lightweight and easy to configure.
Inspired by and (soon) integratable with:
- URL-compatible with i.imgur.com - just replace the domain in the URL
- Images and videos (gifv, mp4) returned directly
- Galleries with comments
- User page
- Tag page
- Supports http(s) forward proxy
This is currently very early stage software. Some things left to implement (contributions welcome!):
- Streaming (currently media is downloaded in full in rimgu before it's returned)
- Pretty CSS styling (responsive?)
- Automatically fetch / rotate / renew client ID
- Support for other popular image sites than only imgur
- Filtering and exploration on user/tags pages
- Responsive scaling of videos on user/tags pages
- Prometheus metrics
- SOCKS5 proxy support
Things that are currently considered out of scope:
- Uploading/commenting/voting/etc - rimgu is read-only for now.
- Caching, authentication, serving HTTPS, rate limiting etc - Just use a proxy or load balancer like squid/haproxy/envoy/nginx/traefik/caddy.
- Anything requiring client-side JS or client-side directly interacting with upstream servers
- node.js >= v16 (earlier most likely works fine)
$ npm install && npm run build
$ docker build -t rimgu:latest .
$ node dist/index.js
$ docker run -p 8080:8080 -e -it RIMGU_ADDRESS=0.0.0.0 -e RIMGU_PORT=8080 rimgu:latest
If you decide to run a public instance, consider opening an issue to have it listed here :)
Rimgu is configured via environment variables. See available variables in src/config.ts.
API and client ID
Media and galleries can be scraped without authorization through the public web interface. Some imgur functionality (comments, full albums) requires a provisioned client ID to authenticate requests.
You can get a client ID by opening https://imgur.com in a web browser and looking for requests to
https://api.imgur.com/...?client_id=1234567deadbeef under "Network" in the developer console.
To run without API/key:
To run with API/key:
This key may be used to track you and could be banned when overused. Keep this in mind before exposing a public instance with a client key associated with your personal imgur account. Consider any ToS you may have signed before associating a personal imgur account with a public instance.
PRs are welcome! Before submitting a PR, please make sure linting passes successfully:
$ npm run lint
This software is released under the AGPL 3.0 license. In short, this means that if you make any modifications to the code and then publish the result (e.g. by hosting the result on a webserver), you must publicly distribute your changes and declare that they also use AGPL 3.0.
You are also requested to not remove attribution and donation information from forks and publications.
Donations are welcome and will contribute to development, maintenance and a future public hosted instance.