If you go back to the overview tab, there are some instructions
If you go to the network tab, you will get IP address.
2. Jupyter Lab Configuration Once VM is Running
In local terminal:
ssh user@216.153.52.16
Password:
Xthequickbrownfox321.
Run:
jupyter lab --ip=0.0.0.0 --no-browser
for a Jupyter Lab or:
jupyter notebook --ip=0.0.0.0 --no-browser
for a Jupyter Notebook
After starting Jupyter Lab, it will provide a URL in the terminal, typically something like http://127.0.0.1:8888/?token=xxxxxxxx. You need to replace 127.0.0.1 with your VM's IP address (216.153.52.16 in your case)
Once the key pair is generated, you need to add the public key to your GitHub account. First, display your public key with the following command:
Copy the output, then go to GitHub, navigate to your account settings, click on the SSH and GPG link, and click Add Key to register the public SSH key with your account
Next, clone your GitHub repository to your VM. You can do this with the following command:
This will create a new directory named facebert containing your GitHub repository.
Step 3: Copy Files to the Repository Directory
Now, you need to copy the files you want to push to GitHub into the facebert directory. You can do this with the cp command. For example, to copy all files from the workspace directory, you can use the following command:
Step 4: Push Files to GitHub
Finally, you can push the files to GitHub. Navigate to the facebert directory and use the git add, git commit, and git push commands to add the files to the repository and push them to GitHub:
This will add all files in the facebert directory to the repository, commit the changes with the message "Add files from VM", and push the changes to the master branch of your GitHub repository
Please replace "master" with the appropriate branch name if your default branch is not named "master".
Navigate to your project directory:
Pull the Latest Changes:
Replace main with the branch name you want to update, if it's different.
Resolve Any Merge Conflicts:
If there are conflicts, you'll need to manually resolve them.
Check the Status:
After the pull, confirm everything is up to date and integrated.
Optional - Push Local Changes:
If you have made local changes to push.
Using git pull is more straightforward if you are comfortable with automatically merging changes without reviewing them first. Remember, git fetch and git merge give you more control over the process by allowing you to review changes before integrating them.
5. Data Acquisition and Preprocessing
Dataset Management
Download the required datasets directly to the VM.
Perform any necessary preprocessing steps, leveraging the VM's computational resources.