{"id":13248,"date":"2025-12-20T11:04:50","date_gmt":"2025-12-20T05:34:50","guid":{"rendered":"https:\/\/www.youstable.com\/blog\/?p=13248"},"modified":"2026-09-07T11:12:00","modified_gmt":"2026-09-07T05:42:00","slug":"use-cron-jobs-on-linux","status":"publish","type":"post","link":"https:\/\/www.youstable.com\/blog\/use-cron-jobs-on-linux\/","title":{"rendered":"How to Use Cron Jobs on Linux Server? Scheduling Explained"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><strong>Cron jobs on a Linux server<\/strong> are scheduled tasks that run automatically at fixed times, dates, or intervals. You define tasks in a crontab file using a concise schedule syntax (minute, hour, day, month, weekday) and a command to execute.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This lets you automate backups, updates, monitoring, and routine server maintenance reliably.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you\u2019re new to automation, learning how to use <a href=\"https:\/\/www.youstable.com\/blog\/install-cron-jobs-on-linux\/\"><strong>cron jobs on a Linux server<\/strong><\/a> is one of the most valuable admin skills. In this guide, you\u2019ll master crontab basics, schedule syntax, logging, debugging, security, and production-ready examples\u2014based on real-world hosting experience.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"what-is-cron-and-how-it-works\"><strong>What is Cron and How it Works<\/strong><\/h2>\n\n\n\n<div class=\"wp-block-media-text has-media-on-the-right is-stacked-on-mobile\"><div class=\"wp-block-media-text__content\">\n<p class=\"wp-block-paragraph\">Cron is a time-based scheduler on Unix\/Linux systems. The cron daemon (<code>crond<\/code>) reads crontab files and runs commands at the specified times. Each user can have a personal crontab, and the system has global cron directories for standardized tasks.<\/p>\n<\/div><figure class=\"wp-block-media-text__media\"><img loading=\"lazy\" decoding=\"async\" width=\"1168\" height=\"784\" src=\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2025\/12\/What-Is-Cron-and-How-It-Works.png\" alt=\"\" class=\"wp-image-13600 size-full\" srcset=\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2025\/12\/What-Is-Cron-and-How-It-Works.png 1168w, https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2025\/12\/What-Is-Cron-and-How-It-Works-150x101.png 150w\" sizes=\"auto, (max-width: 1168px) 100vw, 1168px\" \/><\/figure><\/div>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>User crontab:<\/strong> user-specific schedules (via <code>crontab -e<\/code>).<\/li>\n\n\n\n<li><strong>System crontab: <\/strong>global schedules (e.g., <code>\/etc\/crontab<\/code>, <code>\/etc\/cron.d\/<\/code>).<\/li>\n\n\n\n<li><strong>Cron daemon:<\/strong> continuously monitors schedules and executes commands.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"quick-start-create-your-first-cron-job\"><strong>Quick Start: Create Your First Cron Job<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Let\u2019s create a simple <a href=\"https:\/\/www.youstable.com\/blog\/what-is-cron-jobs-on-linux-server\/\">cron job<\/a> that writes a timestamp to a log file every 5 minutes.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Open your user crontab\ncrontab -e\n\n# Add this line, save and exit:\n*\/5 * * * * \/usr\/bin\/date &gt;&gt; $HOME\/cron-test.log 2&gt;&amp;1<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Wait a few minutes, then check the file. If you see timestamps appended, your cron job is running correctly.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"cron-schedule-syntax-explained\"><strong>Cron Schedule Syntax Explained<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Each cron line has five time fields followed by the command. Special strings simplify common schedules.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500 minute (0\u201359)\n# \u2502 \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500 hour (0\u201323)\n# \u2502 \u2502 \u250c\u2500\u2500\u2500\u2500\u2500 day of month (1\u201331)\n# \u2502 \u2502 \u2502 \u250c\u2500\u2500\u2500 month (1\u201312 or names)\n# \u2502 \u2502 \u2502 \u2502 \u250c\u2500 day of week (0\u20137 or names; 0\/7=Sun)\n# \u2502 \u2502 \u2502 \u2502 \u2502\n# * * * * *  command-to-run\n\n# Special strings:\n@reboot     run once at startup\n@hourly     run once an hour\n@daily      run once a day\n@weekly     run once a week\n@monthly    run once a month\n@yearly     run once a year<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Every 15 minutes:<\/strong> <code>*\/15 * * * * \/path\/script.sh<\/code><\/li>\n\n\n\n<li><strong>Every day at 02:30:<\/strong> <code>30 2 * * * \/path\/backup.sh<\/code><\/li>\n\n\n\n<li><strong>Mondays at 08:00:<\/strong> <code>0 8 * * 1 \/path\/report.sh<\/code><\/li>\n\n\n\n<li><strong>First day of month 00:05:<\/strong> <code>5 0 1 * * \/path\/monthly.sh<\/code><\/li>\n\n\n\n<li><strong>At boot: <\/strong><code>@reboot \/usr\/local\/bin\/startup-check.sh<\/code><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"managing-crontab-edit-list-remove-and-scope\"><strong>Managing Crontab: Edit, List, Remove, and Scope<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Use <code>crontab<\/code> to manage user-specific schedules. System-wide schedules live in files and directories under <code>\/etc<\/code>.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Edit current user's crontab\ncrontab -e\n\n# List jobs\ncrontab -l\n\n# Remove all jobs (careful!)\ncrontab -r\n\n# Edit another user's crontab (root only)\nsudo crontab -u username -e\n\n# System-wide cron files\n\/etc\/crontab\n\/etc\/cron.d\/ (individual files)\n\/etc\/cron.hourly\/, \/etc\/cron.daily\/, \/etc\/cron.weekly\/, \/etc\/cron.monthly\/<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">On many distributions, <code>\/etc\/crontab<\/code> includes a user field. In user crontabs, omit the user field; the job runs as that user.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"environment-path-and-permissions\"><strong>Environment, PATH, and Permissions<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Cron uses a minimal environment. If a command runs fine in your shell but fails in cron, the PATH or environment variables are likely missing.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Good practice: set the shell, PATH, and crucial env vars at top of crontab\nSHELL=\/bin\/bash\nPATH=\/usr\/local\/sbin:\/usr\/local\/bin:\/usr\/sbin:\/usr\/bin:\/sbin:\/bin\nMAILTO=you@example.com\n# For apps:\n# NODE_ENV=production\n# APP_HOME=\/var\/www\/app<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Always use absolute paths to binaries and scripts. Ensure scripts are executable and owned by the correct user.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Make script executable and secure\nchmod 750 \/usr\/local\/bin\/backup.sh\nchown root:root \/usr\/local\/bin\/backup.sh\n\n# Use absolute paths inside scripts\n\/usr\/bin\/mysqldump ... &gt; \/var\/backups\/db.sql<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"logging-debugging-and-monitoring-cron-jobs\"><strong>Logging, Debugging, and Monitoring Cron Jobs<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">By default, cron emails output to <code>MAILTO<\/code>. In many servers, system logs also record cron events.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Review logs: <\/strong><code>\/var\/log\/cron<\/code> or <code>\/var\/log\/syslog<\/code> (distribution-dependent).<\/li>\n\n\n\n<li>Send output to a log file with timestamps.<\/li>\n\n\n\n<li>Test commands interactively before scheduling.<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code># Log stdout\/stderr to a file with timestamps\n*\/10 * * * * \/usr\/local\/bin\/healthcheck.sh &gt;&gt; \/var\/log\/healthcheck.log 2&gt;&amp;1\n\n# Wrap with a logger\n*\/30 * * * * \/usr\/local\/bin\/task.sh 2&gt;&amp;1 | \/usr\/bin\/logger -t task_cron\n\n# Verify cron service\nsystemctl status cron     # Debian\/Ubuntu\nsystemctl status crond    # CentOS\/RHEL\/AlmaLinux\/Rocky<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If a job doesn\u2019t fire, check time, time zone, permissions, SELinux\/AppArmor, and whether the script requires a TTY or interactive shell.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"common-cron-job-examples-you-can-copy\"><strong>Common Cron Job Examples You Can Copy<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Below are production-friendly examples for typical server tasks. Adjust paths and users to your environment.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># 1) Rotate and compress logs daily at 00:10\n10 0 * * * \/usr\/sbin\/logrotate -f \/etc\/logrotate.conf\n\n# 2) MySQL database backup every night at 02:00\n0 2 * * * \/usr\/bin\/mysqldump -u backup -p'strongPass' --single-transaction --quick --lock-tables=false dbname | \/usr\/bin\/gzip &gt; \/var\/backups\/dbname-$(date +%F).sql.gz\n\n# 3) Sync files to remote storage at 03:15\n15 3 * * * \/usr\/bin\/rsync -az \/var\/www\/ user@backup.example:\/data\/www\/\n\n# 4) Run a WordPress cron alternative every 5 minutes\n*\/5 * * * * \/usr\/bin\/php -d detect_unicode=0 \/var\/www\/html\/wp-cron.php &gt;&gt; \/var\/log\/wp-cron.log 2&gt;&amp;1\n\n# 5) Renew Let's Encrypt certificates twice daily\n0 3,15 * * * \/usr\/bin\/certbot renew --quiet --deploy-hook \"systemctl reload nginx\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For WordPress sites, consider disabling the internal pseudo-cron (<code>DISABLE_WP_CRON<\/code>) and trigger <code>wp-cron.php<\/code> via system cron for consistent execution under load.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"security-best-practices-for-cron\"><strong>Security Best Practices for Cron<\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Least privilege: <\/strong>run jobs as the minimal-privilege user; avoid root unless necessary.<\/li>\n\n\n\n<li><strong>Validate scripts: <\/strong>store in secured directories with restricted permissions.<\/li>\n\n\n\n<li>Use absolute paths to prevent PATH injection risks.<\/li>\n\n\n\n<li>Escape secrets; prefer env files or a secret manager over inline passwords.<\/li>\n\n\n\n<li><strong>Restrict cron usage: <\/strong>manage <code>\/etc\/cron.allow<\/code> and <code>\/etc\/cron.deny<\/code>.<\/li>\n\n\n\n<li>Log and alert: forward logs to a SIEM or alerting system.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"cron-vs-systemd-timers-vs-anacron\"><strong>Cron vs. Systemd Timers vs. Anacron<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Cron is universal and simple. Systemd timers add dependency management, missed-run handling, and richer logging, while Anacron ensures periodic jobs run even if the system was off at the scheduled time.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use cron for precise, lightweight schedules.<\/li>\n\n\n\n<li>Use systemd timers for complex orchestration and reliable catch-up.<\/li>\n\n\n\n<li>Use Anacron for laptops\/instances that aren\u2019t always on.<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code># Example: run script every 15 minutes with systemd timer\n# \/etc\/systemd\/system\/report.service\n&#91;Unit]\nDescription=Generate report\n\n&#91;Service]\nType=oneshot\nExecStart=\/usr\/local\/bin\/report.sh\n\n# \/etc\/systemd\/system\/report.timer\n&#91;Unit]\nDescription=Run report every 15 minutes\n\n&#91;Timer]\nOnBootSec=2m\nOnUnitActiveSec=15m\nUnit=report.service\n\n&#91;Install]\nWantedBy=timers.target\n\n# Enable\nsystemctl enable --now report.timer<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"cron-on-shared-hosting-and-with-youstable\"><strong>Cron on Shared Hosting and With YouStable<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">On shared hosting with cPanel or similar, you can configure cron jobs from the control panel. The interface helps set schedules, command paths, and email notifications without touching the shell.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At YouStable, our hosting plans support cron via UI and SSH. For busy WordPress or WooCommerce sites, our team can help convert WP-Cron to system cron, tune PHP CLI settings, and configure reliable logs\u2014so scheduled tasks run on time even under heavy traffic.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"troubleshooting-checklist\"><strong>Troubleshooting Checklist<\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Is <code>cron<\/code>\/<code>crond<\/code> running? Check with <code>systemctl<\/code>.<\/li>\n\n\n\n<li>Does your schedule match your time zone? Verify with <code>date<\/code>.<\/li>\n\n\n\n<li>Are absolute paths used for binaries and files?<\/li>\n\n\n\n<li>Is the script executable and owned by the correct user?<\/li>\n\n\n\n<li>Are needed environment variables set in the crontab?<\/li>\n\n\n\n<li>Any output or errors in logs or emails (<code>MAILTO<\/code>)?<\/li>\n\n\n\n<li>SELinux\/AppArmor blocking? Review audit logs or set proper contexts.<\/li>\n\n\n\n<li>Does the command require a TTY or interactive input? If so, refactor.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"real-world-tips-from-hosting-experience\"><strong>Real-World Tips from Hosting Experience<\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Batch heavy jobs during off-peak hours to reduce load spikes.<\/li>\n\n\n\n<li>Stagger related jobs by a few minutes to avoid contention.<\/li>\n\n\n\n<li>Throttle with <code>flock<\/code> to prevent overlapping runs on slow servers.<\/li>\n\n\n\n<li>Version control your scripts and keep a change log tied to cron edits.<\/li>\n\n\n\n<li>Test with the same user that will run the cron job (env differences matter).<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code># Use flock to prevent overlapping jobs\n*\/10 * * * * \/usr\/bin\/flock -n \/var\/run\/report.lock \/usr\/local\/bin\/report.sh<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"faqs\"><strong>FAQs: <\/strong><\/h2>\n\n\n<div id=\"rank-math-faq\" class=\"rank-math-block\">\n<div class=\"rank-math-list \">\n<div id=\"faq-question-1765791900775\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"u003cstrongu003ehow-do-i-list-all-cron-jobs-for-a-useru003c-strongu003e\">u003cstrongu003eHow do I list all cron jobs for a user?u003c\/strongu003e<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Run u003ccodeu003ecrontab -lu003c\/codeu003e as that user to view their crontab. As root, use u003ccodeu003ecrontab -u username -lu003c\/codeu003e. System-wide jobs can be found in u003ccodeu003e\/etc\/crontabu003c\/codeu003e, u003ccodeu003e\/etc\/cron.d\/u003c\/codeu003e, and periodic directories like u003ccodeu003e\/etc\/cron.daily\/u003c\/codeu003e.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1765791917372\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"u003cstrongu003ehow-do-i-run-a-cron-job-every-minuteu003c-strongu003e\">u003cstrongu003eHow do I run a cron job every minute?u003c\/strongu003e<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Use u003ccodeu003e* * * * *u003c\/codeu003e as the schedule. Example: u003ccodeu003e* * * * * \/usr\/local\/bin\/task.sh u003eu003e \/var\/log\/task.log 2u003eu0026amp;1u003c\/codeu003e. Ensure the script is executable and uses absolute paths.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1765791931794\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"u003cstrongu003ewhere-are-cron-logs-storedu003c-strongu003e\">u003cstrongu003eWhere are cron logs stored?u003c\/strongu003e<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>On Debian\/Ubuntu, check u003ccodeu003e\/var\/log\/syslogu003c\/codeu003e for cron entries; on RHEL\/CentOS\/AlmaLinux\/Rocky, check u003ccodeu003e\/var\/log\/cronu003c\/codeu003e. You can also redirect job output to dedicated log files for easier debugging.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1765791944581\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"u003cstrongu003ewhats-the-difference-between-user-crontab-and-etc-crontabu003c-strongu003e\">u003cstrongu003eWhat\u2019s the difference between user crontab and \/etc\/crontab?u003c\/strongu003e<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>User crontabs run as the owning user and omit the user field. u003ccodeu003e\/etc\/crontabu003c\/codeu003e is system-wide and includes a user field for each job, letting you specify which user executes the command.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1765791956285\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"u003cstrongu003ewhy-does-my-cron-job-run-manually-but-not-in-cronu003c-strongu003e\">u003cstrongu003eWhy does my cron job run manually but not in cron?u003c\/strongu003e<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Usually due to environment differences: missing PATH, required variables, permissions, or relative paths. Set u003ccodeu003eSHELLu003c\/codeu003e and u003ccodeu003ePATHu003c\/codeu003e in the crontab, use absolute paths, and redirect output to logs to capture errors.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Cron jobs on a Linux server are scheduled tasks that run automatically at fixed times, dates, or intervals. You define [&hellip;]<\/p>\n","protected":false},"author":21,"featured_media":15515,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"iawp_total_views":48,"footnotes":""},"categories":[350,2259],"tags":[],"class_list":["post-13248","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-knowledgebase","category-kb-linux"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts\/13248","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/users\/21"}],"replies":[{"embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/comments?post=13248"}],"version-history":[{"count":1,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts\/13248\/revisions"}],"predecessor-version":[{"id":23257,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts\/13248\/revisions\/23257"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/media\/15515"}],"wp:attachment":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/media?parent=13248"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/categories?post=13248"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/tags?post=13248"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}