sudodo

【悲報】賢者、10年のネトゲ生活に飽きてオフ会デビューを決意する

第一部 ツァラトゥストラの序説ッ！

1. 伝説のコテハン、山を降りる

ツァラトゥストラが30歳になったとき、彼は決意した。「俗世間とかいうクソゲー、もうやってらんねぇ」。そう言って彼は故郷の町と、よく釣りをした湖に別れを告げ、山へと引きこもった。リアルからのログアウトである。

ここで彼は、己の精神という名の果てしない沼と、誰にも邪魔されない孤独という名の快適なネット環境を享受し、10年もの間、賢者としてのレベル上げに没頭した。……というのは建前で、要はガチの引きこもりである。

sudodo

import requests
import json
import os

# Set your personal access token
token = os.environ.get('GITHUB_TOKEN')
your_username = 'sudodo'
your_repo = 'your_repo'

# Replace with the appropriate URL for your repository's issues

sudodo

https://github.com/James-Yu/LaTeX-Workshop/wiki/Compile に書いてあったbibのコンパイルを日本語に対応．

0. VSCodeやLatexをインストールしてなければインストール（https://code.visualstudio.com/）
1. Latex-Workshopをインストール(https://marketplace.visualstudio.com/items?itemName=James-Yu.latex-workshop)
2. settings.json(Windows: ファイル > 基本設定 > 設定 or Ctrl + ,， Mac: Code > 基本設定 > 設定 or ⌘ + ,)の{ }内に以下を追加(設定ファイルの変更方法: https://qiita.com/y-w/items/614843b259c04bb91495)

    "latex-workshop.latex.tools": [
        {
            "command": "ptex2pdf",
            "args": [

sudodo

Implementing a logout feature in your web application involves invalidating the user's session or token on both the client and server sides. Since you're using token-based authentication (JWT), the process is mostly client-side because JWTs are stateless; they aren't stored on the server (unless you have a blacklist mechanism in place). Here's how you can implement the logout functionality:

1. Frontend (React):

In your React application, "logging out" a user typically involves removing the token from localStorage (or wherever it's stored) and updating the application's state accordingly.

Here's an example of what the logout button's click handler might look like:

const logoutUser = () => {

sudodo

To ensure that only logged-in users can see the update_user page, you'll need to implement authentication checks. This typically involves sending the token (that you've stored in localStorage after login) with each request to your backend and verifying it there. Here's how you can achieve this:

1. Send Token in Request from React: Modify your API calls to include the authentication token in the headers. With Axios, it might look something like this:

   import axios from "axios";
   
   const token = localStorage.getItem('token');

sudodo

When working with Flask, circular imports (like importing db from app in models.py and User from models in app.py) can sometimes cause problems. To address this, you might want to create a separate file, say database.py, where you define and configure the SQLAlchemy instance, and then import db from this new file wherever it’s needed.

Example with a separate database.py file:

database.py

from flask_sqlalchemy import SQLAlchemy

db = SQLAlchemy()

sudodo

Question

When a developer update model classes after executing db.create_all(), can she reflect those updates into DB schema using convenient tools like db.create_all()?

Answer

When the database model classes (schemas) in a Flask application are updated, reflecting these changes in the actual database schema can be a bit tricky, especially when the database already contains data. db.create_all() is quite limited in this respect, as it does not modify existing tables - it only creates new tables if they do not exist.

For handling changes or migrations of the database schema, Flask has an extension called Flask-Migrate, which is built on top of another package called Alembic. Flask-Migrate/Alembic can generate migration scripts automatically based on the changes detected in the models. It also provides a command-line interface to apply the migrations to the database. Here's a basic flow of how it works:

sudodo

Setting environment variables can be slightly different depending on your production environment and platform (e.g., Linux server, Vercel, AWS, etc.). However, I'll guide you through a general approach and provide some platform-specific examples.

General Approach: Linux Server

If you're deploying your React app on a basic Linux server, you can set environment variables in various ways:

1. Directly in Your Session: When you SSH into your server, you can set an environment variable that lasts for the duration of the session.

export REACT_APP_API_URL="https://yourapiurl.com"

sudodo

import os

# Define the directory and file structure
structure = {
    'myflaskapp': {
        'app': {
            'templates': {},
            'static': {
                'css': {},
                'js': {},

sudodo