- Ruby 48%
- HTML 22.8%
- JavaScript 16.9%
- CSS 11.4%
- Shell 0.5%
- Other 0.4%
9310b002d7The docker block copied bundler's cooldown wholesale, but Dependabot only accepts semver-major/minor/patch-days for ecosystems whose versions it classifies as semver, and container tags aren't. One invalid property invalidates the entire file rather than the block it sits in, so since this config landed in #248 the version updater has not run for any ecosystem at all: Your .github/dependabot.yml contained invalid details The property '#/updates/2/cooldown/semver-major-days' is not supported for the package ecosystem 'docker'. (and -minor-, -patch-) That is why #249's cooldown exclude for brakeman never took effect, and why #250 had to bump the workflow linter pins by hand while every other repo got a Dependabot PR. It also left `bin/brakeman --ensure-latest 15` armed with nothing to disarm it: the lock pins brakeman 8.0.6, and CI would have gone red roughly 15 days after 8.0.7 shipped. Security updates were never affected — those don't read this file, which is why the only four Dependabot runs here are single-gem security bumps. docker keeps default-days, which is supported for every ecosystem. |
||
|---|---|---|
| .github | ||
| app | ||
| bin | ||
| config | ||
| db | ||
| docs | ||
| hooks | ||
| lib | ||
| log | ||
| public | ||
| script | ||
| test | ||
| tmp | ||
| vendor | ||
| .dockerignore | ||
| .env.erb | ||
| .gitattributes | ||
| .gitignore | ||
| .pumaenv | ||
| .rubocop.yml | ||
| .ruby-version | ||
| config.ru | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| Dockerfile-export | ||
| Gemfile | ||
| Gemfile.lock | ||
| MIT-LICENSE | ||
| Procfile | ||
| Rakefile | ||
| README.md | ||
| SECURITY.md | ||
Campfire
Campfire is a web-based chat application. It supports many of the features you'd expect, including:
- Multiple rooms, with access controls
- Direct messages
- File attachments with previews
- Search
- Notifications (via Web Push)
- @mentions
- API, with support for bot integrations
Running your own Campfire instance
Campfire's Docker image contains everything needed for a fully-functional,
single-machine deployment. This includes the web app, background jobs, caching,
file serving, and SSL. You can use our pre-built image at
ghcr.io/basecamp/once-campfire:latest, or build your own from this repo.
Deploying with ONCE
The easiest way to self-host Campfire is with ONCE. It will guide you through the initial set up and then keep your instance up to date automatically.
If you don't already have once installed, run this on the machine you want to run Campfire on:
curl https://get.once.com | sh
once will launch as soon as the install is finished.
Choose Campfire from the list of applications, follow the instructions, and ONCE will take care of the rest.
If you prefer the command line to the dashboard, you can deploy directly:
once deploy ghcr.io/basecamp/once-campfire --host chat.example.com
Deploying with Docker
If you'd rather run the Docker image yourself, you can read more about that in the self-hosting guide.
Tip
When you start Campfire for the first time, you'll be guided through a wizard to create an admin account. The email address that you enter for the admin account will be visible on the sign-in page, it's there so that people have someone to contact if they need help with their account. If that bothers you, put in any email address you want and create yourself a new admin account.
Development
You are welcome - and encouraged - to modify Campfire to your liking. Please see our development guide for how to get Campfire set up for local development.
Security
See SECURITY.md for how to report a vulnerability and a description of our trust model.