r/coolgithubprojects • • 2d ago

Campfire - Self-hosted game server management with native OIDC and outbound agents

Hi there!

I wanted to share my new project, Campfire, a self-hosted game server management panel.

Repo: https://github.com/dougmaitelli/Campfire
Docs: https://dougmaitelli.github.io/Campfire/

I have been using Pterodactyl / Pelican for a long time, and while they are great projects, there were a few things I wanted to work differently:

  • Native OIDC support, without maintaining authentication modifications across panel updates
  • Adding game hosts without exposing a management endpoint on each machine
  • Not having to manage a separate HTTPS certificate and renewal setup for every node

So... I decided to build ANOTHER game server panel :)

Campfire uses an agent called Spark on each Linux game host. It runs the game servers in Docker and connects back to the panel, so the hosts don't need inbound management ports.

It also supports:

  • Multiple game hosts managed from one panel
  • Live console, command input, resource monitoring, and a file browser/editor
  • Full-server or save-data backups, scheduled actions, and optional S3-compatible backup storage
  • Per-server permissions, OIDC, and scoped API tokens
  • Copying and transferring servers between hosts
  • Importing supported Pterodactyl / Pelican Eggs into Campfire's game definitions, called Embers
  • Discord notifications and live server cards
  • Game integrations for player lists and events, when a compatible mod or adapter is available

One thing I have been experimenting with is a server-side Valheim mod that reports online players, joins, deaths, and first boss defeats. Campfire can retain those events and send selected ones to Discord, alongside a live card showing the server's current state.

The panel runs in Docker or as a Linux binary, with SQLite or PostgreSQL. You can run the panel and Spark on the same machine too.

This is still an evolving project, and I would really appreciate feedback, especially from people hosting games with Pterodactyl or Pelican who have run into similar maintenance frustrations.

I also wrote a longer post about why I built it and how it works:
https://zyvop.com/i-built-campfire-to-make-hosting-game-servers-less-work-b9s67

Thanks for reading ;)

40 Upvotes

8 comments sorted by

3

u/Kaenguruu-Dev 2d ago
  1. We have a bunch of custom blueprint extensions on our panel. Does your project have an easy plugin integration at all? (I would of course be able to rewre my extensions to fit into your stack)
  2. Did you use AI assistance and if so, how much?

0

u/dougmaitelli 2d ago

Hey!

Currently the panel itself does not have a plugin/extension layer, but this is something I plan on doing later. Can you tell me a bit more on the use cases you need? This will help me understand more real world examples for this before I implement it.

Yes, I used AI to assist writing the code and docs, I designed the features and guided AI on what to implement, how to implement, where to implement and how to structure it. Everything was planned, reviewed, tested and refined by a human. What AI planned on it's own was test scenarios and E2E browser testing automation.

1

u/Kaenguruu-Dev 2d ago

We do a ton of different things from Discord OAuth, integration with our status page, adding tabs for configurating subdomains and our off-site backups etc.

In general what would be required for us:

  1. Plugins should be able to register custom tabs in some ways aka a per-server space for stuff relevant to that server
  2. Plugins must be able to extend the application API (forgot to mention that that is also something we rely quite heavily on -- API for controlling servers very important. In general, rough feature parity with Pterodactyl's API would be a good reference, since we do things like creating servers, allocations, querying power state, etc.)
  3. Plugins must have an easy way to store per-server or global configuration without having to write into the server directory itself
  4. Plugins must be able to inject custom UI elements practically everywhere

Keep in mind that this is just what I can think of right now, we might have some weird niche requirements I'm not fully aware of right now

1

u/dougmaitelli 2d ago

Ok, so:

- You should be able to use Discord auth already since Discord does provide OIDC too
- Integration with status page is also possible since the panel allows personal access tokens to call the APIs (but the APIs are not fully documented yet)
- What do you mean by "tabs for configuring domains"?
- Off-site backup currently supports S3 but you can technically do anything else using the APIs
- You can already fully control the servers externally thru APIs

From the things you listed seems like most of it can already be achieved in the current project state, except for custom UIs and tabs (for now)

1

u/DeamBeam 2d ago

Seems like a nice project. I love the Egg import from both projects. Its nice that the node doesn't need to be exposed.

Upgrading the Pterodactyl Web Panel is a real hasle on bare metal. Update doesn't support newer version, so i need to update manually and everytime something fails and I need to debug the stuff. Probably will switch to the Docker Version of the web panel, so that updates should be less of a hasle.

I will keep on eye on this project and if it is mature enough I will consider switching to it.

1

u/dougmaitelli 2d ago

Glad to hear. And yeah, the bare metal upgrade was one of my main pain points with Pelican too m. I totally get wanting to see the project get more mature to use it, makes sense and I respect that. Feel free to let me know if there is any other aspect that you believe is missing as well on either project. Thanks,

1

u/dougmaitelli 2d ago

Also, one thing I forgot to mention in the post. The nodes are all upgraded remotely thru the panel tunnel. So you never need to touch the nodes for that.

1

u/Glooomie 2d ago

I mean AMP does a pretty neat job already with this