-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathflow.txt
31 lines (21 loc) · 1.76 KB
/
flow.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
1. Makefile ---> will just install python and adding the executeable to path, and also chmodding the executeable since it will run with a shebang line. We will also have to make sure at this stage that we are fetching the needed programs, as well as switching to a venv as described in our venv file. The services will be created using make init
make
make clean install #from this point the user should be able to run the main "executeable" (not sure if this is the correct term for a scripting lang)
besides this we should have a consice way of uninstalling, maybe an uninstall script, since this bot probably will create a lot of moving parts (at least 3)
2. after this you should be able to type "rsab" from anywhere in the terminal, which should get you to the setup
3. *setup process* #Think this is mostly correct, might have to do some tiny tweaks to it
4. Prompt user to choose 1. if they want to start a service(os dependent) for the bot, and 2. if they want to start the bot right away.
5. *starting bot definition*
6. I think that the poolscan will be an ongoing system service
7. And maybe the best way to do the rest of the computations will be through using cronjobs. Think this might be best done somewhat compartmentalized, so maybe we'll go with FA scans every 15 minutes and then TA scans every 5 minutes.
Flags:
-u --update = Updating to latest version using github
-i --init = If you want to redo the config file
-g --flagRemoval = Removes the record flag
-r --restart = Stop and restartign bot
-x --stop = Stop bot
-t --test = For Development testing
-s --start = Start the bot
-fs --faScan = Perform the FA scan
-ts --taScan = Perform the TA scan
-f --fetch = Scan for new tokens