Skip to content

Commit

Permalink
typos
Browse files Browse the repository at this point in the history
  • Loading branch information
minhadona committed May 19, 2022
1 parent 0adc2f1 commit 9de1d6d
Showing 1 changed file with 9 additions and 8 deletions.
17 changes: 9 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,25 +37,25 @@ If you're using an unix based system, the command `which python3` must do the jo

![](https://i.imgur.com/xxFADqu.png)

so, the path where your python binary is locate is */opt/homebrew/bin/python3*
so, this is the path where your python binary is located: */opt/homebrew/bin/python3*

<br>
<br>


-----------------------
# 2. Create an app password specially for this script
We know you don't want to expose any password and you might create infinite app passwords for your e-mail to use every single of them in a different app! Just follow [this](https://support.google.com/accounts/answer/185833?hl=en) AND GRAB YOUR 16 MAGIC CHARS for this script!
We know you don't want to expose any password and, well, you can create infinite app passwords for your e-mail to use every single of them in a different app! Just follow [this](https://support.google.com/accounts/answer/185833?hl=en) AND GRAB YOUR 16 MAGIC CHARS for this script!


<br>
<br>

-----------------------
# 3. Export as environment variable
This handles your super secret 16-digit password even if you're out of your beloved machine. If you are doing some deploy on Heroku, for example, the syntax to get the environment variables is exactly the same. If works on cron, works on your secret deploy. The variables just have to be there!
This handles how we authenticate with your super secret 16-digit password even if you're out of your beloved machine. If you are doing some deploy on Heroku, for example, the syntax to get the environment variables is exactly the same. If works on cron, works on your secret deploy. **The variables just have to be there!**

`$ export EMAIL_PASSWORD=this16digitspassword`
`$ export EMAIL_PASSWORD=your16digitspassword`
`$ export EMAIL_USERNAME=email@gmail.com`

This is the gmail credentials you'll use to authenticate **AND** to whom you'll send the table we've fetched from the website!
Expand Down Expand Up @@ -87,23 +87,24 @@ if the file successfully executes, this is what you'll get:
- On your terminal, type `$ crontable -e`
- This will open a file, every line is potentially a task that you can schedule your computer to execute for you! In this case, we'll schedule a python file.
- Translate your schedule to [cron syntax](https://crontab.guru/)
- To enable edition, type `i` (yes, like insertion)
- To enable edition of the file, type `i` (yes, like insertion)
- Now, edit one line by following the example:
```
05 11 * * 5 /opt/homebrew/bin/python3 ~/Documents/scripts/b4s.py
```

This would execute the file b4s.py file, located on Documents/scripts, using python3 interpreter, located at homebrew binaries folder every friday at 11h05
This statement would execute the file b4s.py file, located on Documents/scripts, using python3 interpreter, located at homebrew binaries folder every friday at 11h05

After settling your crontable file, type `Esc` to leave edition mode

- `$ Esc`
- `$ :wq` to write and quit the file
- you must see the output `crontab: installing new crontab`


<br>
<br>

*ps: the file b4s.ipynb has nothing to do with the script, but I love jupyter since it's easier to manipulate tiny pieces of code; thus the file you'll use to schedule your cron is the .py one*
*ps: the file b4s.ipynb has nothing to do with the script, but I love jupyter since it's easier to manipulate tiny pieces of code; the file you'll use to schedule your cron is the .py one*

## ✧・゚: *✧・゚:* ✧・゚: *✧・゚:* This is it. Suggestions? [Mail me](mailto:minhadona@tuta.io) ✧・゚: *✧・゚:* ✧・゚: *✧・゚:*

Expand Down

0 comments on commit 9de1d6d

Please sign in to comment.