{"id":1021,"date":"2026-11-06T18:00:00","date_gmt":"2026-11-06T18:00:00","guid":{"rendered":"https:\/\/vpslake.com\/blog\/?p=1021"},"modified":"2026-11-06T18:00:00","modified_gmt":"2026-11-06T18:00:00","slug":"install-bagisto-lamp-almalinux-8","status":"publish","type":"post","link":"https:\/\/vpslake.com\/blog\/2026\/11\/06\/install-bagisto-lamp-almalinux-8\/","title":{"rendered":"How to Install Bagisto on AlmaLinux 8 with LAMP"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Install Bagisto on AlmaLinux 8 with Apache, PHP 8.3, MariaDB 10.11, and Composer, then publish the store behind HTTPS. Allow about 20\u201330 minutes on a fresh VPS, including the interactive Bagisto installer.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Prerequisites<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>AlmaLinux 8.10, updated and reachable over SSH.<\/li>\n\n\n<li>A root login or a sudo-enabled user.<\/li>\n\n\n<li>At least 2 GB of RAM and 10 GB of free disk space for the application, dependencies, database, and product media.<\/li>\n\n\n<li>A domain such as <code>YOUR_DOMAIN<\/code> with an A record pointing to the VPS; ports 80 and 443 must be reachable.<\/li>\n\n\n<li>A Linux server from <a href=\"https:\/\/vpslake.com\/buy-vps\">VPSLake<\/a> with a public IPv4 address.<\/li>\n\n\n<li>A unique database password and a separate Bagisto administrator password.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This guide installs the maintained Bagisto 2.4 line. It uses PHP 8.3 from Remi\u2019s AlmaLinux-compatible repository and MariaDB 10.11 because those versions match Bagisto 2.4\u2019s current server requirements. The official <a href=\"https:\/\/devdocs.bagisto.com\/getting-started\/installation.html\" target=\"_blank\" rel=\"noopener\">Bagisto installation documentation<\/a> covers other deployment methods.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Install Apache, PHP 8.3, MariaDB, and required tools<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bagisto needs a PHP version newer than AlmaLinux 8\u2019s original default stream, so enable PHP 8.3 before installing the application packages.<\/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.3 -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-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 are suitable for catalog images and Composer dependency work. The file is separate from the package defaults, so updates will not overwrite these values.<\/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<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Check the versions and service state before continuing.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>php -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.3.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: Open only the web ports<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The store will use Apache on ports 80 and 443; MariaDB stays local and does not need port 3306 exposed.<\/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: Secure MariaDB and create a dedicated database<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The hardening script removes anonymous access and test data; the separate database account keeps Bagisto away from MariaDB\u2019s 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\">Accept the prompts to remove anonymous users, disallow remote root login, remove the test database, and reload privilege tables. Then create the store database. Replace <code>YOUR_DB_PASSWORD<\/code> before running this command and keep the value for the Bagisto installer.<\/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';\nGRANT ALL PRIVILEGES ON bagisto.* TO 'bagisto'@'localhost';\nFLUSH PRIVILEGES;\nSQL<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Test the account without putting its password into shell history.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mariadb -u bagisto -p bagisto -e 'SELECT VERSION();'<\/code><\/pre>\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 securely<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Composer downloads Bagisto and its PHP dependencies. Verify the installer checksum first, following the current <a href=\"https:\/\/getcomposer.org\/download\/\" target=\"_blank\" rel=\"noopener\">Composer download instructions<\/a>, so a damaged or altered installer is not executed.<\/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='c8b085408188070d5f52bcfe4ecfbee5f727afa458b2573b8eaaf77b3419b0bf2768dc67c86944da1544f06fa544fd47'\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\nrm 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: Download Bagisto 2.4<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Run Composer as a service account instead of root, and pin the project to the 2.4 release line that supports PHP 8.3.<\/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\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.4.*'<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The command creates <code>.env<\/code> and generates an application key through Bagisto\u2019s Composer setup hook. Do not start <code>php artisan serve<\/code> on a public VPS; Apache will serve the application through its <code>public\/<\/code> directory.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 6: Configure Apache and SELinux<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Apache must expose only Bagisto\u2019s <code>public<\/code> directory, pass PHP files to PHP-FPM, and allow Laravel\u2019s rewrite rules to run.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Replace <code>YOUR_DOMAIN<\/code> in this block with the real hostname 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 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 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<p class=\"wp-block-paragraph\">The <code>httpd_sys_rw_content_t<\/code> labels apply write access only to Laravel\u2019s runtime directories. This keeps SELinux enforcing while allowing logs, cache files, and uploaded media to work.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 7: Run the Bagisto installer<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The installer writes the database settings, runs migrations, seeds the initial store data, and creates the administrator account.<\/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\">When prompted, use these values:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Application URL: <code>http:\/\/YOUR_DOMAIN<\/code> for the moment.<\/li>\n\n\n<li>Database name: <code>bagisto<\/code>.<\/li>\n\n\n<li>Database user: <code>bagisto<\/code>.<\/li>\n\n\n<li>Database password: the value used for <code>YOUR_DB_PASSWORD<\/code>.<\/li>\n\n\n<li>Database host: <code>127.0.0.1<\/code> or <code>localhost<\/code>, matching the database account host.<\/li>\n\n\n<li>Administrator email and a long, unique administrator password.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">After the wizard finishes, point the URL in the generated environment file at the HTTPS address that you will configure next.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo -u bagisto sed -i 's#^APP_URL=.*#APP_URL=https:\/\/YOUR_DOMAIN#' \/var\/www\/bagisto\/.env\nsudo -u bagisto -H bash -lc 'cd \/var\/www\/bagisto &amp;&amp; php artisan config:clear'<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Step 8: Enable HTTPS with Let\u2019s Encrypt<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">TLS protects customer logins, checkout data, and the administrator session. Run Certbot only after DNS resolves to this server and HTTP traffic can reach port 80.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Replace <code>ADMIN_EMAIL<\/code> with an address that receives certificate 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 PHP modules, database, service state, and public HTTPS response. A <code>200 OK<\/code> or an expected application redirect shows that Apache and PHP-FPM are serving the store.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>php -m | grep -E 'bcmath|calendar|curl|gd|intl|mbstring|PDO|pdo_mysql|SimpleXML|xml|zip'\nsudo mariadb -e \"SHOW DATABASES LIKE 'bagisto';\"\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>bcmath\ncurl\ngd\nintl\nmbstring\nPDO\npdo_mysql\nzip\nbagisto\nactive\nactive\nactive\nHTTP\/1.1 200 OK<\/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 Bagisto on an AlmaLinux VPS with the resources your catalog needs.<\/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 reports that PHP 8.3 is required<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The old AlmaLinux PHP stream is still selected, or the Remi module did not replace it. Check the active stream and switch it before running Composer again.<\/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.3 -y\nsudo dnf distro-sync -y\nphp -v<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">SQLSTATE[HY000] [1045] Access denied<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The installer\u2019s database password or host does not match the MariaDB account. Test the exact values interactively, and use <code>localhost<\/code> if the account was created as <code>'bagisto'@'localhost'<\/code>; use <code>127.0.0.1<\/code> only if you also create that host-specific account.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mariadb -u bagisto -p bagisto -e 'SELECT 1;'<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Apache returns 403 Forbidden or Laravel cannot write to storage<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The directory permissions or SELinux labels were changed after the install. Reapply both the group write permissions and persistent contexts, then restart PHP-FPM.<\/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 PHP source appears in the browser<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">PHP-FPM is stopped, or Apache is pointing at a missing socket. Confirm the socket exists and inspect the service log before restarting both services.<\/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\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Does Bagisto work on AlmaLinux 8?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Yes. Bagisto 2.4 runs on PHP 8.3 or 8.4 and supports MariaDB 10.11. AlmaLinux 8\u2019s default PHP stream is older, which is why this guide enables the PHP 8.3 stream before installing Bagisto.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why does Apache point to the <code>public<\/code> directory?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Laravel\u2019s front controller and public assets live there. Pointing Apache at the project root could expose environment files, Composer metadata, and application source to web requests.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Do I need Node.js for a normal Bagisto install?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. A Composer installation includes the application assets needed for a standard deployment. Install Node.js only when you plan to rebuild Bagisto\u2019s storefront, admin, or installer assets.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Where is the Bagisto administrator login?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The default administrator path is <code>https:\/\/YOUR_DOMAIN\/admin<\/code>, unless you choose a different admin URL during installation. Use the administrator email and password created by the installer, and change the password immediately if you used a temporary value.<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Does Bagisto work on AlmaLinux 8?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Yes. Bagisto 2.4 runs on PHP 8.3 or 8.4 and supports MariaDB 10.11. AlmaLinux 8\u2019s default PHP stream is older, which is why this guide enables the PHP 8.3 stream before installing Bagisto.\"}}, {\"@type\": \"Question\", \"name\": \"Why does Apache point to the `public` directory?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Laravel\u2019s front controller and public assets live there. Pointing Apache at the project root could expose environment files, Composer metadata, and application source to web requests.\"}}, {\"@type\": \"Question\", \"name\": \"Do I need Node.js for a normal Bagisto install?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. A Composer installation includes the application assets needed for a standard deployment. Install Node.js only when you plan to rebuild Bagisto\u2019s storefront, admin, or installer assets.\"}}, {\"@type\": \"Question\", \"name\": \"Where is the Bagisto administrator login?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"The default administrator path is `https:\/\/YOUR_DOMAIN\/admin`, unless you choose a different admin URL during installation. Use the administrator email and password created by the installer, and change the password immediately if you used a temporary value.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Install Bagisto on AlmaLinux 8 with Apache, PHP 8.3, MariaDB 10.11, Composer, secure SELinux permissions, HTTPS, and troubleshooting for VPS stores.","protected":false},"author":1,"featured_media":1022,"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":[94,71,126,117,73,72],"class_list":["post-1021","post","type-post","status-publish","format-standard","has-post-thumbnail","category-guides","category-vps-hosting","tag-almalinux-8","tag-apache","tag-bagisto","tag-lamp-stack","tag-mariadb","tag-php","cs-entry"],"_links":{"self":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1021","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=1021"}],"version-history":[{"count":1,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1021\/revisions"}],"predecessor-version":[{"id":3917,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1021\/revisions\/3917"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media\/1022"}],"wp:attachment":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media?parent=1021"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/categories?post=1021"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/tags?post=1021"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}