Homepage: https://lqdoj.edu.vn

Based on DMOJ.

Supported Programming Languages:

• Assembly (x64)
• AWK
• C
• C++03 / C++11 / C++14 / C++17 / C++20 / C++23
• Java
• Pascal
• Perl
• Python 2 / Python 3
• PyPy 2 / PyPy 3

Features:

• Plagiarism detection via Stanford MOSS
• Contest management with various formats
• User rating and performance tracking
• Real-time chat system
• Multi-language support
• Dark/Light theme
• Organization management

Most of the setup follows the same process as DMOJ installations. You can view the installation guide of DMOJ here: https://docs.dmoj.ca/#/site/installation.

The main difference is instead of git clone https://github.com/DMOJ/site.git, you clone this repository: git clone https://github.com/LQDJudge/online-judge.git.

Step 1: Install required libraries

• $ here means sudo. For example, the first line means run sudo apt update

$ apt update
$ apt install git gcc g++ make python3-dev python3-pip libxml2-dev libxslt1-dev zlib1g-dev gettext curl redis-server pkg-config
$ curl -sL https://deb.nodesource.com/setup_18.x | sudo -E bash -
$ apt install nodejs
$ npm install -g sass postcss-cli postcss autoprefixer

Step 2: Set up database

• The server currently uses MariaDB ≥ 10.5, but you can also use MySQL if there are conflicts
• If after running the commands below your MariaDB version is old (< 10.5), you can Google how to install the latest MariaDB (10.5 or 10.6)
• You can check your MariaDB version by typing sudo mysql (Ctrl + C to quit)

$ apt update
$ apt install mariadb-server libmysqlclient-dev

Step 3: Create database tables

• You can change the table name and password

$ sudo mysql
mariadb> CREATE DATABASE dmoj DEFAULT CHARACTER SET utf8mb4 DEFAULT COLLATE utf8mb4_general_ci;
mariadb> GRANT ALL PRIVILEGES ON dmoj.* TO 'dmoj'@'localhost' IDENTIFIED BY '<password>';
mariadb> exit
$ mariadb-tzinfo-to-sql /usr/share/zoneinfo | sudo mariadb -u root mysql

Step 4: Set up virtual environment and pull code

• If pip3 install mysqlclient fails, try running pip3 install mysqlclient==2.1.1

$ python3 -m venv dmojsite
$ . dmojsite/bin/activate

$ git clone https://github.com/LQDJudge/online-judge.git
$ cd online-judge
$ git submodule init
$ git submodule update
$ pip3 install -r requirements.txt
$ pip3 install mysqlclient
$ pre-commit install

Step 5: Create local_settings.py This is the file for customizing Django settings. Create the file at online-judge/dmoj/local_settings.py

• Sample file: online-judge/dmoj/sample_local_settings.py
• If you changed the database table name or password, update the corresponding information in Databases
• After completion, run python3 manage.py check to verify

Step 6: Compile CSS and translations

