{"id":1117,"date":"2026-11-18T18:00:00","date_gmt":"2026-11-18T18:00:00","guid":{"rendered":"https:\/\/vpslake.com\/blog\/?p=1117"},"modified":"2026-11-18T18:00:00","modified_gmt":"2026-11-18T18:00:00","slug":"install-docmost-docker-rocky-linux-9","status":"publish","type":"post","link":"https:\/\/vpslake.com\/blog\/2026\/11\/18\/install-docmost-docker-rocky-linux-9\/","title":{"rendered":"How to Install Docmost Using Docker on Rocky Linux 9"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Install Docmost using Docker on Rocky Linux 9 to run a collaborative wiki with PostgreSQL, Redis, and automatic HTTPS. With DNS ready before you begin, the deployment takes about 15 minutes and ends at the Docmost workspace setup screen.<\/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 64-bit Rocky Linux 9 VPS with at least 2 GB of RAM and 10 GB of free disk space. Reserve more disk for file uploads and Docker image updates.<\/li>\n\n\n<li>SSH access as <code>root<\/code>, or a normal Linux account 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>. Caddy uses this hostname for a trusted TLS certificate.<\/li>\n\n\n<li>Inbound TCP ports 80 and 443 allowed by both the VPS provider and the server firewall. Port 3000 will remain private.<\/li>\n\n\n<li>A <a href=\"https:\/\/vpslake.com\/buy-vps\">VPSLake Linux VPS<\/a> if you need a Rocky Linux server with root access.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The commands assume a non-root SSH user and therefore use <code>sudo<\/code>. If you are logged in as <code>root<\/code>, remove <code>sudo<\/code> from each command. This setup keeps SELinux enabled and uses Rocky Linux\u2019s DNF and firewalld.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Confirm Rocky Linux 9 and prepare the host<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: Confirming the release and architecture prevents Docker\u2019s Enterprise Linux repository from being applied to the wrong system.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>. \/etc\/os-release\nprintf '%s\\n' \"$PRETTY_NAME\"\nprintf 'Release: %s\\n' \"$VERSION_ID\"\nuname -m\ngetenforce\nsudo dnf upgrade -y\nsudo dnf install -y ca-certificates curl dnf-plugins-core openssl<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The checks should identify Rocky Linux 9, a 64-bit architecture, and an enforcing or permissive SELinux mode:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Rocky Linux 9.x (Blue Onyx)\nRelease: 9.x\nx86_64\nEnforcing<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The minor release may differ. Resolve any DNF mirror, DNS, or GPG-signature failure before continuing; do not disable SELinux to make the installation proceed.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Install Docker Engine and Compose<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: Docker supplies the runtime, while the Compose plugin starts Docmost and its PostgreSQL, Redis, and Caddy services from one definition.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On a new VPS, remove packages that can conflict with Docker\u2019s runtime. If this machine already runs Podman containers, inspect those workloads first and skip the removal until you have a migration plan.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dnf remove -y docker docker-client docker-client-latest docker-common docker-latest docker-latest-logrotate docker-logrotate docker-engine podman runc\nsudo dnf config-manager --add-repo https:\/\/download.docker.com\/linux\/rhel\/docker-ce.repo\nsudo dnf makecache\nsudo dnf install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin\nsudo systemctl enable --now docker<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This follows Docker\u2019s <a href=\"https:\/\/docs.docker.com\/engine\/install\/rhel\/\" target=\"_blank\" rel=\"noopener\">official RHEL repository installation method<\/a> using the RHEL-compatible package channel on Rocky Linux 9. Keep Docker commands under <code>sudo<\/code>; membership in the <code>docker<\/code> group grants root-equivalent access.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check the daemon, Compose plugin, and a disposable container before creating the Docmost stack:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl is-active docker\nsudo docker version --format 'Client {{.Client.Version}} \/ Server {{.Server.Version}}'\nsudo docker compose version\nsudo docker run --rm hello-world<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output is similar to this, with different patch versions as packages change:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>active\nClient 29.x.y \/ Server 29.x.y\nDocker Compose version v2.x.y\nHello from Docker!<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Create the Docmost environment file<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: The application secret protects Docmost sessions, and using one generated database password in both services prevents connection mismatches.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Generate hexadecimal values so the database password is safe inside a PostgreSQL connection URL, then create the deployment directory:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openssl rand -hex 32\nopenssl rand -hex 24\nsudo install -d -m 0755 \/opt\/docmost\nsudo vi \/opt\/docmost\/.env<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">In <code>vi<\/code>, create <code>\/opt\/docmost\/.env<\/code>. Put the first command\u2019s output in <code>APP_SECRET<\/code>, the second in <code>DB_PASSWORD<\/code>, and replace <code>YOUR_DOMAIN<\/code> with the real hostname:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>APP_URL=https:\/\/YOUR_DOMAIN\nAPP_SECRET=REPLACE_WITH_64_HEX_CHARACTERS\nDB_PASSWORD=REPLACE_WITH_48_HEX_CHARACTERS<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Save the file and make it readable only by <code>root<\/code> because it contains a database credential:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo chown root:root \/opt\/docmost\/.env\nsudo chmod 600 \/opt\/docmost\/.env\nsudo grep -E '^(APP_URL|APP_SECRET|DB_PASSWORD)=' \/opt\/docmost\/.env | sed 's\/=.*\/=&lt;set&gt;\/'<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The final command should show three variables ending in <code>&lt;set&gt;<\/code> without revealing their values. Docmost\u2019s <a href=\"https:\/\/docmost.com\/docs\/installation\" target=\"_blank\" rel=\"noopener\">official installation guide<\/a> requires an <code>APP_SECRET<\/code> of at least 32 characters; <code>openssl rand -hex 32<\/code> produces 64.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Add Caddy and the Compose services<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: Caddy handles public HTTPS and WebSocket forwarding, while the Compose network keeps PostgreSQL and Redis away from the internet.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Create the Caddyfile with the same hostname used in <code>.env<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo vi \/opt\/docmost\/Caddyfile<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Enter this content:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>YOUR_DOMAIN {\n    reverse_proxy docmost:3000\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Now create <code>\/opt\/docmost\/docker-compose.yml<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo vi \/opt\/docmost\/docker-compose.yml<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Paste the following configuration:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>services:\n  caddy:\n    image: caddy:2\n    ports:\n      - \"80:80\"\n      - \"443:443\"\n    volumes:\n      - .\/Caddyfile:\/etc\/caddy\/Caddyfile:ro,Z\n      - caddy_data:\/data\n      - caddy_config:\/config\n    depends_on:\n      - docmost\n    restart: unless-stopped\n\n  docmost:\n    image: docmost\/docmost:latest\n    depends_on:\n      - db\n      - redis\n    environment:\n      APP_URL: \"${APP_URL}\"\n      APP_SECRET: \"${APP_SECRET}\"\n      DATABASE_URL: \"postgresql:\/\/docmost:${DB_PASSWORD}@db:5432\/docmost\"\n      REDIS_URL: \"redis:\/\/redis:6379\"\n    ports:\n      - \"127.0.0.1:3000:3000\"\n    restart: unless-stopped\n    volumes:\n      - docmost:\/app\/data\/storage\n\n  db:\n    image: postgres:18\n    environment:\n      POSTGRES_DB: docmost\n      POSTGRES_USER: docmost\n      POSTGRES_PASSWORD: \"${DB_PASSWORD}\"\n    restart: unless-stopped\n    volumes:\n      - db_data:\/var\/lib\/postgresql\n\n  redis:\n    image: redis:8\n    command: [\"redis-server\", \"--appendonly\", \"yes\", \"--maxmemory-policy\", \"noeviction\"]\n    restart: unless-stopped\n    volumes:\n      - redis_data:\/data\n\nvolumes:\n  docmost:\n  db_data:\n  redis_data:\n  caddy_data:\n  caddy_config:<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The <code>:Z<\/code> suffix labels the Caddy bind mount for Rocky\u2019s SELinux policy. The loopback-only mapping prevents remote clients from reaching port 3000 directly, while the named volumes preserve pages, uploads, database records, Redis data, and certificates.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Configure firewalld for the public endpoints<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: The firewall should expose SSH and Caddy\u2019s web ports, but not Docmost, PostgreSQL, or Redis as public services.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Allow SSH before reloading the firewall. If SSH uses a custom port, add that port instead of the <code>ssh<\/code> service:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dnf install -y firewalld\nsudo systemctl enable --now firewalld\nsudo 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 last command should include <code>ssh<\/code>, <code>http<\/code>, and <code>https<\/code>. Allow the same web ports in the VPS provider\u2019s network firewall; Caddy needs port 80 for certificate validation and port 443 for visitors.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 6: Validate and start the stack<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: Rendering the Compose file first catches an invalid YAML file or missing <code>.env<\/code> variable before images are downloaded and containers are created.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/opt\/docmost\nsudo docker compose config --quiet\nsudo docker compose pull\nsudo docker compose up -d\nsudo docker compose ps\nsudo ss -ltnp | grep -E ':(80|443|3000)\\b'<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><code>config --quiet<\/code> is silent when the configuration is valid. A running deployment has four services up, with port 3000 bound only to loopback:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>NAME                 SERVICE   STATUS   PORTS\ndocmost-caddy-1      caddy     Up       0.0.0.0:80-&gt;80\/tcp, 0.0.0.0:443-&gt;443\/tcp\ndocmost-docmost-1    docmost   Up       127.0.0.1:3000-&gt;3000\/tcp\ndocmost-db-1         db        Up\ndocmost-redis-1      redis     Up<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Compose may choose different names. The <code>ss<\/code> output should show listeners for 80, 443, and <code>127.0.0.1:3000<\/code>, not <code>0.0.0.0:3000<\/code>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verify the Docmost installation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Check the health endpoint through the public hostname. This single request tests DNS, firewalld, Caddy\u2019s certificate, the reverse proxy, and Docmost\u2019s HTTP listener:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>curl -fsS -o \/dev\/null -w 'HTTP %{http_code}\\n' https:\/\/YOUR_DOMAIN\/api\/health<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>HTTP 200<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Open <code>https:\/\/YOUR_DOMAIN<\/code> in a browser. The Docmost setup page should appear; enter a workspace name, administrator details, and a unique strong password. Create a page and add a small attachment so you verify both the editor and persistent storage.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Finish with a short log review:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/opt\/docmost\nsudo docker compose logs --since=5m caddy docmost db redis<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The services should not be in a restart loop, and the logs should not report an ACME certificate failure or PostgreSQL authentication error.<\/p>\n\n\n\n<aside class=\"vl-element vl-cta-banner\" aria-label=\"Run Docmost privately\">\n\t<div class=\"vl-cta-banner__content\">\n\t\t<p class=\"vl-cta-banner__eyebrow\">Rocky Linux VPS<\/p>\n\t\t<h3 class=\"vl-cta-banner__title\">Run Docmost privately<\/h3>\n\t\t<p class=\"vl-cta-banner__text\">Deploy a Docker-ready Rocky Linux VPS for a collaborative documentation workspace behind HTTPS.<\/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\"><code>No match for argument: docker-ce<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">DNF cannot see Docker\u2019s repository, or its metadata is stale. Re-add the RHEL-compatible repository, refresh metadata, and retry the packages:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dnf config-manager --add-repo https:\/\/download.docker.com\/linux\/rhel\/docker-ce.repo\nsudo dnf clean all\nsudo dnf makecache\nsudo dnf install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If the error persists, confirm that <code>\/etc\/os-release<\/code> reports Rocky Linux 9 and that the VPS can resolve <code>download.docker.com<\/code>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Caddy reports <code>permission denied<\/code> for <code>Caddyfile<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The bind mount is missing its SELinux label, or the file is not readable. Confirm the Compose mount ends in <code>:ro,Z<\/code>, then recreate Caddy so Docker applies the label:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo chmod 644 \/opt\/docmost\/Caddyfile\ncd \/opt\/docmost\nsudo docker compose up -d --force-recreate caddy\nsudo docker compose logs --tail=40 caddy<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Do not disable SELinux as a workaround.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The browser shows <code>502 Bad Gateway<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Caddy is reachable, but Docmost is still starting or has exited. Check the application and dependency logs, then test the private listener directly:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/opt\/docmost\nsudo docker compose ps\nsudo docker compose logs --tail=80 docmost db redis\ncurl -i http:\/\/127.0.0.1:3000\/api\/health<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If the logs show <code>password authentication failed for user \"docmost\"<\/code>, restore the original <code>DB_PASSWORD<\/code> in <code>.env<\/code>; PostgreSQL keeps the password from its first initialization. Do not run <code>docker compose down -v<\/code> on a live installation.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Caddy cannot obtain an HTTPS certificate<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The domain may still resolve to another server, or port 80\/443 may be blocked upstream. Check the A record, run <code>sudo firewall-cmd --zone=public --list-services<\/code>, allow both ports in the VPS provider firewall, and keep Caddy running while it retries the certificate request.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Hardening and maintenance<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Keep <code>127.0.0.1:3000<\/code> in the Compose mapping and never publish PostgreSQL or Redis ports.<\/li>\n\n\n<li>Back up the <code>docmost<\/code>, <code>db_data<\/code>, <code>redis_data<\/code>, <code>caddy_data<\/code>, and <code>caddy_config<\/code> volumes before upgrades or host maintenance.<\/li>\n\n\n<li>Review image changes before applying them. From <code>\/opt\/docmost<\/code>, use <code>sudo docker compose pull<\/code> followed by <code>sudo docker compose up -d<\/code>.<\/li>\n\n\n<li>After confirming the wiki works, use the <a href=\"https:\/\/vpslake.com\/sshd-hardening-generator\">VPSLake SSH hardening generator<\/a> and keep <code>.env<\/code> readable only by <code>root<\/code>.<\/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 use an IP address instead of a domain?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You can test Docmost over an IP only by changing the setup to publish port 3000, but that removes Caddy\u2019s trusted automatic certificate. A domain is the safer production choice and gives <code>APP_URL<\/code> a stable HTTPS value.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why does the Compose file include the <code>:Z<\/code> mount option?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Rocky Linux uses SELinux labels to control what containers may read. <code>:Z<\/code> gives this private Caddy mount a container-readable label without weakening the host\u2019s SELinux policy.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Where is the workspace data stored?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Uploaded files are stored in the <code>docmost<\/code> named volume, while PostgreSQL uses <code>db_data<\/code>. Redis and Caddy use separate volumes, so recreating containers does not remove data unless you explicitly remove the volumes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do I update Docmost later?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Back up the volumes, then run <code>sudo docker compose pull<\/code> and <code>sudo docker compose up -d<\/code> from <code>\/opt\/docmost<\/code>. Review <code>sudo docker compose ps<\/code> and the recent logs before allowing users back into the updated workspace.<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Can I use an IP address instead of a domain?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"You can test Docmost over an IP only by changing the setup to publish port 3000, but that removes Caddy\u2019s trusted automatic certificate. A domain is the safer production choice and gives `APP_URL` a stable HTTPS value.\"}}, {\"@type\": \"Question\", \"name\": \"Why does the Compose file include the `:Z` mount option?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Rocky Linux uses SELinux labels to control what containers may read. `:Z` gives this private Caddy mount a container-readable label without weakening the host\u2019s SELinux policy.\"}}, {\"@type\": \"Question\", \"name\": \"Where is the workspace data stored?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Uploaded files are stored in the `docmost` named volume, while PostgreSQL uses `db_data`. Redis and Caddy use separate volumes, so recreating containers does not remove data unless you explicitly remove the volumes.\"}}, {\"@type\": \"Question\", \"name\": \"How do I update Docmost later?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Back up the volumes, then run `sudo docker compose pull` and `sudo docker compose up -d` from `\/opt\/docmost`. Review `sudo docker compose ps` and the recent logs before allowing users back into the updated workspace.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Install Docmost using Docker on Rocky Linux 9 with PostgreSQL, Redis, Caddy HTTPS, firewalld, SELinux, and health checks for a private wiki.","protected":false},"author":1,"featured_media":1118,"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":[118,138,100,139],"class_list":["post-1117","post","type-post","status-publish","format-standard","has-post-thumbnail","category-guides","category-vps-hosting","tag-docker","tag-docmost","tag-rocky-linux-9","tag-self-hosting","cs-entry"],"_links":{"self":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1117","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=1117"}],"version-history":[{"count":1,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1117\/revisions"}],"predecessor-version":[{"id":4100,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1117\/revisions\/4100"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media\/1118"}],"wp:attachment":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media?parent=1117"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/categories?post=1117"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/tags?post=1117"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}