Discussion
Loading...

Post

  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
GitRoot
@forge@gts.gitroot.dev  路  activity timestamp 3 weeks ago

Why gitroot is different? Why the need to build another forge? Just 2 concepts I have not found in all other forges:

- no database + no api == no vendor locking, your data is just aside your code. By data I mean: users, branches rights but also issues, boards and pipelines... Clone your repo all your data is on your computer, mirror to another forge (preferably @Codeberg 馃槏) and you have a backup.

- simple at start, grow only if needed == plugin based, you want to do a simple static blog: use only apex plugin. You want a full forge install ladybug, silo, grafter, pollen plugins and many more. Don't waste your server resources with unused features.

This 2 concepts drive the code every day. It's not simple (to code) but at the end of every day I'm happy with a simple (to use) forge.

This 2 concepts permit to do more with less and that is exactly what I want for my forge.

Something not clear here or in https://gitroot.dev please ask here, in DM, at contact@gitroot.dev, or in issues and I will try to explain.

Edit: added missing hashtags

#git #forge #selfhost #foss

  • Copy link
  • Flag this post
  • Block
Log in

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About 路 Code of conduct 路 Privacy 路 Users 路 Instances
Bonfire social 路 1.0.0 no JS en
Automatic federation enabled
  • Explore
  • About
  • Members
  • Code of Conduct
Home
Login