0% found this document useful (0 votes)
61 views5 pages

Betty Setup

Uploaded by

josiah omoba
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
61 views5 pages

Betty Setup

Uploaded by

josiah omoba
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Shell Scripts

 Allowed editors: vi, vim, emacs

 All your scripts will be tested on Ubuntu 20.04 LTS

 All your scripts should be exactly two lines long ($ wc -l file should print 2)

 All your files should end with a new line

 The first line of all your files should be exactly #!/bin/bash

More Info

Betty linter

To run the Betty linter just with command betty <filename>:

 Go to the Betty repository

 Clone the repo to your local machine

 cd into the Betty directory

 Install the linter with sudo ./install.sh

 emacs or vi a new file called betty, and copy the script below:

#!/bin/bash

# Simply a wrapper script to keep you from having to use betty-style

# and betty-doc separately on every item.

# Originally by Tim Britton (@wintermanc3r), multiargument added by

# Larry Madeo (@hillmonkey)

BIN_PATH="/usr/local/bin"

BETTY_STYLE="betty-style"

BETTY_DOC="betty-doc"

if [ "$#" = "0" ]; then

echo "No arguments passed."

exit 1

fi
for argument in "$@" ; do

echo -e "\n========== $argument =========="

${BIN_PATH}/${BETTY_STYLE} "$argument"

${BIN_PATH}/${BETTY_DOC} "$argument"

done

 Once saved, exit file and change permissions to apply to all users with chmod a+x betty

 Move the betty file into /bin/ directory or somewhere else in your $PATH with sudo mv betty
/bin/

You can now type betty <filename> to run the Betty linter!
0. Create and setup your Git and GitHub account
Step 0 - Create an account on GitHub [if you do not have one already]
Step 1 - Create a Personal Access Token on Github
To have access to your repositories and authenticate yourself, you need to create a Personal
Access Token on Github.
You can follow this tutorial to create a token.
Once it’s created, you should have a token that looks like this:

Step 2 - Update your profile on the Intranet


Update your Intranet profile by adding your Github username here
If it’s not done the Checker won’t be able to correct your work

Step 3 - Create your first repository


Using the graphic interface on the github website, create your first repository.

 Name: alx-zero_day
 Description: I'm now a ALX Student, this is my first repository as a full-stack
engineer
 Public repo
 No README, .gitignore, or license

Step 4 - Open the sandbox


On the intranet, just under the task, click on the button and run to start the machine.
Once the container is started, click on to open a shell where you can start work from.

Step 5 - Clone your repository


On the webterm of the sandbox, do the following:

 Clone your repository

root@896cf839cf9a:/# git clone


https://{YOUR_PERSONAL_TOKEN}@github.com/{YOUR_USERNAME}/alx-zero_day.git
Cloning into 'alx-zero_day'...

warning: You appear to have cloned an empty repository.


Replace {YOUR_PERSONAL_TOKEN} with your token from step 1
Replace {YOUR_USERNAME} with your username from step 0 and 1
Pro-Tip: On windows, use CTRL + A + V to paste in the web terminal

Step 6 - Create the README.md and push the modifications


 Navigate to this new directory. Tips

root@896cf839cf9a:/# cd alx-zero_day/
root@896cf839cf9a:/alx-zero_day#

 Create the file README.md with the content My first readme. Tips

root@896cf839cf9a:/alx-zero_day# echo 'My first readme' > README.md


root@896cf839cf9a:/alx-zero_day# cat README.md
My first readme

 Update your git identity

root@896cf839cf9a:/alx-pre_course# git config --global user.email "[email protected]"


root@896cf839cf9a:/alx-pre_course# git config --global user.name "Your Name"

 Add this new file to git, commit the change with this message “My first commit” and push to
the remote server / origin

root@896cf839cf9a:/alx-zero_day# git add .


root@896cf839cf9a:/alx-zero_day# git commit -m 'My first commit'
[master (root-commit) 98eef93] My first commit
1 file changed, 1 insertion(+)
create mode 100644 README.md

root@896cf839cf9a:/alx-zero_day# git push


Enumerating objects: 3, done.
Counting objects: 100% (3/3), done.
Writing objects: 100% (3/3), 212 bytes | 212.00 KiB/s, done.
Total 3 (delta 0), reused 0 (delta 0)

To https://github.com/{YOUR_USERNAME}/alx-zero_day.git
* [new branch] master -> master

Good job!
You pushed your first file in your first repository of the first task of your first ALX School project.
You can now check your repository on GitHub to see if everything is good.

You might also like