kytta, (edited )
@kytta@fosstodon.org avatar

My fellow devs, I need your opinion:

Say, you have a software project. To do some operations more quickly, you write helper scripts. Think build.sh, download_dependencies.py, whatever. You may use them yourself or in CI.

What is your directory name of choice for these scripts?

See next post for clarification.

frank,
@frank@frankwiles.social avatar

@kytta I use “just” instead to build them. Sort of like Makefiles but better.

pmakholm,
@pmakholm@fosstodon.org avatar

@kytta Theoretically I would use ./scripts for development tools and ./bin for other maintenance tools. Deploy tools might fall in either category depending on the type of project.

In practice I often start out by just having one of those and dump everything there. In that case it might be a bit random if it ends up being named ./bin or ./scripts.

kytta,
@kytta@fosstodon.org avatar

./scripts is so far the most popular, it’s just what I have seen across projects.

./script was proposed (and is still used?) by GitHub. See https://github.com/github/scripts-to-rule-them-all

./build is sometimes used because these scripts are often executed at build-time (and thus in CI)

Another thing I’ve seen were scripts in the repository root, but for the sake of the poll let’s assume there are too many scripts for this.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • rosin
  • cisconetworking
  • GTA5RPClips
  • osvaldo12
  • khanakhh
  • DreamBathrooms
  • magazineikmin
  • Youngstown
  • everett
  • mdbf
  • slotface
  • InstantRegret
  • kavyap
  • cubers
  • megavids
  • modclub
  • normalnudes
  • Durango
  • thenastyranch
  • ethstaker
  • tacticalgear
  • ngwrru68w68
  • Leos
  • anitta
  • provamag3
  • tester
  • JUstTest
  • lostlight
  • All magazines