For Your Eyes Only

For Your Eyes Only

We are back to the good stuff again!
Sometimes, we need to store information in our code that we don't want others to be able to see. Like passwords and such.
Replit repls are public, and we don't want other little forkers to get their hands on our passwords, do we?

👉 We can make information like this secret in our repls by selecting 'secrets' from the left hand toolbar.

👉 Secrets are a lot like dictionaries in that they have a key which is used to access a value. Let's set up a password secret.

As soon as we've done that, we get a bunch of options further down our secrets menu. They use the os library, so we'll need to import that.

👉 Now let's use our secret to set up a very simple login system.

import os
password = os.environ['password'] # Uses the os library to talk to the environment and get the secret password stored there.
userPass = input("Password > ")
if userPass == password:
print("Well done")
else:
print("Better luck next time")
The secret data does not get copied when the repl is forked, so it is protected from others getting a copy.

Comments

Automate! Automate!

Making this customizable 👉So how about making our search user customizable? In the code below, I have: Asked the user to input an artist (line 14) Tidied up their input (line 15) formatted the search URL as an fString that includes the artist (line 19) Here's tAutomate! Automate! We are so close. I can taste it, folks! Massive kudos on getting this far! Today's lesson, however, will work best if you have one of Replit's paid for features (hacker plan or cycles). Free plan Repls 'fall asleep' after a while. Automation kinda relies on the Repl being always on. If you have hacker plan or you've bought some cycles, then you can enable always on in the drop down menu that appears when you click your Repl name (top left).he code: This is important because when our repl is always running, it can keep track of time and schedule events. 👉 I've set up a simple schedule that prints out a clock emoji every couple of seconds. It works like this: Import schedule librar...

HTTP & Sessions

HTTP & Sessions One of the main protocols (rules that govern how computers communicate) on the web is called HTTP. HTTP is what is known as a stateless protocol. This means that it doesn't 'remember' things. It's a bit like having a conversation with a goldfish. You can ask a question and get a reply, but when you ask a follow up question, the original has already been forgotten, as has who you are and what you were talking about. So if HTTP is stateless, how come my news site remembers to give me the weather for my home town, my preferred South American river based online store tells me when it's time to order more multivitamins, and I'm justifiably proud of my #100days success streak? The answer is......... Sessions Sessions are a way of storing files on your computer that allows a website to keep a record of previous 'conversations' and 'questions' you've asked. By using sessions, we can store this info about the user to access later....

Incoming!

Incoming! Today, we're going to learn how to deal with data from forms in Flask. 👉 To start, I've added yesterday's HTML code for my form in main.py for you already. (You're welcome!) Go take a look! 👉 However, at the moment, the app.route() has no method associated with it, so I need to create a route for this page to receive the data. First, I need a new import: request. Then I create the app.route - I also need to add an extra argument to specify the methods being received. At the moment, that's just 'post', but it does need to be ALL CAPS - POST. Finally I define the process() subroutine that returns request.form 👉 Here's the new code on its own: from Flask import Flask, request app.route('/process', methods=["POST"]) def process(): return request.form 👉 And here it is as part of the whole code: from flask import Flask, request app = Flask(__name__) app.route("/process", methods=["POST"]) def process(): ...

PYTHON SYNTAX

Search This Blog