Document how to run BugSigDb locally

[jwokaty]

Below are instructions from Wikiworks about how to run BugSigDb locally. I'm putting them here to document, share, and work out problems, so that later we can update either the README or add a document to the repository with instructions (or script). We can use the issue to discuss how it works.

Running BugSigDB stack locally

Get code

Clone the repo:

git clone https://github.com/waldronlab/BugSigDB

Or update existing repo:

git checkout master
git pull

Modules

Make sure that the necessary modules have been installed. Run from the wiki stack root:

cd to/mediawiki/docker/compose
git submodule update --init

Database

By default, the local wiki will be created empty. Get a copy of the database from the BugSigDB server and put it in the __initdb directory inside the stack.

Secrets

Create secrets and add passwords:

cd secrets
./_create_empty_secret_files.sh

Volumes

Make sure that necessary docker volumes are created:

docker compose up -d --no-start

Networking (with Traefik)

ACCESS TO https://github.com/WikiTeq/docker-mediawiki-traefik IS REQUIRED OTHERWISE FOLLOW NETWORKING (WITHOUT TRAEFIK) BELOW

The BugSigDB MediaWiki stack is designed to work with Traefik.

Step 1. Create a local DNS record

Linux offers a file /etc/hosts to configure local DNS records (other OSes should have equivalents). Associate localtest.me with the local IP. Here is my file content:

➜  ~ cat /etc/hosts

# Standard host addresses
127.0.0.1  localhost localtest.me

Step 2. Make sure the Traefik is up and running

Clone WikiTeq traefik docker-compose repo.

There is .env.localtest.me file with predefined settings for local development. Make it work by creating a symlink

ls -s .env.localtest.me .env

Or rename it to .env.

Run Traefik:

cd to/traefik/docker/compose
docker compose up -d

Step 3. Run wiki stack

There is .env.localtest.me file with predefined settings for local development. Make it work by creating a symlink

cd to/mediawiki/docker/compose
ls -s .env.localtest.me .env

Run the stack:

docker compose up -d

Networking (without Traefik)

It is possible to make the stack run without Traefik.

Step 1. Create a local DNS record

It can be skipped.

Step2. Adjust environment

In the .env.localtest.me set MW_SITE_SERVER to http://localhost:8081 and make it work by symlinking or copying it to .env (port can be whatever allowed port)

Step 3. Adjust compose file

In the compose.yml add the ports section with the port from Step 2 to the varnish service:

    varnish:
        image: pastakhov/varnish:7.0
        restart: unless-stopped
        networks:
            - default
            - traefik-public
        depends_on:
            - web
        ports:
            - "${PORT:-127.0.0.1:8081}:80"
        tmpfs:
            - /var/lib/varnish:exec

Comment out all network sections in all services and at the bottom (before volumes definition). Like this:

        restart: unless-stopped
#        networks:
#

            - default
#            - traefik-public
        depends_on:

Save changes and run the stack:

docker compose up -d

Navigate to http://localhost:8081 to see the wiki.

Update entity collation

If you see a banner about pending SemanticMediaWiki tasks, run from the wiki stack root:

docker compose exec web bash -cl 'php extensions/SemanticMediaWiki/maintenance/updateEntityCollation.php'

[jwokaty]

@RonaldRonnie These are the instructions that were shared with me, which does bring up all containers but didn't work. I tried without Traefik.

[RonaldRonnie]

Okay @jwokaty . Thank you for sharing. Let me work with these and see

[jwokaty]

To clarify what I experienced, I tried to run a local bugsigdb without Traefik and without backup files, but when I visited localhost:8081, I got a service unavailable message. I am clarifying with wikiworks what they are referring to in the modules sections.

[jwokaty]

Here's their reply with what commands they used to start a local bugsigdb without Traefik and a database backup. (I haven't tried it yet.)

mkdir -p docker
cd docker
git clone https://github.com/waldronlab/BugSigDB.git bugsigdb.org
cd bugsigdb.org
git submodule update --init
cp .env.localtest.me .env
nano .env

Make sure that your .env has MW_SITE_SERVER=http://localhost:8081

nano compose.yml

Make sure your compose.yml has ports defined in the varnish section:

    varnish:
        image: pastakhov/varnish:7.0
        restart: unless-stopped
        networks:
            - default
            - traefik-public
        depends_on:
            - web
        ports:
            - "${PORT:-127.0.0.1:8081}:80"
        tmpfs:
            - /var/lib/varnish:exec

Continue with:

cp ~/your.database.backup.sql ./__initdb/
cd secrets
./_create_empty_secret_files.sh
echo anypassword > db_root_password.txt
cd ..
docker compose up -d --no-start
docker compose up -d

Monitor web container by running:

docker compose logs -f web

Due to the size of the database, the first run can take some time (over 1 hour).

When the log reaches the following, the wiki should be available at http://localhost:8081/

web-1  | Run Jobs
web-1  | Starting job runner (in 10 seconds)...
web-1  | Run transcoder
web-1  | Starting transcoder (in 180 seconds)...
web-1  | Sitemap generator is disabled
web-1  | 
web-1  | 
web-1  | >>>>> run-maintenance-script.sh <<<<<
web-1  | 
web-1  | 
web-1  | Job runner started.
web-1  | Transcoder started.

If it hangs (in our case it did), you can try to create database “manually”:

docker compose down
docker compose up -d db
docker compose exec web bash
mysql -p
show databases;
create database mediawiki;
use mediawiki;
source /docker-entrypoint-initdb.d/your.database.backup.sql;
exit
exit
docker compose up -d

If you stuck with the SemanticMediaWiki maintenance screen, you need to run maintenance scripts:

docker compose exec web bash
php extensions/SemanticMediaWiki/maintenance/updateEntityCollation.php
php maintenance/update.php

[RonaldRonnie]

Thank you so much Been trying the other method but nothing is returned to the port

…

On Wed, 19 Mar 2025 at 6:31 PM, jwokaty ***@***.***> wrote: Here's their reply with what commands they used to start a local bugsigdb without Traefik and a database backup. (I haven't tried it yet.) mkdir -p docker cd docker git clone https://github.com/waldronlab/BugSigDB.git bugsigdb.org cd bugsigdb.org git submodule update --init cp .env.localtest.me .env nano .env Make sure that your .env has MW_SITE_SERVER=http://localhost:8081 nano compose.yml Make sure your compose.yml has ports defined in the varnish section: varnish: image: pastakhov/varnish:7.0 restart: unless-stopped networks: - default - traefik-public depends_on: - web ports: - "${PORT:-127.0.0.1:8081}:80" tmpfs: - /var/lib/varnish:exec Continue with: cp ~/your.database.backup.sql ./__initdb/ cd secrets ./_create_empty_secret_files.sh echo anypassword > db_root_password.txt cd .. docker compose up -d --no-start docker compose up -d Monitor web container by running: docker compose logs -f web Due to the size of the database, the first run can take some time (over 1 hour). When the log reaches the following, the wiki should be available at http://localhost:8081/ web-1 | Run Jobs web-1 | Starting job runner (in 10 seconds)... web-1 | Run transcoder web-1 | Starting transcoder (in 180 seconds)... web-1 | Sitemap generator is disabled web-1 | web-1 | web-1 | >>>>> run-maintenance-script.sh <<<<< web-1 | web-1 | web-1 | Job runner started. web-1 | Transcoder started. If it hangs (in our case it did), you can try to create database “manually”: docker compose down docker compose up -d db docker compose exec web bash mysql -p show databases; create database mediawiki; use mediawiki; source /docker-entrypoint-initdb.d/your.database.backup.sql; exit exit docker compose up -d If you stuck with the SemanticMediaWiki maintenance screen, you need to run maintenance scripts: docker compose exec web bash php extensions/SemanticMediaWiki/maintenance/updateEntityCollation.php php maintenance/update.php — Reply to this email directly, view it on GitHub <#261 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBVREPYHIJPUDHQT2CARH532VGEWNAVCNFSM6AAAAABYY6RFT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZXGA4DENJUGU> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: jwokaty]*jwokaty* left a comment (waldronlab/BugSigDB#261) <#261 (comment)> Here's their reply with what commands they used to start a local bugsigdb without Traefik and a database backup. (I haven't tried it yet.) mkdir -p docker cd docker git clone https://github.com/waldronlab/BugSigDB.git bugsigdb.org cd bugsigdb.org git submodule update --init cp .env.localtest.me .env nano .env Make sure that your .env has MW_SITE_SERVER=http://localhost:8081 nano compose.yml Make sure your compose.yml has ports defined in the varnish section: varnish: image: pastakhov/varnish:7.0 restart: unless-stopped networks: - default - traefik-public depends_on: - web ports: - "${PORT:-127.0.0.1:8081}:80" tmpfs: - /var/lib/varnish:exec Continue with: cp ~/your.database.backup.sql ./__initdb/ cd secrets ./_create_empty_secret_files.sh echo anypassword > db_root_password.txt cd .. docker compose up -d --no-start docker compose up -d Monitor web container by running: docker compose logs -f web Due to the size of the database, the first run can take some time (over 1 hour). When the log reaches the following, the wiki should be available at http://localhost:8081/ web-1 | Run Jobs web-1 | Starting job runner (in 10 seconds)... web-1 | Run transcoder web-1 | Starting transcoder (in 180 seconds)... web-1 | Sitemap generator is disabled web-1 | web-1 | web-1 | >>>>> run-maintenance-script.sh <<<<< web-1 | web-1 | web-1 | Job runner started. web-1 | Transcoder started. If it hangs (in our case it did), you can try to create database “manually”: docker compose down docker compose up -d db docker compose exec web bash mysql -p show databases; create database mediawiki; use mediawiki; source /docker-entrypoint-initdb.d/your.database.backup.sql; exit exit docker compose up -d If you stuck with the SemanticMediaWiki maintenance screen, you need to run maintenance scripts: docker compose exec web bash php extensions/SemanticMediaWiki/maintenance/updateEntityCollation.php php maintenance/update.php — Reply to this email directly, view it on GitHub <#261 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBVREPYHIJPUDHQT2CARH532VGEWNAVCNFSM6AAAAABYY6RFT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZXGA4DENJUGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[jwokaty]

@RonaldRonnie I'm still having trouble with it. I think the database isn't being set up correctly and mediawiki isn't finding the LocalSettings.php. This is what I am setting to wikiworks. It might be helpful if we compare our results.

I ran the following

mkdir -p docker
cd docker
git clone https://github.com/waldronlab/BugSigDB.git bugsigdb.org
cd bugsigdb.org
git submodule update --init
cp .env.localtest.me .env
nano .env

# Make sure that your .env has MW_SITE_SERVER=http://localhost:8081

nano compose.yml

# Make sure your compose.yml has ports defined in the varnish section:

    varnish:
        image: pastakhov/varnish:7.0
        restart: unless-stopped
        #networks:
        #    - default
        #    - traefik-public
        depends_on:
            - web
        ports:
            - "${PORT:-127.0.0.1:8081}:80"
        tmpfs:
            - /var/lib/varnish:exec

# Comment out all network sections, including the one at the bottom.

# Continue with:

# We don't have a backup to copy over
cd secrets
./_create_empty_secret_files.sh
echo anypassword > db_root_password.txt
cd ..
docker compose up -d --no-start
docker compose up -d

When I go to http://localhost:8081/, I see

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

With docker compose logs web, I see

web-1  | Starting cache_purge.sh ..                                                                                                                  
web-1  | Starting run_apache.sh ..                                                                                                                   
web-1  | ==== STARTING 20250323_050140 ====                                                                                                          
web-1  | See Bash XTrace in the /var/log/mediawiki/_bootstrap_20250323_050140.log file                                                               
web-1  |                                                                                                                                             
web-1  | * Defined variable MW_ADMIN_PASS with value from /run/secrets/mw_admin_pass                                                                 
web-1  | * Defined variable MW_DB_INSTALLDB_PASS with value from /run/secrets/db_root_password                                                       
web-1  | * Defined variable MW_DB_PASS with value from /run/secrets/db_root_password   
web-1  | * Defined variable MW_DB_PASS with value from /run/secrets/db_root_password
web-1  | Starting cache purge (in 60 seconds)...
web-1  | * Defined variable MW_NCBI_TAXONOMY_API_KEY with value from /run/secrets/mw_ncbi_taxonomy_api_key
web-1  | * Defined variable MW_RECAPTCHA_SECRET_KEY with value from /run/secrets/mw_recaptcha_secret_key
web-1  | * Defined variable MW_RECAPTCHA_SITE_KEY with value from /run/secrets/mw_recaptcha_site_key
web-1  | Syncing files...
web-1  | 
web-1  | Check wiki settings for errors... 1.39.10 OK
web-1  | 
web-1  | MW_MAP_DOMAIN_TO_DOCKER_GATEWAY is not true
web-1  | Checking permissions of Apache log dir /var/log/apache2...
web-1  | Checking permissions of Mediawiki log dir /var/log/mediawiki...
web-1  | Checking permissions of Mediawiki volume dir /mediawiki except /mediawiki/images...
web-1  | 
web-1  | 
web-1  | ==================================================================================
web-1  | 
web-1  | 
web-1  | 
web-1  | 
web-1  | ===== update-images-permissions.sh =====
web-1  | 
web-1  | 
web-1  | Checking permissions of images in Mediawiki volume dir /mediawiki/images...
web-1  | AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.20.0.6. Set the 'ServerName' directive globally to suppress this message
web-1  | 
web-1  | 
web-1  | ===== run-maintenance-script.sh =====
web-1  | 
web-1  | 
web-1  | There is no LocalSettings.php file
web-1  | Defined database server: db
web-1  | Waiting for database to start
web-1  | wait-for-it.sh: waiting 86400 seconds for db:3306
web-1  | wait-for-it.sh: db:3306 is available after 0 seconds
web-1  | Successfully connected to the database.
web-1  | Variable MW_ADMIN_PASS must be defined
web-1  | Cache purger started
web-1  | The file /var/www/mediawiki/w/LocalSettings.php must exist and be readable.
web-1  | Use --conf to specify it.

It doesn’t appear to find the LocalSettings.php file in _settings. When I try to manually set it, I get the following:

root@15ed600f7274:/var/www/mediawiki/w# php maintenance/update.php _settings/LocalSettings.php
The file /var/www/mediawiki/w/LocalSettings.php must exist and be readable.
Use --conf to specify it.
root@15ed600f7274:/var/www/mediawiki/w# php maintenance/update.php --conf _settings/LocalSettings.php
PHP Fatal error:  Uncaught ExtensionDependencyError: VariablesLua requires Scribunto to be installed.
VariablesLua requires Variables to be installed.
SemanticScribunto requires Scribunto to be installed.
 in /var/www/mediawiki/w/includes/registration/ExtensionRegistry.php:432
Stack trace:
#0 /var/www/mediawiki/w/includes/registration/ExtensionRegistry.php(276): ExtensionRegistry->readFromQueue()
#1 /var/www/mediawiki/w/includes/Setup.php(278): ExtensionRegistry->loadFromQueue()
#2 /var/www/mediawiki/w/maintenance/doMaintenance.php(83): require_once('...')
#3 /var/www/mediawiki/w/maintenance/update.php(319): require_once('...')
#4 {main}
  thrown in /var/www/mediawiki/w/includes/registration/ExtensionRegistry.php on line 432

The mediawiki database was created, but it’s empty.

[jwokaty]

@RonaldRonnie I was finally able to stand up a local copy.

Before I could do that, I had to stop all containers and remove all volumes previous created with docker volume rm. You can see what volumes are available with docker volume ls.

Then you do the following from above:

mkdir -p docker
cd docker
git clone https://github.com/waldronlab/BugSigDB.git bugsigdb.org
cd bugsigdb.org
git submodule update --init
cp .env.localtest.me .env

