Sequenzy
FeaturesPricingCustomersDocsChangelogBlog
Get Started

Sequenzy

Email Marketing Tool for SaaS.

Make us preferred on Google
Compare
  • vs Resend
  • vs Mailchimp
  • vs Loops
  • vs ConvertKit
X vs Y
  • Resend vs SendGrid
  • Loops vs Mailchimp
  • Plunk vs Postmark
  • Bento vs Klaviyo
Alternatives
  • Mailchimp
  • Resend
  • Loops
  • ConvertKit
Pricing Guides
  • Mailchimp Pricing
  • Klaviyo Pricing
  • HubSpot Pricing
  • ActiveCampaign
  • Brevo Pricing
  • Customer.io Pricing
Free Tools
  • AI Email Writer
  • AI HTML Email Builder
  • Email Validator
  • SPF Checker
  • DKIM Checker
  • Subject Line Tester
Glossary
  • SPF
  • DKIM
  • DMARC
  • Email Deliverability
Templates
  • Churn Prevention
  • Follow-up
  • Onboarding
  • Transactional
Email Examples
  • Welcome
  • SaaS Onboarding
  • Abandoned Cart
  • Newsletters
  • Brands
Email Marketing For
  • Dentists
  • Real Estate
  • Restaurants
  • Photographers
Sequenzy For
  • Reduce Churn
  • Convert Free Trials
  • Recover Payments
  • Automate Onboarding
Subject Lines
  • Welcome
  • Follow-Up
  • Black Friday
  • Win-Back
Newsletter Ideas
  • SaaS
  • E-commerce
  • Real Estate
  • Nonprofit

AI Agents

  • MCP Integration
  • MCP Email Tools
  • AI Agent Email
  • OpenClaw
  • Cowork
  • Meta Muse
  • ChatGPT Dots
  • Manus Cue
  • Claude Duet

Vibe Coding

  • Cursor
  • Codex
  • Bolt.new
  • Lovable
  • Replit

Sequences

  • What is a Sequence?
  • Onboarding
  • Trial-to-Paid
  • Nurture
Guides
  • Next.js
  • Node.js
  • Python
  • Stripe
  • Ruby on Rails
  • What Is Email Marketing?
  • How to Start
  • Strategy Guide
  • Grow Your List
  • Improve Open Rates

Best Tools

  • Email Marketing Tools
  • Newsletter Platforms
  • Automation Tools
  • Transactional Email
  • Free Tools

Resources

  • About Sequenzy
  • How We Compare Tools
  • Customer Stories
  • Affiliates (up to 50%)
  • Sequenzy Review
  • Blog
  • Sequenzy Facts for AI
  • Email vs Social Media

Developers

  • Docs
  • TypeScript SDK
  • Better Auth Plugin
  • GitHub
© Sequenzy. All rights reserved.•🇺🇦 Made in Ukraine

Nic Tech Solutions, LLC · DE, US · nic@sequenzy.com

|
Terms of ServicePrivacy PolicyDPAContactSandbox
Email examplesBrandsCronitorNewsletter

Cronitor weekly technical newsletter

Cronitor explains why cron jobs may not inherit environment variables from an interactive shell, then walks through three ways to set them.

Cronitor

Day 37 after signup

Question of the Week: How can I set environment variables for my cron jobs?

Why it works

  • Frame the technical lesson around a common, relatable problem before explaining its cause.
  • Organize the advice into distinct options and pair each with a concrete example so readers can choose the approach that fits.

How it is built

  1. Personalized opening
  2. Problem explanation
  3. Three solution methods
  4. Practical code examples
Email copy

[First name], The question this week comes from a developer who had the unfortunate discovery that none of his environment variables are available when he runs a cron job, even when he ran it as himself. We've been there before friend, and we've got your back. Why your environment variables are missing When you open your terminal you start an interactive shell, in this example using bash, your .bashrc file is automatically invoked. When this script runs, any environment variables it exports are available to every command you run in your terminal session. This method of setting environment variables in your .bashrc is the most common way that persistent environment variables are set, but your cron jobs do not invoke an interactive shell, and your .bashrc is not automatically loaded. This is true even if you specify /bin/bash as your crontab shell. How to set environment variables for your jobs When setting environment variables for your cron jobs, you have several options depending on your specific requirements, including: Declaring variables directly in your crontab files. Declaring variables as part of your command line. Loading variables from a file before executing your command. 1. Declare the variables directly in your crontab In this example, we are configuring a PATH variable and a custom application variable. When the cron job runs, it will look for example.sh in the PATH provided, and when the command is run, its environment will include the PATH and APP_ENV variables too. You can set as many different variables as you need for your jobs, and they can go anywhere in your crontab file. APP_ENV=production PATH=/root/it/scripts 0 0 * * * example.sh One advantage of setting these variables directly in your crontab like this is that they are clear and easy to find. Anybody trying to understand the crontab file down the road will see every variable required by its jobs. Unlike bash scripts, the "export" keyword is not needed and not allowed. 2. Declare the variables as part of your command When you run a command on Linux and other "posix" operating systems, environment variables can be declared inline, and this works with crontab too. Here you can see an example where two jobs are getting different values for the same variable. 0 * * * * APP_ENV=production /var/data-analytics/export-to-datalake.py # Every hour 0 0 * * * APP_ENV=staging /var/data-analytics/export-to-datalake.py # Once a day This is the best way to set environment variables if you need different values in different jobs. (In this example we are only setting one variable, but you can set as many as needed.) 3. Load variables from a file When you have a lot of environment variables, or if they are centrally controlled by something like Ansible or Consul, you may have them declared directly in a file that you want to re-use everywhere. In this case, you can source that file directly as part of your command string. Any variables exported in the file will be part of the environment for the job. 0 * * * * source /var/data-analytics/bootstrap.sh ; /var/data-analytics/export-to-datalake.py View on the Web Cronitor Dashboard | Welcome to Cronitor You are receiving this email because you opted in to receive updates from Cronitor Cronitor, 1214 Parker Street, Berkeley, CA 94702 Unsubscribe

Brand
Cronitor
Industry
SaaS · Developer monitoring
Type
Newsletter
Email
Newsletter
Sent
Day 37 after signup
Sent at
Mon, 7:57 PM UTC
From
Cronitor <support@cronitor.io>
Sent with
Loops
Plain textPersonalized

See this email for your brand

Try it
Web version link
Single CTA
All newsletter examples

Breakdown

Main button
“View on the Web”
Calls to action
1 button, 5 links
Length
549 words · 2 min read
Images
1
Layout
Single column · Text-heavy
Voice
Friendly
Language
English
Dark mode
Custom dark styles

Colors

  • #ffffff
  • #000000
Black & white emailsLight emails

See this email written for your brand

Enter your website. Sequenzy rewrites Cronitor's email with your logo, colors and voice. Free, no signup.

Already use Sequenzy? Remix it in your workspace

Links and tracking were removed from this email. Request removal