• Commands 1 and 2 should be run after each change to CSS or JS files (HTML files don't require this)
• Commands 3 and 4 should be run after each change to translation files
• Note: After running these commands, the folder corresponding to STATIC_ROOT in local_settings.py must be created. If it hasn't been created, you need to create that folder before running the first two commands.

$ ./make_style.sh
$ python3 manage.py collectstatic
$ python3 manage.py compilemessages
$ python3 manage.py compilejsi18n

Step 7: Add data to database

$ python3 manage.py migrate
$ python3 manage.py loaddata navbar
$ python3 manage.py loaddata language_small
$ python3 manage.py loaddata demo

Step 8: Run the site At this point, the basic setup is complete (without judge, websocket, celery). You can access it at localhost:8000

python3 manage.py runserver 0.0.0.0:8000

1. (WSL) You can download the Terminal application from the Windows Store

2. (WSL) Each time you open Ubuntu, you need to run the following command to start MariaDB: sudo service mysql restart (similar for other services like memcached, celery)

3. After installation, you only need to activate the virtual environment and run the runserver command:

   . dmojsite/bin/activate
   python3 manage.py runserver

4. For nginx, after configuring according to the DMOJ guide, you need to add the following location to use the profile image feature. Replace path/to/oj with the path where you cloned the source code:

   location /profile_images/ {
       root /path/to/oj;
   }
   

5. Development workflow:

   1. After changing code, Django will automatically rebuild, you just need to press F5
   2. Some styles are in .scss files. You need to recompile CSS to see changes.

Before running unit tests, create the test database in MariaDB/MySQL:

sudo mariadb

CREATE DATABASE test_dmoj DEFAULT CHARACTER SET utf8mb4 DEFAULT COLLATE utf8mb4_general_ci;
GRANT ALL PRIVILEGES ON test_dmoj.* TO 'dmoj'@'localhost';
FLUSH PRIVILEGES;

# Run all tests
python3 manage.py test judge.tests --keepdb

# Run a specific test
python3 manage.py test judge.tests.TestClass.test_method --keepdb

You can save these aliases for faster development:

• mtrans: to generate translation when you add a string in code
• trans: compile translation (after you've translated to Vietnamese)
• cr: change to OJ folder
• pr: run server
• sm: restart services (mainly for WSL)
• sd: activate virtual env
• css: compile CSS files

alias mtrans='python3 manage.py makemessages -l vi && python3 manage.py makedmojmessages -l vi --no-mark-obsolete'
alias pr='python3 manage.py runserver'
alias sd='source ~/LQDOJ/dmojsite/bin/activate'
alias sm='sudo service mysql restart && sudo service redis-server start && sudo service memcached start'
alias trans='python3 manage.py compilemessages -l vi && python3 manage.py compilejsi18n -l vi'
alias cr='cd ~/LQDOJ/online-judge'
alias css='./make_style.sh && python3 manage.py collectstatic --noinput'

Used for in-memory caching:

$ sudo apt install memcached

Used for live updates (like chat):

• The WebSocket configuration file online-judge/websocket/config.js is already included with default settings.

• Install Node.js dependencies:

$ cd websocket
$ npm install

• Add WebSocket settings to local_settings.py:

# WebSocket daemon settings
EVENT_DAEMON_KEY = 'lqdoj'  # Must match backend_auth_token in config.js
EVENT_DAEMON_URL = 'http://127.0.0.1:15100'
EVENT_DAEMON_PUBLIC_URL = 'http://127.0.0.1:15100'  # Same as EVENT_DAEMON_URL in development

# For production with SSL/domain
# EVENT_DAEMON_PUBLIC_URL = 'wss://your-domain.com'  # nginx proxies to port 15100

• Start (in a separate tab)

$ node websocket/daemon.js

Production Deployment:

For nginx, add this location block:

location /socket.io/ {
    proxy_pass http://127.0.0.1:15100/socket.io/;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_read_timeout 86400;
}

Used for background tasks like batch rejudging, AI processing, moderation, and scheduled maintenance. Run both a worker and beat in production:

celery -A dmoj_celery worker
celery -A dmoj_celery beat

Install in a separate folder outside the site:

$ apt install python3-dev python3-pip build-essential libseccomp-dev
$ git clone https://github.com/LQDJudge/judge-server.git
$ cd judge-server
$ sudo pip3 install -e .

• Create a judge.yml file outside the judge-server folder (sample file: https://github.com/DMOJ/docs/blob/master/sample_files/judge_conf.yml)
• Add judge to site via UI: Admin → Judge → Add Judge → enter id and key (only need to add once) or use command python3 manage.py addjudge <id> <key>
• Run Bridge (connection between judge and site) in a separate tab in the online-judge folder:

$ python3 manage.py runbridged

• Start Judge (in a separate tab):

$ dmoj -c judge.yml localhost

• Note: Each time you want to run judges later, open 1 tab for bridge and n tabs for judges. Each judge needs a different yml file (containing different authentication)

For running judges on multiple servers, you can use JuiceFS to share problem data across machines via a POSIX-compatible distributed filesystem backed by S3/R2. See docs/juicefs-setup.md for the full setup guide.

1. Missing local_settings.py: You need to copy the local_settings.py in order to pass the check.

2. Missing problem folder in local_settings.py: You need to create a folder to contain all problem packages and configure in local_settings.py.

3. Missing static folder in local_settings.py: Similar to problem folder, make sure to configure STATIC_FILES inside local_settings.py.

4. Missing configure file for judges: Each judge must have a separate configure file. To create this file, you can run dmoj-autoconf. Check out all sample files here: https://github.com/DMOJ/docs/blob/master/sample_files.

5. Missing timezone data for SQL: If you're using Ubuntu and following DMOJ's installation guide for the server, and you get the error mentioned in #45, then you can follow this method to fix:

   # You may have to do this if you haven't set root password for MySQL, replace mypass with your password
   # SET PASSWORD FOR 'root'@'localhost' = PASSWORD('mypass');
   # FLUSH PRIVILEGES;
   mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -D mysql -u root -p 
   mysql -u root -p -e "flush tables;" mysql

After finishing all installation steps, every time you want to run a local server, follow these steps:

1. Activate virtual environment:

   source dmojsite/bin/activate

2. Run server:

   python3 manage.py runserver 0.0.0.0:8000

3. Create a bridge (open in a different terminal if using the same machine)

   python3 manage.py runbridged

4. Create a judge (another terminal)

   dmoj 0.0.0.0 -p 9999 -c <path to yml configure file>

   Here we assume you use the default port 9999 for bridge in settings.py. You can create multiple judges, each should be in a separate terminal.

1. Run celery worker (server's queue, may be necessary for some functions)

   celery -A dmoj_celery worker

2. Run live event server (for real-time updates like in production)

   node websocket/daemon.js

3. To use subdomain for each organization: Go to admin page → navigation bar → sites, add domain name (e.g., localhost:8000). Then add USE_SUBDOMAIN = True to local_settings.py.

Most steps are similar to standard Django tutorials. Here are two common operations:

• If you add any new phrases in the code: python3 manage.py makemessages
• Go to locale/vi
• Modify .po file
• python3 manage.py compilemessages
• python3 manage.py compilejsi18n

• Change .css/.scss files in resources folder
• ./make_style.sh && python3 manage.py collectstatic
• Sometimes you need to press Ctrl + F5 to see the new user interface in browser

This section covers deploying LQDOJ to a production server. The setup uses Nginx as a reverse proxy, uWSGI as the application server, Supervisor to manage processes, and Docker for the bridge and judges.

It is assumed you have completed the Installation steps (database, virtualenv, code, migrations, static files) on your production server, and that services like Memcached, Redis, Celery, and WebSocket are configured as described in Optional Components.

Edit local_settings.py for production:

# SECURITY: disable debug mode
DEBUG = False

# Generate a strong secret key:
# python3 -c 'from django.core.management.utils import get_random_secret_key;print(get_random_secret_key())'
SECRET_KEY = '<your generated secret key>'

# Optional: SSL settings (uncomment if using HTTPS)
# DMOJ_SSL = 2
# SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')
# SECURE_SSL_REDIRECT = True
# SESSION_COOKIE_SECURE = True
# CSRF_COOKIE_SECURE = True

# Database - use 127.0.0.1 (not localhost) to force TCP connection.
# This is required for the Docker bridge to connect to the database.
DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.mysql',
        'NAME': 'dmoj',
        'USER': 'dmoj',
        'PASSWORD': '<your password>',
        'HOST': '127.0.0.1',
        'OPTIONS': {
            'charset': 'utf8mb4',
            'sql_mode': 'STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION',
        },
    },
}

# Bridge - bind to 0.0.0.0 so Docker judges can connect
BRIDGED_JUDGE_ADDRESS = [('0.0.0.0', 9999)]
BRIDGED_DJANGO_ADDRESS = [('localhost', 9998)]

Make sure the required services are installed and running:

sudo apt install memcached redis-server
sudo systemctl enable memcached redis-server
sudo systemctl start memcached redis-server

Recommended MariaDB production safeguards for web-only database connections:

# Add these inside the existing [mariadbd] or [mysqld] section in:
# /etc/mysql/mariadb.conf.d/50-server.cnf
innodb_ft_min_token_size = 2
max_statement_time = 8
idle_transaction_timeout = 30
idle_write_transaction_timeout = 15
idle_readonly_transaction_timeout = 30

max_statement_time prevents unexpectedly expensive statements from running too long. The idle transaction timeouts prevent sleeping web connections from holding row locks indefinitely. After editing the config, validate and restart MariaDB:

sudo mariadbd --validate-config
sudo systemctl restart mariadb
sudo mariadb dmoj -e "SHOW GLOBAL VARIABLES WHERE Variable_name IN ('innodb_ft_min_token_size', 'max_statement_time', 'idle_transaction_timeout', 'idle_write_transaction_timeout', 'idle_readonly_transaction_timeout');"

For migrations or maintenance commands that legitimately need longer database work, override the limit for that session instead of changing the global default:

SET SESSION max_statement_time = 0;

Install uWSGI inside the virtualenv:

(dmojsite) $ pip3 install uwsgi

Copy sample_conf/uwsgi.ini to the site root directory and adjust the paths. Test with:

(dmojsite) $ uwsgi --ini uwsgi.ini

Install Supervisor:

sudo apt install supervisor

Copy the sample configs from sample_conf/supervisor/ to /etc/supervisor/conf.d/ and adjust the paths:

• site.conf — Django application server (uWSGI)
• celery.conf — Background task worker
• wsevent.conf — WebSocket event server

Then load and start all services:

sudo supervisorctl update
sudo supervisorctl status

Install Nginx:

sudo apt install nginx

Copy sample_conf/nginx/nginx.conf to /etc/nginx/conf.d/ and adjust the paths. Then test and reload:

sudo nginx -t
sudo systemctl reload nginx

If you get 403 errors on static files, nginx (running as www-data) likely can't traverse your home directory. Fix with:

chmod o+x /home/<user> /path/to/static /path/to/media

sudo apt install certbot python3-certbot-nginx
sudo certbot --nginx -d <your domain>

Certbot will automatically modify the Nginx config to add SSL. If you enable SSL, uncomment the SSL settings in local_settings.py (see Pre-deployment Configuration).

LQDOJ runs the bridge in Docker (instead of Supervisor as in standard DMOJ). The Docker files are in .docker/bridge/.

Build the bridge image (run from the parent of the online-judge directory):

.docker/bridge/build.sh

Start the bridge:

.docker/bridge/run.sh

The bridge uses --network=host so it can connect to the host's database on 127.0.0.1 and be reachable by judges on port 9999.

Verify the bridge is running:

docker logs bridge

LQDOJ uses Docker-based judges built from the DMOJ judge-server. Scripts are in .docker/judge/.

Clone the judge-server repo alongside the online-judge directory (if not already done):

git clone https://github.com/LQDJudge/judge-server.git

Then build the Docker image:

.docker/judge/build_image.sh

By default the script looks for judge-server/ next to online-judge/. Set JUDGE_SERVER_DIR to override.

Tip: The full tierlqdoj image includes all runtimes and takes a long time to build. For a quick start, you can build tier1 instead (Python 2/3, C/C++, Java 8, Pascal):

cd judge-server/.docker && make judge-tier1

Then set JUDGE_IMAGE=vnoj/judge-tier1:latest when running judges.

Register judges in the site database (run from the online-judge directory with virtualenv activated):

.docker/judge/register_judges.sh 1 10 '<authentication key>'

This registers judge1 through judge10 with the given key. You can also add judges via the admin panel: Admin -> Judges -> Add Judge.

Create a config file in your problems directory (e.g., /mnt/problems/__conf__/general.yml). A full sample is at sample_conf/judge.yml. The judge name is passed via the command line, so the config only needs the key and paths:

key: '<authentication key>'
problem_storage_globs:
  - /problems/**/
# All configuration for language executors.
# If you're unsure of what values a language needs, consult the source of the executor:
# <https://github.com/DMOJ/judge/tree/master/dmoj/executors>
runtime:
  g++: /usr/bin/g++
  gcc: /usr/bin/gcc
  fpc: /usr/bin/fpc
  java: /usr/lib/jvm/java-25-openjdk-amd64/bin/java
  javac: /usr/lib/jvm/java-25-openjdk-amd64/bin/javac
  python3: /usr/bin/python3
  pypy3: /opt/pypy3/bin/pypy3
  # ... add more runtimes as needed

Note: the problem_storage_globs uses /problems/ because that's the mount point inside the Docker container.

Set PROBLEMS_DIR to your problems directory before running judges:

export PROBLEMS_DIR=/path/to/problems

Start a single judge:

.docker/judge/start_judge.sh judge1

Start multiple judges at once:

.docker/judge/start_judges.sh 1 5

This starts judge1 through judge5. Each judge runs in its own Docker container with --network=host.

Verify judges are connected in Admin -> Judges — they should appear as online.

Make sure port 9999 is open on the site server's firewall. For sharing problem data across multiple servers, see Distributed Judges (JuiceFS).

By default, media files (user uploads, profile images, etc.) are stored on the local filesystem. To use Amazon S3 or S3-compatible storage (e.g., Cloudflare R2) instead:

pip install django-storages[boto3]

Then uncomment and configure the S3 section in local_settings.py (see sample_local_settings.py for all options):

AWS_ACCESS_KEY_ID = 'your-access-key'
AWS_SECRET_ACCESS_KEY = 'your-secret-key'
AWS_STORAGE_BUCKET_NAME = 'your-bucket-name'
AWS_S3_REGION_NAME = 'ap-southeast-1'
AWS_S3_CUSTOM_DOMAIN = 'cdn.example.com'  # Optional: CloudFront or custom domain
DEFAULT_FILE_STORAGE = 'storages.backends.s3boto3.S3Boto3Storage'

No code changes are needed — the codebase uses Django's default_storage abstraction, so all file operations automatically use S3 when configured.

LQDOJ includes a problem recommendation system using collaborative filtering and neural Two Tower models with MariaDB vector search. Requires MariaDB 11.7+.

See judge/ml/README.md for the full setup guide.

Application-level periodic jobs are scheduled in CELERY_BEAT_SCHEDULE in dmoj/settings.py and require celery -A dmoj_celery beat plus at least one Celery worker. This includes moderation, notification cleanup, session cleanup, inactive-account cleanup, score recomputation, contribution recomputation, organization-private flag sync, and auto-review reapers.

Use cron only for server/infrastructure scripts that should stay outside the Django worker process, such as backups, bridge container restarts, or external ML pipelines. Example production crontab entries:

0 2 * * * /home/ubuntu/backup/backup.sh >> /home/ubuntu/backup/backup.log 2>&1
0 3 * * * /home/ubuntu/cronjobs/ml_gen_data.sh
30 2 * * * /home/ubuntu/bridge/run.sh >> /home/ubuntu/bridge/cron.log 2>&1

$ apt update
$ apt install git gcc g++ make python3-dev python3-pip libxml2-dev libxslt1-dev zlib1g-dev gettext curl redis-server pkg-config
$ curl -sL https://deb.nodesource.com/setup_18.x | sudo -E bash -
$ apt install nodejs
$ npm install -g sass postcss-cli postcss autoprefixer

$ apt update
$ apt install mariadb-server libmysqlclient-dev

$ sudo mysql
mariadb> CREATE DATABASE dmoj DEFAULT CHARACTER SET utf8mb4 DEFAULT COLLATE utf8mb4_general_ci;
mariadb> GRANT ALL PRIVILEGES ON dmoj.* TO 'dmoj'@'localhost' IDENTIFIED BY '<password>';
mariadb> exit
$ mariadb-tzinfo-to-sql /usr/share/zoneinfo | sudo mariadb -u root mysql

$ python3 -m venv dmojsite
$ . dmojsite/bin/activate

$ git clone https://github.com/LQDJudge/online-judge.git
$ cd online-judge
$ git submodule init
$ git submodule update
$ pip3 install -r requirements.txt
$ pip3 install mysqlclient
$ pre-commit install

$ ./make_style.sh
$ python3 manage.py collectstatic
$ python3 manage.py compilemessages
$ python3 manage.py compilejsi18n

$ python3 manage.py migrate
$ python3 manage.py loaddata navbar
$ python3 manage.py loaddata language_small
$ python3 manage.py loaddata demo

python3 manage.py runserver 0.0.0.0:8000

sudo mariadb

CREATE DATABASE test_dmoj DEFAULT CHARACTER SET utf8mb4 DEFAULT COLLATE utf8mb4_general_ci;
GRANT ALL PRIVILEGES ON test_dmoj.* TO 'dmoj'@'localhost';
FLUSH PRIVILEGES;

# Chạy tất cả test
python3 manage.py test judge.tests --keepdb

# Chạy một test cụ thể
python3 manage.py test judge.tests.TestClass.test_method --keepdb

alias mtrans='python3 manage.py makemessages -l vi && python3 manage.py makedmojmessages -l vi --no-mark-obsolete'
alias pr='python3 manage.py runserver'
alias sd='source ~/LQDOJ/dmojsite/bin/activate'
alias sm='sudo service mysql restart && sudo service redis-server start && sudo service memcached start'
alias trans='python3 manage.py compilemessages -l vi && python3 manage.py compilejsi18n -l vi'
alias cr='cd ~/LQDOJ/online-judge'
alias css='./make_style.sh && python3 manage.py collectstatic --noinput'

$ sudo apt install memcached

$ cd websocket
$ npm install

# WebSocket daemon settings
EVENT_DAEMON_KEY = 'lqdoj'  # Phải giống backend_auth_token trong config.js
EVENT_DAEMON_URL = 'http://127.0.0.1:15100'
EVENT_DAEMON_PUBLIC_URL = 'http://127.0.0.1:15100'  # Giống EVENT_DAEMON_URL trong development

# Cho production với SSL/domain
# EVENT_DAEMON_PUBLIC_URL = 'wss://your-domain.com'  # nginx proxy đến port 15100

$ node websocket/daemon.js

location /socket.io/ {
    proxy_pass http://127.0.0.1:15100/socket.io/;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_read_timeout 86400;
}

celery -A dmoj_celery worker
celery -A dmoj_celery beat

$ apt install python3-dev python3-pip build-essential libseccomp-dev
$ git clone https://github.com/LQDJudge/judge-server.git
$ cd judge-server
$ sudo pip3 install -e .

$ python3 manage.py runbridged

$ dmoj -c judge.yml localhost

# BẢO MẬT: tắt chế độ debug
DEBUG = False

# Tạo secret key mạnh:
# python3 -c 'from django.core.management.utils import get_random_secret_key;print(get_random_secret_key())'
SECRET_KEY = '<secret key của bạn>'

# Tùy chọn: cài đặt SSL (bỏ comment nếu dùng HTTPS)
# DMOJ_SSL = 2
# SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')
# SECURE_SSL_REDIRECT = True
# SESSION_COOKIE_SECURE = True
# CSRF_COOKIE_SECURE = True

# Database - dùng 127.0.0.1 (không dùng localhost) để buộc kết nối TCP.
# Cần thiết để Docker bridge kết nối được đến database.
DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.mysql',
        'NAME': 'dmoj',
        'USER': 'dmoj',
        'PASSWORD': '<mật khẩu>',
        'HOST': '127.0.0.1',
        'OPTIONS': {
            'charset': 'utf8mb4',
            'sql_mode': 'STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION',
        },
    },
}

