Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rename and centralize our tools #118

Open
jonenst opened this issue Dec 29, 2020 · 5 comments
Open

rename and centralize our tools #118

jonenst opened this issue Dec 29, 2020 · 5 comments

Comments

@jonenst
Copy link
Member

jonenst commented Dec 29, 2020

  • wipe doesn't wipe (it creates a new db and changes the name of the current db in the config database)
  • replicate doesn't really replicate (it ensures the couchdb replication is running by repeatadily starting it. Just because couchdb sometimes stops replicating), and it does a lot more ( sends text messages, fixes bib input errors and merges conflicts).

something like this ?
loader -> stk-load-contestants
wipe -> stk-create-new-db
replicate -> stk-race-controller

we could put everything in a single docker image with the correct entrypoint:
something like this ?

docker run stk load-contestants
docker run stk controller checkpoint 2
@samueltardieu
Copy link
Member

samueltardieu commented Dec 29, 2020

Creating a unique application would probably ease testing and maintenance. I am all for it.

replicate which would probably be (as the largest application today) the host for those new applications already handles subcommands.

@Tomo59
Copy link
Member

Tomo59 commented Jan 3, 2021

Let's say the new binary is named stk and this binary handles subcommands, what do you think about:

  • replicate checkpoint -> stk checkpoint
  • replicate init -> stk init
  • replicate master -> stk master
  • replicate mirror -> stk mirror
  • replicate slave -> stk slave
  • wipe -> stk create-new-db
  • loader -> stk load-contestants
  • stats -> stk simulate-race

@samueltardieu
Copy link
Member

Except for simulate-race which does not convince me (since it doesn't simulate a full race), I like those suggestions.

@jonenst
Copy link
Member Author

jonenst commented Jan 5, 2021 via email

@sp4ce
Copy link
Contributor

sp4ce commented Jan 8, 2021

My 2 cents:

replicate master -> stk captain
replicate slave -> stk crew

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants