{"id":1125,"date":"2026-11-19T18:00:00","date_gmt":"2026-11-19T18:00:00","guid":{"rendered":"https:\/\/vpslake.com\/blog\/?p=1125"},"modified":"2026-11-19T18:00:00","modified_gmt":"2026-11-19T18:00:00","slug":"install-drupal-lamp-centos-stream-10","status":"publish","type":"post","link":"https:\/\/vpslake.com\/blog\/2026\/11\/19\/install-drupal-lamp-centos-stream-10\/","title":{"rendered":"How to Install Drupal with LAMP on CentOS Stream 10"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Install Drupal with LAMP on CentOS Stream 10 and finish with a working Drupal 11 site behind Apache, MariaDB, PHP-FPM, and HTTPS in about 20\u201330 minutes. You will prepare the server over SSH, then complete Drupal&#8217;s guided setup in a browser.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Prerequisites<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>A fresh CentOS Stream 10 VPS with at least 2 GB RAM and 10 GB of free disk space. Drupal&#8217;s installer and future updates need more memory than a bare PHP page.<\/li>\n\n\n<li>SSH access as <code>root<\/code>, or a normal user with working <code>sudo<\/code> privileges.<\/li>\n\n\n<li>A domain such as <code>YOUR_DOMAIN<\/code> with an A record pointing to <code>SERVER_IP<\/code>; the domain is needed for a trusted HTTPS certificate.<\/li>\n\n\n<li>A strong database password and a separate strong Drupal administrator password. Replace each uppercase placeholder before running a command or filling in the installer.<\/li>\n\n\n<li>If you need the server, choose a <a href=\"https:\/\/vpslake.com\/buy-vps\">VPSLake Linux VPS<\/a> with root access and CentOS Stream 10.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Drupal 11 requires PHP 8.3 or later, MariaDB 10.6 or later, the PDO database extension, and several common PHP extensions. Check the current <a href=\"https:\/\/www.drupal.org\/docs\/getting-started\/system-requirements\" target=\"_blank\" rel=\"noopener\">Drupal system requirements<\/a> if you plan to add modules with extra dependencies.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Update CentOS and install LAMP packages<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Install the web server, database, PHP-FPM, Drupal&#8217;s required extensions, and SELinux utilities together so the stack uses the CentOS Stream 10 repositories consistently.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dnf update -y\nsudo dnf install -y httpd firewalld mariadb-server mariadb php php-cli php-fpm php-mysqlnd php-gd php-mbstring php-xml php-opcache php-curl php-zip php-intl curl tar policycoreutils-python-utils\nsudo systemctl enable --now firewalld httpd mariadb php-fpm\nsudo php -v<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The PHP version must begin with <code>8.3<\/code> or a newer supported PHP 8 release. CentOS Stream 10 runs PHP through PHP-FPM, which keeps request processing in a managed service instead of depending on the older Apache PHP module.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>PHP 8.3.x (cli) (built: ...)<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Open only the web ports<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Allow SSH and the two web protocols while leaving MariaDB private to the VPS; Drupal and PHP can reach the local database without exposing port 3306 to the internet.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo firewall-cmd --permanent --zone=public --add-service=ssh\nsudo firewall-cmd --permanent --zone=public --add-service=http\nsudo firewall-cmd --permanent --zone=public --add-service=https\nsudo firewall-cmd --reload\nsudo firewall-cmd --zone=public --list-services<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The final command should include <code>ssh<\/code>, <code>http<\/code>, and <code>https<\/code>. If SSH uses a custom port, add that port before reloading firewalld; do not lock yourself out by assuming the default service definition matches your VPS.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Create Drupal&#8217;s MariaDB database<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Drupal needs a dedicated database account so the site does not use MariaDB&#8217;s administrative account.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo mariadb-secure-installation<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Remove anonymous accounts and the test database, disallow remote administrative login, and reload the privilege tables when the hardening script asks. On a fresh MariaDB installation, local root access commonly uses the Unix socket, so <code>sudo mariadb<\/code> is expected to work without a root password.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Create a UTF-8 database and a local-only application user. Replace <code>YOUR_DB_PASSWORD<\/code> with a long, unique password and save it for the web installer.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo mariadb -e \"CREATE DATABASE drupal CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci; CREATE USER 'drupaluser'@'localhost' IDENTIFIED BY 'YOUR_DB_PASSWORD'; GRANT ALL PRIVILEGES ON drupal.* TO 'drupaluser'@'localhost'; FLUSH PRIVILEGES;\"\nsudo mariadb -e \"SELECT VERSION() AS mariadb_version; SHOW DATABASES LIKE 'drupal';\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output includes a MariaDB version and the <code>drupal<\/code> database:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mariadb_version\n10.6.x-MariaDB\nDatabase (drupal)\ndrupal<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Download Drupal and apply SELinux-safe permissions<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The official release archive is sufficient for a single-site deployment and avoids putting Composer&#8217;s vendor directory under a web-accessible parent.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/var\/www\nsudo curl -fL https:\/\/www.drupal.org\/download-latest\/tar.gz -o \/tmp\/drupal.tar.gz\nsudo tar -xzf \/tmp\/drupal.tar.gz -C \/var\/www\nsudo mv \/var\/www\/drupal-* \/var\/www\/drupal\nsudo rm -f \/tmp\/drupal.tar.gz<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Make the application readable by Apache, but give the web process write access only to Drupal&#8217;s public files directory and the settings file during installation. This keeps uploads separate from the PHP code.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo chown -R root:apache \/var\/www\/drupal\nsudo find \/var\/www\/drupal -type d -exec chmod 750 {} +\nsudo find \/var\/www\/drupal -type f -exec chmod 640 {} +\nsudo install -d -o apache -g apache -m 0770 \/var\/www\/drupal\/sites\/default\/files\nsudo cp \/var\/www\/drupal\/sites\/default\/default.settings.php \/var\/www\/drupal\/sites\/default\/settings.php\nsudo chown root:apache \/var\/www\/drupal\/sites\/default\/settings.php\nsudo chmod 660 \/var\/www\/drupal\/sites\/default\/settings.php\nsudo chcon -t httpd_sys_rw_content_t \/var\/www\/drupal\/sites\/default\/settings.php\nsudo semanage fcontext -a -t httpd_sys_rw_content_t '\/var\/www\/drupal\/sites\/default\/files(\/.*)?'\nsudo restorecon -Rv \/var\/www\/drupal\/sites\/default\/files<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The <code>chcon<\/code> line temporarily permits the installer to write <code>settings.php<\/code>; the final step below restores its read-only SELinux label after installation. The persistent <code>semanage<\/code> rule lets Drupal create uploads and generated assets without disabling SELinux.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Configure Apache and PHP-FPM<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Apache must permit Drupal&#8217;s <code>.htaccess<\/code> file, because that file provides clean URLs and several request protections.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Set a practical PHP memory limit and upload size for a new site:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo tee \/etc\/php.d\/90-drupal.ini &gt;\/dev\/null &lt;&lt;'PHP'\nmemory_limit = 256M\nupload_max_filesize = 64M\npost_max_size = 64M\nPHP<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Create a virtual host. Replace <code>YOUR_DOMAIN<\/code> and <code>ADMIN_EMAIL<\/code> with the real hostname and an address for server notices.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo tee \/etc\/httpd\/conf.d\/drupal.conf &gt;\/dev\/null &lt;&lt;'APACHE'\n&lt;VirtualHost *:80&gt;\n    ServerName YOUR_DOMAIN\n    ServerAdmin ADMIN_EMAIL\n    DocumentRoot \/var\/www\/drupal\n\n    &lt;Directory \/var\/www\/drupal&gt;\n        AllowOverride All\n        Options -Indexes +FollowSymLinks -MultiViews\n        Require all granted\n    &lt;\/Directory&gt;\n\n    DirectoryIndex index.php index.html\n    ErrorLog \/var\/log\/httpd\/drupal_error.log\n    CustomLog \/var\/log\/httpd\/drupal_access.log combined\n&lt;\/VirtualHost&gt;\nAPACHE\nsudo apachectl configtest\nsudo systemctl restart php-fpm httpd\nsudo systemctl is-active httpd php-fpm<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The configuration check must say <code>Syntax OK<\/code>, and both services should report <code>active<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Syntax OK\nactive\nactive<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Step 6: Issue an HTTPS certificate<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Run this after DNS resolves <code>YOUR_DOMAIN<\/code> to the VPS and the HTTP virtual host answers from the public internet. Certbot can then complete the challenge and update Apache for HTTPS.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dnf install -y epel-release\nsudo dnf install -y certbot python3-certbot-apache\nsudo certbot --apache --domain YOUR_DOMAIN<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Choose the redirect-to-HTTPS option when Certbot offers it. The certificate is renewed by the installed timer; check it with <code>sudo systemctl list-timers 'certbot*'<\/code>. If you are testing with an IP address only, skip this step temporarily and do not use an HTTP-only site for real administrator credentials.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 7: Run the Drupal browser installer<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The server is ready; the web installer now creates Drupal&#8217;s tables and the first administrator account.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Open <code>https:\/\/YOUR_DOMAIN\/core\/install.php<\/code> in a browser. Select <code>English<\/code>, choose the <code>Standard<\/code> installation profile, and select <code>MySQL, MariaDB, or equivalent<\/code> as the database type.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Enter these database values:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Database name: <code>drupal<\/code><\/li>\n\n\n<li>Database username: <code>drupaluser<\/code><\/li>\n\n\n<li>Database password: <code>YOUR_DB_PASSWORD<\/code><\/li>\n\n\n<li>Database host: <code>localhost<\/code><\/li>\n\n\n<li>Database port: <code>3306<\/code><\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">On the site configuration page, use a descriptive site name, a unique administrator username, a strong password, and an email address you monitor. Do not use <code>admin<\/code> as the username. Drupal will redirect you to the new front page when the installation finishes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verify the Drupal LAMP installation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Run these checks from SSH and load the site over HTTPS from another device. The service check proves the daemons are running, the Apache check validates the vhost, and the database query confirms that the application database exists.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl is-active httpd php-fpm mariadb firewalld\nsudo apachectl configtest\ncurl -fsSI https:\/\/YOUR_DOMAIN\/\nsudo mariadb -e \"SHOW DATABASES LIKE 'drupal';\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected results are four <code>active<\/code> lines, <code>Syntax OK<\/code>, an HTTP <code>200<\/code> or Drupal redirect response, and one row named <code>drupal<\/code>. In Drupal, open <strong>Manage \u2192 Reports \u2192 Status report<\/strong> and resolve any warning about file permissions, trusted hosts, or PHP extensions.<\/p>\n\n\n\n<aside class=\"vl-element vl-cta-banner\" aria-label=\"Launch your Drupal server\">\n\t<div class=\"vl-cta-banner__content\">\n\t\t<p class=\"vl-cta-banner__eyebrow\">CentOS Stream VPS<\/p>\n\t\t<h3 class=\"vl-cta-banner__title\">Launch your Drupal server<\/h3>\n\t\t<p class=\"vl-cta-banner__text\">Get root access for a secure Drupal LAMP deployment on CentOS Stream 10.<\/p>\n\t<\/div>\n\t<a class=\"vl-cta-banner__button\" href=\"\/buy-vps\" aria-label=\"View Linux VPS plans\">View Linux VPS plans<\/a>\n<\/aside>\n\n\n\n<h2 class=\"wp-block-heading\">Troubleshooting<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">The installer says PHP 8.3 is required<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Drupal 11 will not run on an older PHP release. Confirm both the command-line and PHP-FPM packages, then update the operating system and restart PHP-FPM; do not mix a random third-party PHP repository into the base installation.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>php -v\nsudo dnf update -y php\\*\nsudo systemctl restart php-fpm httpd<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\"><code>403 Forbidden<\/code> or a <code>500 Internal Server Error<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The usual causes are a missing <code>AllowOverride All<\/code>, incorrect ownership, or an SELinux label that does not match the new path. Check the Apache error log, validate the vhost, and restore the labels before restarting.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo tail -n 40 \/var\/log\/httpd\/drupal_error.log\nsudo apachectl configtest\nsudo restorecon -Rv \/var\/www\/drupal\nsudo systemctl restart httpd php-fpm<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\"><code>Access denied for user 'drupaluser'@'localhost'<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The password in the installer does not match the account, or the database user was created with a different host value. Reset the password using the local administrative socket, then enter the same value in Drupal&#8217;s database form.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo mariadb -e \"ALTER USER 'drupaluser'@'localhost' IDENTIFIED BY 'YOUR_DB_PASSWORD'; FLUSH PRIVILEGES;\"<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Certbot reports a failed challenge<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The domain&#8217;s DNS record may still point elsewhere, or port 80 may be blocked by firewalld or the VPS provider&#8217;s network firewall. Confirm the public A record, allow HTTP, and try again after the domain resolves to <code>SERVER_IP<\/code>.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo firewall-cmd --zone=public --list-services\ncurl -I http:\/\/YOUR_DOMAIN\/\nsudo certbot --apache --domain YOUR_DOMAIN<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Hardening<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>After the installer finishes, make the settings file read-only and restore its normal SELinux type:<\/li>\n\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code>  sudo chmod 640 \/var\/www\/drupal\/sites\/default\/settings.php\n  sudo restorecon -v \/var\/www\/drupal\/sites\/default\/settings.php\n  sudo chown root:apache \/var\/www\/drupal\/sites\/default\/settings.php<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Configure Drupal trusted hosts in <code>sites\/default\/settings.php<\/code> for <code>YOUR_DOMAIN<\/code> and any deliberate <code>www<\/code> alias; this blocks unexpected Host headers.<\/li>\n\n\n<li>Keep MariaDB bound to localhost and back up both <code>\/var\/www\/drupal<\/code> and the <code>drupal<\/code> database before core or module updates.<\/li>\n\n\n<li>Apply operating-system security updates regularly. For a repeatable SSH baseline, you can use VPSLake&#8217;s <a href=\"https:\/\/vpslake.com\/sshd-hardening-generator\">SSH hardening generator<\/a>.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Can I install Drupal 10 instead of Drupal 11?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Yes, but the current archive may install the latest supported branch. Drupal 10 has lower PHP and MariaDB minimums, while Drupal 11 requires PHP 8.3 and MariaDB 10.6 or newer. Pin a supported release only when your project requires it, and plan upgrades before that branch reaches end of life.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is Composer required for this installation?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. The official release archive includes the Drupal code and runtime dependencies needed for this basic site. Composer is recommended for teams that manage modules and updates as a version-controlled project, so use the Composer workflow when you need that deployment model.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why does Drupal need a writable <code>sites\/default\/files<\/code> directory?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Drupal stores uploaded media, generated stylesheets, and cached assets there. Only that data directory should be writable by Apache; the application code should remain owned by root and read-only to the web process.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I use the VPS IP instead of a domain?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You can use the IP for an initial HTTP connectivity test, but a domain is strongly preferred for production. A domain is required for a normal trusted certificate and makes Drupal&#8217;s trusted-host protection and future email configuration predictable.<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Can I install Drupal 10 instead of Drupal 11?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Yes, but the current archive may install the latest supported branch. Drupal 10 has lower PHP and MariaDB minimums, while Drupal 11 requires PHP 8.3 and MariaDB 10.6 or newer. Pin a supported release only when your project requires it, and plan upgrades before that branch reaches end of life.\"}}, {\"@type\": \"Question\", \"name\": \"Is Composer required for this installation?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. The official release archive includes the Drupal code and runtime dependencies needed for this basic site. Composer is recommended for teams that manage modules and updates as a version-controlled project, so use the Composer workflow when you need that deployment model.\"}}, {\"@type\": \"Question\", \"name\": \"Why does Drupal need a writable `sites\/default\/files` directory?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Drupal stores uploaded media, generated stylesheets, and cached assets there. Only that data directory should be writable by Apache; the application code should remain owned by root and read-only to the web process.\"}}, {\"@type\": \"Question\", \"name\": \"Can I use the VPS IP instead of a domain?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"You can use the IP for an initial HTTP connectivity test, but a domain is strongly preferred for production. A domain is required for a normal trusted certificate and makes Drupal's trusted-host protection and future email configuration predictable.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Install Drupal with LAMP on CentOS Stream 10 using Apache, MariaDB, PHP-FPM, firewalld, SELinux-safe permissions, HTTPS, checks, and clear fixes.","protected":false},"author":1,"featured_media":1126,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_singular_sidebar":"","csco_page_header_type":"","csco_page_load_nextpost":"","footnotes":""},"categories":[5,9],"tags":[71,110,140,73,72],"class_list":["post-1125","post","type-post","status-publish","format-standard","has-post-thumbnail","category-guides","category-vps-hosting","tag-apache","tag-centos-stream-10","tag-drupal","tag-mariadb","tag-php","cs-entry"],"_links":{"self":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1125","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/comments?post=1125"}],"version-history":[{"count":1,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1125\/revisions"}],"predecessor-version":[{"id":4116,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1125\/revisions\/4116"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media\/1126"}],"wp:attachment":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media?parent=1125"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/categories?post=1125"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/tags?post=1125"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}