# Bridge - bind 0.0.0.0 để Docker judge có thể kết nối
BRIDGED_JUDGE_ADDRESS = [('0.0.0.0', 9999)]
BRIDGED_DJANGO_ADDRESS = [('localhost', 9998)]

sudo apt install memcached redis-server
sudo systemctl enable memcached redis-server
sudo systemctl start memcached redis-server

# Thêm các dòng này vào section [mariadbd] hoặc [mysqld] có sẵn trong:
# /etc/mysql/mariadb.conf.d/50-server.cnf
innodb_ft_min_token_size = 2
max_statement_time = 8
idle_transaction_timeout = 30
idle_write_transaction_timeout = 15
idle_readonly_transaction_timeout = 30

sudo mariadbd --validate-config
sudo systemctl restart mariadb
sudo mariadb dmoj -e "SHOW GLOBAL VARIABLES WHERE Variable_name IN ('innodb_ft_min_token_size', 'max_statement_time', 'idle_transaction_timeout', 'idle_write_transaction_timeout', 'idle_readonly_transaction_timeout');"

SET SESSION max_statement_time = 0;

(dmojsite) $ pip3 install uwsgi

(dmojsite) $ uwsgi --ini uwsgi.ini

sudo apt install supervisor

sudo supervisorctl update
sudo supervisorctl status

