{"id":1023,"date":"2026-11-07T03:00:00","date_gmt":"2026-11-07T03:00:00","guid":{"rendered":"https:\/\/vpslake.com\/blog\/?p=1023"},"modified":"2026-11-07T03:00:00","modified_gmt":"2026-11-07T03:00:00","slug":"install-bagisto-lamp-rocky-linux-8","status":"publish","type":"post","link":"https:\/\/vpslake.com\/blog\/2026\/11\/07\/install-bagisto-lamp-rocky-linux-8\/","title":{"rendered":"How to Install Bagisto with LAMP on Rocky Linux 8"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Install Bagisto on Rocky Linux 8 with Apache, PHP 8.4, MariaDB 10.11, and Composer, then put the store behind HTTPS. Budget about 25 minutes on a clean VPS, including the interactive store installer and certificate setup.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Prerequisites<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Rocky Linux 8.10, fully updated, with a public IPv4 address.<\/li>\n\n\n<li>A root account or a sudo-enabled user connected over SSH.<\/li>\n\n\n<li>At least 2 GB RAM and 10 GB free disk space for the application, dependencies, database, and uploaded media.<\/li>\n\n\n<li>A domain such as <code>YOUR_DOMAIN<\/code> pointing to the VPS; ports 80 and 443 must reach the server.<\/li>\n\n\n<li>A Linux server from <a href=\"https:\/\/vpslake.com\/buy-vps\">VPSLake<\/a> with enough storage for your catalog and media.<\/li>\n\n\n<li>A strong database password, a separate Bagisto administrator password, and an email address for certificate notices.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This guide installs the current Bagisto 2.5 release line. Bagisto\u2019s <a href=\"https:\/\/devdocs.bagisto.com\/getting-started\/before-you-start\" target=\"_blank\" rel=\"noopener\">system requirements<\/a> call for PHP 8.4, Composer 2, and MariaDB 10.11 or another supported database. Rocky Linux 8\u2019s original PHP stream is older, so the first step enables the Remi PHP 8.4 stream.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Install the LAMP packages<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Rocky\u2019s package manager installs Apache and PHP-FPM, while a MariaDB repository supplies the database version expected by Bagisto.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dnf -y update\nsudo dnf -y install epel-release dnf-plugins-core\nsudo dnf config-manager --set-enabled powertools\nsudo dnf -y install https:\/\/rpms.remirepo.net\/enterprise\/remi-release-8.rpm\nsudo dnf module reset php -y\nsudo dnf module enable php:remi-8.4 -y\nsudo tee \/etc\/yum.repos.d\/MariaDB.repo &gt; \/dev\/null &lt;&lt;'REPO'\n[mariadb]\nname=MariaDB 10.11\nbaseurl=https:\/\/rpm.mariadb.org\/10.11\/rhel\/$releasever\/$basearch\ngpgkey=https:\/\/rpm.mariadb.org\/RPM-GPG-KEY-MariaDB\ngpgcheck=1\nenabled=1\nmodule_hotfixes=1\nREPO\nsudo dnf -y install httpd MariaDB-server MariaDB-client php php-cli php-common php-fpm php-bcmath php-curl php-gd php-intl php-mbstring php-mysqlnd php-opcache php-pdo php-process php-xml php-zip unzip curl policycoreutils-python-utils firewalld\nsudo systemctl enable --now firewalld httpd mariadb php-fpm<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Set PHP limits that allow larger product images and Composer operations without changing the package-managed <code>php.ini<\/code>.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo tee \/etc\/php.d\/99-bagisto.ini &gt; \/dev\/null &lt;&lt;'INI'\nmemory_limit = 512M\nupload_max_filesize = 100M\npost_max_size = 110M\nmax_execution_time = 300\nmax_input_time = 300\nINI\nsudo systemctl restart php-fpm\nphp -v\nmariadb --version\nsudo systemctl is-active httpd mariadb php-fpm<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>PHP 8.4.x (cli) ...\nmariadb  Ver 15.1 Distrib 10.11.x-MariaDB ...\nactive\nactive\nactive<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Configure firewalld before publishing the site<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Allow SSH for administration and the two web services; do not expose MariaDB\u2019s port because the application uses the database locally.<\/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 --list-services<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>ssh dhcpv6-client http https<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Harden MariaDB and create the Bagisto database<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The hardening wizard removes unused database access, and a dedicated account limits Bagisto to its own schema.<\/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\">When prompted, remove anonymous users, disallow remote root login, remove the test database, and reload the privilege tables. Then create the database and grant access for both common local connection forms; this prevents a <code>localhost<\/code> versus <code>127.0.0.1<\/code> mismatch during installation.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo mariadb &lt;&lt;'SQL'\nCREATE DATABASE bagisto CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;\nCREATE USER 'bagisto'@'localhost' IDENTIFIED BY 'YOUR_DB_PASSWORD';\nCREATE USER 'bagisto'@'127.0.0.1' IDENTIFIED BY 'YOUR_DB_PASSWORD';\nGRANT ALL PRIVILEGES ON bagisto.* TO 'bagisto'@'localhost';\nGRANT ALL PRIVILEGES ON bagisto.* TO 'bagisto'@'127.0.0.1';\nFLUSH PRIVILEGES;\nSQL\nmariadb -u bagisto -p -h 127.0.0.1 bagisto -e 'SELECT VERSION();'<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Replace <code>YOUR_DB_PASSWORD<\/code> in the SQL block with a long, unique password. The final command asks for it without placing the value in shell history.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>VERSION()\n10.11.x-MariaDB<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Install Composer with checksum verification<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Composer is Bagisto\u2019s dependency manager, and checking the installer signature before executing it reduces the risk of running a corrupted download. This follows the current <a href=\"https:\/\/getcomposer.org\/download\/\" target=\"_blank\" rel=\"noopener\">Composer installation procedure<\/a>.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/tmp\ncurl -fsSL https:\/\/getcomposer.org\/installer -o composer-setup.php\nEXPECTED_CHECKSUM=\"$(curl -fsSL https:\/\/composer.github.io\/installer.sig)\"\nACTUAL_CHECKSUM=\"$(php -r \"echo hash_file('sha384', 'composer-setup.php');\")\"\ntest \"$EXPECTED_CHECKSUM\" = \"$ACTUAL_CHECKSUM\"\nsudo php composer-setup.php --install-dir=\/usr\/local\/bin --filename=composer --2\nrm -f composer-setup.php\ncomposer --version<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>Composer version 2.x.x 20xx-xx-xx<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Create the application with Composer<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Running the project as a non-login service account keeps the web application files away from root-owned Composer operations.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo useradd --system --home-dir \/var\/www\/bagisto --shell \/sbin\/nologin --user-group bagisto\nsudo install -d -o bagisto -g bagisto -m 0750 \/var\/www\/bagisto\nsudo -u bagisto -H composer create-project --no-dev --prefer-dist --no-interaction bagisto\/bagisto \/var\/www\/bagisto \"2.5.*\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The Composer command creates the <code>.env<\/code> file and application key. The project\u2019s <code>public\/<\/code> directory, rather than <code>\/var\/www\/bagisto<\/code>, will be the only directory Apache exposes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 6: Set permissions and keep SELinux enforcing<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Apache needs read access to the application, while Laravel needs write access only to <code>storage<\/code> and <code>bootstrap\/cache<\/code>; SELinux labels make that boundary persistent across relabels.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo chown -R bagisto:apache \/var\/www\/bagisto\nsudo find \/var\/www\/bagisto -type d -exec chmod 0750 {} \\;\nsudo find \/var\/www\/bagisto -type f -exec chmod 0640 {} \\;\nsudo chmod -R g+rwX \/var\/www\/bagisto\/storage \/var\/www\/bagisto\/bootstrap\/cache\nsudo semanage fcontext -a -t httpd_sys_content_t '\/var\/www\/bagisto(\/.*)?'\nsudo semanage fcontext -a -t httpd_sys_rw_content_t '\/var\/www\/bagisto\/storage(\/.*)?'\nsudo semanage fcontext -a -t httpd_sys_rw_content_t '\/var\/www\/bagisto\/bootstrap\/cache(\/.*)?'\nsudo restorecon -Rv \/var\/www\/bagisto\nsudo setsebool -P httpd_can_network_connect_db 1<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The database boolean permits the PHP-FPM web process to reach MariaDB locally without disabling SELinux.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 7: Configure Apache and PHP-FPM<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The virtual host points requests at Bagisto\u2019s front controller and sends PHP files to the Rocky Linux PHP-FPM socket.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Replace <code>YOUR_DOMAIN<\/code> in this block before running it.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo tee \/etc\/httpd\/conf.d\/YOUR_DOMAIN.conf &gt; \/dev\/null &lt;&lt;'APACHE'\n&lt;VirtualHost *:80&gt;\n    ServerName YOUR_DOMAIN\n    DocumentRoot \/var\/www\/bagisto\/public\n\n    &lt;Directory \/var\/www\/bagisto\/public&gt;\n        Options -Indexes +FollowSymLinks\n        AllowOverride All\n        Require all granted\n    &lt;\/Directory&gt;\n\n    &lt;FilesMatch \\.php$&gt;\n        SetHandler \"proxy:unix:\/run\/php-fpm\/www.sock|fcgi:\/\/localhost\"\n    &lt;\/FilesMatch&gt;\n\n    DirectoryIndex index.php\n    ErrorLog \/var\/log\/httpd\/YOUR_DOMAIN-error.log\n    CustomLog \/var\/log\/httpd\/YOUR_DOMAIN-access.log combined\n&lt;\/VirtualHost&gt;\nAPACHE\nsudo apachectl configtest\nsudo systemctl restart php-fpm httpd<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>Syntax OK<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Step 8: Run the Bagisto installer and enable HTTPS<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The installer writes the database settings, migrations, seed data, and administrator account; Certbot then changes the public virtual host to HTTPS.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo -u bagisto -H bash -lc 'cd \/var\/www\/bagisto &amp;&amp; php artisan bagisto:install'<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">At the prompts, enter <code>https:\/\/YOUR_DOMAIN<\/code> for the application URL, <code>bagisto<\/code> for the database name and user, <code>127.0.0.1<\/code> for the host, the value used for <code>YOUR_DB_PASSWORD<\/code>, and a unique administrator email and password. The command finishes after it creates the store tables and admin account.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Confirm DNS already resolves to this VPS, then request the certificate. Replace <code>ADMIN_EMAIL<\/code> with an address that should receive renewal notices.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dnf -y install certbot python3-certbot-apache mod_ssl\nsudo certbot --apache --redirect --agree-tos --no-eff-email -m ADMIN_EMAIL -d YOUR_DOMAIN\nsudo certbot renew --dry-run<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>Congratulations, all simulated renewals succeeded<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Verify the Bagisto installation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Check the installation marker, PHP modules, services, and public HTTPS response. A successful page may return <code>200 OK<\/code> or an application redirect, depending on the storefront state.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo -u bagisto test -f \/var\/www\/bagisto\/storage\/installed &amp;&amp; echo 'Bagisto installed'\nphp -m | grep -E 'bcmath|curl|gd|intl|mbstring|PDO|pdo_mysql|SimpleXML|xml|zip'\nsudo systemctl is-active httpd mariadb php-fpm\ncurl -I https:\/\/YOUR_DOMAIN\/<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>Bagisto installed\nbcmath\ncurl\ngd\nintl\nmbstring\nPDO\npdo_mysql\nzip\nactive\nactive\nactive\nHTTP\/2 200<\/code><\/pre>\n\n\n\n<aside class=\"vl-element vl-cta-banner\" aria-label=\"Launch your Bagisto store\">\n\t<div class=\"vl-cta-banner__content\">\n\t\t<p class=\"vl-cta-banner__eyebrow\">Linux VPS hosting<\/p>\n\t\t<h3 class=\"vl-cta-banner__title\">Launch your Bagisto store<\/h3>\n\t\t<p class=\"vl-cta-banner__text\">Deploy your Rocky Linux store on a VPS with room for products, images, and database growth.<\/p>\n\t<\/div>\n\t<a class=\"vl-cta-banner__button\" href=\"\/buy-vps\" aria-label=\"View Linux VPS\">View Linux VPS<\/a>\n<\/aside>\n\n\n\n<h2 class=\"wp-block-heading\">Troubleshooting<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Composer says the PHP version is too old<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Rocky\u2019s original AppStream may still be selected, or the Remi module switch did not complete. Inspect the active stream, enable PHP 8.4 again, synchronize packages, and confirm the CLI version before rerunning Composer.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dnf module list php\nsudo dnf module reset php -y\nsudo dnf module enable php:remi-8.4 -y\nsudo dnf distro-sync -y\nphp -v<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">SQLSTATE[HY000] or \u201cAccess denied for user\u201d<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The installer values do not match the MariaDB account, or MariaDB is stopped. Test the same host, username, and database interactively, then enter the matching password in the installer.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl status mariadb --no-pager\nmariadb -u bagisto -p -h 127.0.0.1 bagisto -e 'SELECT 1;'<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Apache returns 403 or Bagisto cannot write to storage<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The document root may point at the project root, or the writable directories lost their group permissions or SELinux labels. Reapply the deployment permissions and contexts, then restart PHP-FPM and Apache.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo chmod -R g+rwX \/var\/www\/bagisto\/storage \/var\/www\/bagisto\/bootstrap\/cache\nsudo restorecon -Rv \/var\/www\/bagisto\nsudo systemctl restart php-fpm httpd<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">503 Service Unavailable or \u201cPrimary script unknown\u201d<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">PHP-FPM may be stopped, or Apache may be configured for a socket that does not exist. Verify the service and socket, then check the Apache configuration for a typo.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl status php-fpm --no-pager\nsudo ls -l \/run\/php-fpm\/www.sock\nsudo apachectl configtest<\/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>Keep <code>APP_DEBUG=false<\/code> in <code>\/var\/www\/bagisto\/.env<\/code> after installation, and clear the configuration cache after changing environment values.<\/li>\n\n\n<li>Back up the <code>bagisto<\/code> database and <code>\/var\/www\/bagisto\/storage<\/code> before upgrades or catalog imports.<\/li>\n\n\n<li>Limit SSH to your administration network when possible, and use SSH keys instead of password authentication.<\/li>\n\n\n<li>Review certificate renewal output periodically; Certbot\u2019s <code>--dry-run<\/code> check should remain successful.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Which Bagisto version does this Rocky Linux 8 guide install?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The Composer constraint installs the Bagisto 2.5 release line. It is paired here with PHP 8.4 and MariaDB 10.11, rather than the much older package versions used by legacy Bagisto tutorials.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does Bagisto require Node.js on the server?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Not for a normal Composer deployment serving the packaged storefront and admin assets. Install Node.js only if you plan to rebuild frontend or admin assets after customizing the source.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why does Apache use the <code>public<\/code> directory?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Laravel\u2019s public entry point and browser-facing files live there. Using the project root as the document root could expose <code>.env<\/code>, Composer metadata, and application code to web requests.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I use <code>php artisan serve<\/code> in production?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. That command is intended for local development and does not replace Apache, PHP-FPM, TLS, or production process management. Keep Apache as the public web server and use the PHP-FPM socket configured above.<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Which Bagisto version does this Rocky Linux 8 guide install?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"The Composer constraint installs the Bagisto 2.5 release line. It is paired here with PHP 8.4 and MariaDB 10.11, rather than the much older package versions used by legacy Bagisto tutorials.\"}}, {\"@type\": \"Question\", \"name\": \"Does Bagisto require Node.js on the server?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Not for a normal Composer deployment serving the packaged storefront and admin assets. Install Node.js only if you plan to rebuild frontend or admin assets after customizing the source.\"}}, {\"@type\": \"Question\", \"name\": \"Why does Apache use the `public` directory?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Laravel\u2019s public entry point and browser-facing files live there. Using the project root as the document root could expose `.env`, Composer metadata, and application code to web requests.\"}}, {\"@type\": \"Question\", \"name\": \"Can I use `php artisan serve` in production?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. That command is intended for local development and does not replace Apache, PHP-FPM, TLS, or production process management. Keep Apache as the public web server and use the PHP-FPM socket configured above.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Install Bagisto on Rocky Linux 8 with Apache, PHP 8.4, MariaDB 10.11, Composer, SELinux, HTTPS, and fixes for common store errors on a production VPS.","protected":false},"author":1,"featured_media":1024,"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,126,117,73,72,105],"class_list":["post-1023","post","type-post","status-publish","format-standard","has-post-thumbnail","category-guides","category-vps-hosting","tag-apache","tag-bagisto","tag-lamp-stack","tag-mariadb","tag-php","tag-rocky-linux-8","cs-entry"],"_links":{"self":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1023","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=1023"}],"version-history":[{"count":1,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1023\/revisions"}],"predecessor-version":[{"id":3922,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1023\/revisions\/3922"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media\/1024"}],"wp:attachment":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media?parent=1023"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/categories?post=1023"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/tags?post=1023"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}