Edit .env so that MW_SITE_SERVER=http://localhost:8081.

Edit compose.yml so that ports are defined in the varnish section and comment out all networks sections (I think there are 3):

    varnish:
        image: pastakhov/varnish:7.0
        restart: unless-stopped
        #networks:
        #    - default
        #    - traefik-public
        depends_on:
            - web
        ports:
            - "${PORT:-127.0.0.1:8081}:80"
        tmpfs:
            - /var/lib/varnish:exec

Copy backup if you have it. (We don't so we skip.)

cp ~/your.database.backup.sql ./__initdb/

cd secrets
./_create_empty_secret_files.sh
echo anypassword > db_root_password.txt
echo anyotherpassword > mw_admin_pass.txt
cd ..
docker compose up -d --no-start
docker compose up -d

Troubleshooting

If you're stuck with the SemanticMediaWiki maintenance screen at localhost:8081, you need to run maintenance scripts:

docker compose exec web bash
php extensions/SemanticMediaWiki/maintenance/updateEntityCollation.php
php maintenance/update.php

You can view the logs with

docker compose logs -f web

If you need to start from scratch, you may need to remove docker volumes.

# list volumes
docker volumes ls
# remove a volume named myVolume
docker volume rm myVolume

[RonaldRonnie]

Awesome, thanks for the update! Let me also test this aside

…

On Wed, 26 Mar 2025 at 00:09, jwokaty ***@***.***> wrote: @RonaldRonnie <https://github.com/RonaldRonnie> I was finally able to stand up a local copy. Before I could do that, I had to stop all containers and remove all volumes previous created with docker volume rm. You can see what volumes are available with docker volume ls. Then you do the following from above: mkdir -p docker cd docker git clone https://github.com/waldronlab/BugSigDB.git bugsigdb.org cd bugsigdb.org git submodule update --init cp .env.localtest.me .env Edit .env so that MW_SITE_SERVER=http://localhost:8081. Edit compose.yml so that ports are defined in the varnish section and comment out all networks sections (I think there are 3): varnish: image: pastakhov/varnish:7.0 restart: unless-stopped #networks: # - default # - traefik-public depends_on: - web ports: - "${PORT:-127.0.0.1:8081}:80" tmpfs: - /var/lib/varnish:exec Copy backup if you have it. (We don't so we skip.) cp ~/your.database.backup.sql ./__initdb/ cd secrets ./_create_empty_secret_files.sh echo anypassword > db_root_password.txt echo anyotherpassword > mw_admin_pass.txt cd .. docker compose up -d --no-start docker compose up -d Troubleshooting If you're stuck with the SemanticMediaWiki maintenance screen at localhost:8081, you need to run maintenance scripts: docker compose exec web bash php extensions/SemanticMediaWiki/maintenance/updateEntityCollation.php php maintenance/update.php You can view the logs with docker compose logs -f web — Reply to this email directly, view it on GitHub <#261 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBVREPZBHQOH5ZUF7FH7OO32WHAY5AVCNFSM6AAAAABYY6RFT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONJSGU2TIMRWGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: jwokaty]*jwokaty* left a comment (waldronlab/BugSigDB#261) <#261 (comment)> @RonaldRonnie <https://github.com/RonaldRonnie> I was finally able to stand up a local copy. Before I could do that, I had to stop all containers and remove all volumes previous created with docker volume rm. You can see what volumes are available with docker volume ls. Then you do the following from above: mkdir -p docker cd docker git clone https://github.com/waldronlab/BugSigDB.git bugsigdb.org cd bugsigdb.org git submodule update --init cp .env.localtest.me .env Edit .env so that MW_SITE_SERVER=http://localhost:8081. Edit compose.yml so that ports are defined in the varnish section and comment out all networks sections (I think there are 3): varnish: image: pastakhov/varnish:7.0 restart: unless-stopped #networks: # - default # - traefik-public depends_on: - web ports: - "${PORT:-127.0.0.1:8081}:80" tmpfs: - /var/lib/varnish:exec Copy backup if you have it. (We don't so we skip.) cp ~/your.database.backup.sql ./__initdb/ cd secrets ./_create_empty_secret_files.sh echo anypassword > db_root_password.txt echo anyotherpassword > mw_admin_pass.txt cd .. docker compose up -d --no-start docker compose up -d Troubleshooting If you're stuck with the SemanticMediaWiki maintenance screen at localhost:8081, you need to run maintenance scripts: docker compose exec web bash php extensions/SemanticMediaWiki/maintenance/updateEntityCollation.php php maintenance/update.php You can view the logs with docker compose logs -f web — Reply to this email directly, view it on GitHub <#261 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBVREPZBHQOH5ZUF7FH7OO32WHAY5AVCNFSM6AAAAABYY6RFT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONJSGU2TIMRWGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[RonaldRonnie]

Hi @jwokaty , been trying another method also. Combining the one above and the one that i have been using a few days ago, Both lead me to this page in the screenshot.

Could you be having any Idea about this please ? I have tried to check if SemanticWiki is enable in LocalSettings.php and it's enabled. I am currently trying out some troubleshoting to fix it but you can help. Iam not sure If you landed on this page during your local Setup.

[RonaldRonnie]

Hi @jwokaty . I was able to set up the local instance.

[jwokaty]

@RonaldRonnie I haven't heard back from wikiworks about the backups, but they have started daily so they might be good. I've granted you permission through your gmail account to view the bugsigdb bucket. I think you may need to finish some authentication or configuration step from your console before you can access it. Reach out if you have trouble.

List bucket contents

gcloud storage ls gs://backups.bugsigdb.org/
gs://backups.bugsigdb.org/full.images.database.tar
gs://backups.bugsigdb.org/database20250414-153802.sql.gz/
gs://backups.bugsigdb.org/database20250414-154050.sql.gz/
gs://backups.bugsigdb.org/database20250419-010135.sql.gz/
gs://backups.bugsigdb.org/database20250420-010050.sql.gz/
gs://backups.bugsigdb.org/database20250421-010123.sql.gz/
gs://backups.bugsigdb.org/database20250422-010146.sql.gz/
gs://backups.bugsigdb.org/database20250423-010105.sql.gz/
gs://backups.bugsigdb.org/database20250424-010120.sql.gz/
gs://backups.bugsigdb.org/images/

Copy a backup of the database

gcloud storage cp gs://backups.bugsigdb.org/database20250424-010120.sql.gz/* .
Copying gs://backups.bugsigdb.org/database20250424-010120.sql.gz/database.sql.gz to file://./database.sql.gz
  Completed files 1/1 | 209.1MiB/209.1MiB | 9.8MiB/s                                                                                                          

Average throughput: 8.2MiB/s

You should ungzip the backup into the __initdb directory before docker compose up -d --no-start. You may need to also remove volumes as we did previously before and also run the maintenance script as described in #261 (comment). You should be able to log in with your user credentials on the live site. It would be great if you could do a little spot checking to see that the site you brought up appears to represent the production site. Afterwords, please create the PR to add documentation for the local copy with and without a backup database along with troubleshooting hints.

[RonaldRonnie]

I have been able to set it up and will be making a PR later on today. Thank you @jwokaty

[jwokaty]

Regarding the Featured Taxon section of the bugsigdb homepage, the image for the taxonomy browser is missing so you see a narrow error message about it. I've asked wikiworks where we should place the images within the directory structure and will follow up with their response.

[RonaldRonnie]

Ok, thanks for the update.

…

On Thu, 24 Apr 2025 at 18:51, jwokaty ***@***.***> wrote: *jwokaty* left a comment (waldronlab/BugSigDB#261) <#261 (comment)> Regarding the Featured Taxon section of the bugsigdb homepage, the image for the taxonomy browser is missing so you see a narrow error message about it. I've asked wikiworks where we should place the images within the directory structure and will follow up with their response. — Reply to this email directly, view it on GitHub <#261 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBVREPZWMPRVDYCCG5QSFYD23EB7LAVCNFSM6AAAAABYY6RFT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRYGEYTKNBVHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>