Skip to content

Open Collective's Image Server. For badges, banners, avatar, etc ...

License

Notifications You must be signed in to change notification settings

opencollective/opencollective-images

This branch is 1 commit ahead of main.

Folders and files

NameName
Last commit message
Last commit date
Dec 13, 2024
May 17, 2021
May 15, 2024
Mar 29, 2021
Oct 12, 2018
Sep 18, 2018
May 8, 2018
Apr 17, 2019
Jun 22, 2023
Sep 18, 2018
Mar 4, 2020
Jul 15, 2022
May 15, 2024
Nov 27, 2018
Aug 12, 2021
Mar 8, 2021
May 15, 2024
May 21, 2019
Nov 27, 2023
Feb 13, 2025
Feb 13, 2025
Jun 26, 2021

Repository files navigation

Open Collective Images

Dependency Status

Foreword

If you see a step below that could be improved (or is outdated), please update the instructions. We rarely go through this process ourselves, so your fresh pair of eyes and your recent experience with it, makes you the best candidate to improve them for other users. Thank you!

Development

Prerequisite

  1. Make sure you have Node.js version >= 18. We recommend using version 18, the one used in CI and production.
  • We recommend using nvm: nvm install.
  1. Make sure you have GraphicsMagick installed.
  • On Debian/Ubuntu: sudo apt-get install graphicsmagick
  • On MacOS (with Homebrew): brew install graphicsmagick

Install

We recommend cloning the repository in a folder dedicated to opencollective projects.

git clone [email protected]:opencollective/opencollective-images.git opencollective/images
cd opencollective/images
npm install

Environment variables

This project requires an access to the Open Collective API.

By default, it will try to connect to the Open Colllective staging API, you don't have to change anything.

If case you want to connect to the Open Collective API running locally:

Start

npm run dev

Contributing

Code style? Commit convention? Please check our Contributing guidelines.

TL;DR: we use Prettier and ESLint, we do like great commit messages and clean Git history.

Tests

You can run the tests using npm test.

Deployment

To deploy to staging or production, you need to be a core member of the Open Collective team.

We're currently relying on the following Heroku buildpacks:

Staging (heroku)

# Before first deployment, configure staging remote
git remote add staging https://git.heroku.com/oc-staging-image-server.git

# Then deploy main with
npm run deploy:staging

Production (heroku)

# Before first deployment, configure production remote
git remote add production https://git.heroku.com/oc-prod-image-server.git

# Then deploy main with
npm run deploy:production