sudo apt install nginx

sudo nginx -t
sudo systemctl reload nginx

chmod o+x /home/<user> /path/to/static /path/to/media

sudo apt install certbot python3-certbot-nginx
sudo certbot --nginx -d <domain của bạn>

.docker/bridge/build.sh

.docker/bridge/run.sh

docker logs bridge

git clone https://github.com/LQDJudge/judge-server.git

.docker/judge/build_image.sh

.docker/judge/register_judges.sh 1 10 '<authentication key>'

key: '<authentication key>'
problem_storage_globs:
  - /problems/**/
runtime:
  g++: /usr/bin/g++
  gcc: /usr/bin/gcc
  python3: /usr/bin/python3
  # ... thêm runtime khác theo nhu cầu

export PROBLEMS_DIR=/path/to/problems

.docker/judge/start_judge.sh judge1

.docker/judge/start_judges.sh 1 5

pip install django-storages[boto3]

AWS_ACCESS_KEY_ID = 'your-access-key'
AWS_SECRET_ACCESS_KEY = 'your-secret-key'
AWS_STORAGE_BUCKET_NAME = 'your-bucket-name'
AWS_S3_REGION_NAME = 'ap-southeast-1'
AWS_S3_CUSTOM_DOMAIN = 'cdn.example.com'
DEFAULT_FILE_STORAGE = 'storages.backends.s3boto3.S3Boto3Storage'

0 2 * * * /home/ubuntu/backup/backup.sh >> /home/ubuntu/backup/backup.log 2>&1
0 3 * * * /home/ubuntu/cronjobs/ml_gen_data.sh
30 2 * * * /home/ubuntu/bridge/run.sh >> /home/ubuntu/bridge/cron.log 2>&1