localhost:8000project folder / local dev

 
$ cd project_folder (folder you are using for the project)
$ pipenv install requests

 
import requests
response = requests.get('https://httpbin.org/ip')
print('Your IP is {0}'.format(response.json()['origin']))

 
$ pipenv run python main.py

 
$ cd project_folder
$ virtualenv venv

 
$ python -m http.server

3. SUCCESS – URL – http://localhost:8000/

https://developers.google.com/web/tools/chrome-devtools/workspaces

Set up DevTools

1. Press Command+Option+J (Mac) or Control+Shift+J (Windows, Linux, Chrome OS) to open the Console panel of DevTools.

    

   Figure 4. The Console panel

    

2. Click the Sources tab.

3. Click the Filesystem tab.

    

   Figure 5. The Filesystem tab

    

4. Click Add Folder To Workspace.

5. Select ~/Desktop/app.

6. Click Allow to give DevTools permission to read and write to the directory. In the Filesystem tab, there is now a green dot next to index.html, script.js, and styles.css. These green dots mean that DevTools has established a mapping between the network resources of the page, and the files in ~/Desktop/app.

    

   Figure 6. The Filesystem tab now shows a mapping between the local files and the network ones

    

Step 2: Save a CSS change to disk

1. Open ~/Desktop/app/styles.css in a text editor. Notice how the color property of h2 elements is set to fuchsia.

    

   Figure 7. Viewing styles.css in a text editor

    

2. Close the text editor.

3. Back in DevTools, click the Elements tab.

4. Change the value of the color property of the <h2> element to your favorite color. Remember that you need to click the <h2> element in the DOM Tree in order to see the CSS rules applied to it in the Styles pane. The green dot next to styles.css:1 means that any change you make will get mapped to ~/Desktop/app/styles.css.

    

   Figure 8. Setting the color property of the h2 element to green

    

5. Open ~/Desktop/app/styles.css in a text editor again. The color property is now set to your favorite color.

6. Reload the page. The color of the <h2> element is still set to your favorite color. This works because when you made the change, DevTools saved the change to disk. And then, when you reloaded the page, your local server served the modified copy of the file from disk.

Step 3: Save an HTML change to disk

Try changing HTML from the Elements panel

Warning: The workflow that you're about to try doesn't work. You're trying it now so that you don't waste time later trying to figure out why it's not working.

1. Click the Elements tab.

2. Double click the text content of the h2 element, which says Workspaces Demo, and replace it with I ❤️ Cake.

    

   Figure 9. Attempting to change HTML from the DOM Tree of the Elements panel

    

3. Open ~/Desktop/app/index.html in a text editor. The change that you just made isn't there.

4. Reload the page. The page reverts to its original title.

Optional: Why it doesn't work

Note: This section describes why the workflow from Try changing HTML from the Elements panel doesn't work. You can skip this section if you don't care why.

• The tree of nodes that you see on the Elements panel represents the page's DOM.
• To display a page, a browser fetches HTML over the network, parses the HTML, and then converts it into a tree of DOM nodes.
• If the page has any JavaScript, that JavaScript may add, delete, or change DOM nodes. CSS can change the DOM, too, via the property.
• The browser eventually uses the DOM to determine what content it should present to browser users.
• Therefore, the final state of the page that users see may be very different from the HTML that the browser fetched.
• This makes it difficult for DevTools to resolve where a change made in the Elements panel should be saved, because the DOM is affected by HTML, JavaScript, and CSS.

In short, the DOM Tree !== HTML.

Change HTML from the Sources panel

If you want to save a change to the page's HTML, do it via the Sources panel.

1. Click the Sources tab.

2. Click the Page tab.

3. Click (index). The HTML for the page opens.

4. Replace <h2>Workspaces Demo</h2> with <h2>I ❤️ Cake</h2>. See Figure 11.

5. Press Command+S (Mac) or Control+S (Windows, Linux, Chrome OS) to save the change.

6. Reload the page. The <h2> element is still displaying the new text.

    

   Figure 11. Line 12 has been set to I ❤️ Cake

    

7. Open ~/Desktop/app/index.html. The <h2> element contains the new text.

Step 4: Save a JavaScript change to disk

The Sources panel is also the place to make changes to JavaScript. But sometimes you need to access other panels, such as the Elements panel or the Console panel, while making changes to your site. There's a way to have the Sources panel open alongside other panels.

1. Click the Elements tab.

2. Press Command+Shift+P (Mac) or Control+Shift+P (Windows, Linux, Chrome OS). The Command Menu opens.

3. Type QS, then select Show Quick Source. At the bottom of your DevTools window there is now a Quick Source tab. The tab is displaying the contents of index.html, which is the last file you edited in the Sources panel. The Quick Source tab gives you the editor from the Sources panel, so that you can edit files while having other panels open.

    

   Figure 12. Opening the Quick Source tab via the Command Menu

    

4. Press Command+P (Mac) or Control+P (Windows, Linux, Chrome OS) to open the Open File dialog. See Figure 13.

5. Type script, then select app/script.js.

    

   Figure 13. Opening script.js via the Open File dialog

    

6. Notice the Save Changes To Disk With Workspaces link in the demo. It's styled regularly.

7. Add the following code to the bottom of script.js via the Quick Source tab.

   console.log('greetings from script.js');
   document.querySelector('a').style = 'font-style:italic';
   

8. Press Command+S (Mac) or Control+S (Windows, Linux, Chrome OS) to save the change.

9. Reload the page. The link on the page is now italic.

    

   Figure 14. The link on the page is now italic

    

Next steps

Congratulations, you have completed the tutorial. Click the button below to receive your prize.

Use what you have learned in this tutorial to set up Workspaces in your own project. If you run into any issues or are able to get it working after some custom configuration, please start a thread in the mailing list or [ask a que

stion on Stack Overflow to share your knowledge with the rest of the DevTools community.

Chrome DevTools – Debugging Javascript

https://developers.google.com/web/tools/chrome-devtools/javascript

https://developers.google.com/web/tools/chrome-devtools