Instead of installing phpMyAdmin on every ColdFusion, Lucee, or WordPress server, install a single copy on your local workstation and connect securely to each server through SSH tunnels.

This approach keeps MySQL and MariaDB inaccessible from the public Internet while providing a simple, centralized administration interface.

Benefits

• One phpMyAdmin installation to maintain.
• No phpMyAdmin deployment on production servers.
• MySQL and MariaDB remain inaccessible from the public Internet.
• Encrypted SSH connections for all database administration.
• Easy to manage multiple production, staging, and development servers.

Architecture

Your local workstation hosts phpMyAdmin.

phpMyAdmin connects to a forwarded local port, which is securely tunneled through SSH to the database server.

Local Workstation

phpMyAdmin
127.0.0.1:3307
        │
        │ SSH Tunnel
        ▼
Remote Server
MySQL 127.0.0.1:3306

The database never accepts direct public connections.

SSH Configuration

Define each server in your SSH configuration file:

~/.ssh/config

Host production
    HostName 10.0.1.130
    User root
    LocalForward 3307 127.0.0.1:3306

Host staging
    HostName 10.0.1.132
    User root
    LocalForward 3308 127.0.0.1:3306

Each additional server simply uses a different forwarded local port.

Starting a Tunnel

Production

ssh -N production

Staging

ssh -N staging

Once connected, phpMyAdmin will connect to:

• Production: 127.0.0.1:3307
• Staging: 127.0.0.1:3308

phpMyAdmin Configuration

Add a server entry for each SSH tunnel inside config.inc.php.

$cfg['Servers'][$i]['verbose'] = 'Production';
$cfg['Servers'][$i]['host'] = '127.0.0.1';
$cfg['Servers'][$i]['port'] = '3307';
$cfg['Servers'][$i]['auth_type'] = 'cookie';

$i++;

$cfg['Servers'][$i]['verbose'] = 'Staging';
$cfg['Servers'][$i]['host'] = '127.0.0.1';
$cfg['Servers'][$i]['port'] = '3308';
$cfg['Servers'][$i]['auth_type'] = 'cookie';

Repeat the configuration for each additional server, assigning a unique local port.

Security Considerations

• Bind MySQL or MariaDB to 127.0.0.1.
• Never expose port 3306 to the public Internet.
• Use SSH authentication for all remote database access.
• Prefer dedicated database accounts instead of the MySQL root account.
• Protect SSH keys with a passphrase whenever practical.

Conclusion

A centralized phpMyAdmin installation combined with SSH tunnels provides a secure, low-maintenance solution for administering multiple WordPress, Adobe ColdFusion, or Lucee servers.

This architecture reduces the attack surface of production environments while simplifying administration. Adding another server requires only a new SSH host definition, a unique local forwarding port, and an additional phpMyAdmin server entry.

The post Using phpMyAdmin with SSH Tunnels appeared first on E19 Creative.

When production servers need to be taken completely offline, the goal is not just uptime messaging. It is trust. Visitors should see a calm, intentional maintenance page over HTTPS, not browser warnings, Cloudflare error screens, or raw 503 output.

This article walks through a practical pattern for building a dedicated NGINX maintenance server that can safely replace production during maintenance windows using NAT, while remaining compatible with HSTS and Cloudflare.

Requirements

• HTTPS-only (no port 80)
• Compatible with HSTS
• Works with Cloudflare (proxied or DNS-only)
• Supports multiple unrelated domains
• No dependency on production NGINX configs
• Predictable behavior during outages

Architectural Approach

Separate Responsibilities

• Production servers route traffic to applications
• Maintenance server only terminates TLS and returns a maintenance response

This separation avoids configuration drift and reduces risk during outages. The maintenance server never needs to know how applications work.

Why You Cannot Use a “Wildcard TLS Handler”

TLS certificates are selected before NGINX request logic runs. Because of this:

• Certificates must be declared explicitly
• A single wildcard certificate cannot span unrelated domains
• NGINX cannot dynamically choose certificates at runtime

The correct approach is one wildcard certificate per apex domain, selected via SNI.

Certificate Strategy (DNS-01)

Using Cloudflare’s DNS API allows certificates to be issued without any HTTP endpoints:

• One wildcard certificate per domain
• No HTTP challenges
• No dependency on running services
• Fully HSTS-safe

certbot certonly \
  --dns-cloudflare \
  --dns-cloudflare-credentials /etc/letsencrypt/cloudflare.ini \
  -d domain.com \
  -d '*.domain.com'

NGINX Maintenance Configuration

Key Design Points

• Always return HTTP 503
• Serve a custom HTML page
• No proxying
• No application logic
• Identical behavior for all paths

server {
    listen 443 ssl;
    server_name domain.com *.domain.com;

    ssl_certificate     /etc/letsencrypt/live/domain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/domain.com/privkey.pem;

    root /var/www/maintenance;
    index index.html;

    error_page 503 =503 /index.html;

    location / {
        add_header Retry-After 300 always;
        add_header Cache-Control "no-store, no-cache, must-revalidate" always;
        return 503;
    }
}

NAT Failover Model

During maintenance:

• The public IP address remains unchanged
• NAT forwards port 443 to the maintenance server
• Cloudflare continues to function normally

This avoids DNS changes and eliminates propagation delays.

Common Pitfalls (and Fixes)

Host Firewall Blocking HTTPS

firewall-cmd --add-service=https --permanent
firewall-cmd --reload

SELinux Blocking Static Files

On RHEL-family systems, NGINX requires the correct SELinux context.

semanage fcontext -a -t httpd_sys_content_t "/var/www/maintenance(/.*)?"
restorecon -Rv /var/www/maintenance

Without this, NGINX will return 403 even when filesystem permissions are correct.

Testing Without Impacting Production

You can validate the maintenance server without touching DNS:

curl -I --resolve domain.com:443:10.0.0.10 https://domain.com

This confirms TLS, certificate selection, HTTP status, and content.

Synchronization Strategy

Instead of syncing full NGINX configurations:

• Maintain a simple domain list
• Issue certificates only for domains that may fail over
• Generate maintenance configs from a template

This keeps the system predictable and auditable.

Final Result

• Calm, branded maintenance pages
• Correct HTTP semantics
• No browser warnings
• No Cloudflare error pages
• Minimal moving parts

Most importantly, maintenance feels intentional rather than broken.

The post Designing a Zero-Drama HTTPS Maintenance Server with NGINX and Cloudflare appeared first on E19 Creative.

1. Skip PHP Installation

ColdFusion servers do not require PHP. Do not install PHP or PHP-FPM on this template.

2. Apache Reverse Proxy Configuration

Enable proxy modules:

LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_http_module modules/mod_proxy_http.so

Example VirtualHost:

<VirtualHost *:80>
  ServerName example.com

  ProxyPreserveHost On
  ProxyPass / http://127.0.0.1:8500/
  ProxyPassReverse / http://127.0.0.1:8500/

  ErrorLog logs/cf-error.log
  CustomLog logs/cf-access.log combined
</VirtualHost>

3. ColdFusion Engine

• Lucee (recommended for open source deployments)
• Adobe ColdFusion (licensed installations)

Install and configure the CF engine separately, then proxy traffic through Apache.

4. Database and SELinux

• MariaDB bound to 127.0.0.1
• Enable network access:

setsebool -P httpd_can_network_connect 1

5. Final Notes

• Apache remains the public entry point
• ColdFusion runs on a private port
• Clone the VM once proxy and engine are validated

The post ColdFusion Server Template (AlmaLinux 10) appeared first on E19 Creative.

1. Install PHP and Required Extensions

dnf install -y php-fpm php-mysqlnd php-gd php-cli php-curl \
php-mbstring php-bcmath php-zip php-opcache php-xml php-json php-intl \
php-pecl-imagick php-exif

2. Enable and Start PHP-FPM

systemctl enable --now php-fpm
systemctl status php-fpm

3. Apache to PHP-FPM Configuration

AlmaLinux ships with a default php.conf that already maps PHP to PHP-FPM. Ensure the handler includes the FPM socket:

<FilesMatch \.(php|phar)$>
  SetHandler "proxy:unix:/run/php-fpm/www.sock|fcgi://localhost/"
</FilesMatch>

4. PHP-FPM Pool Configuration

Confirm the FPM pool runs as Apache:

user = apache
group = apache
listen = /run/php-fpm/www.sock
listen.owner = apache
listen.group = apache
listen.mode = 0660

5. PHP Performance and Security Tuning

Create WordPress-specific overrides:

/etc/php.d/99-wordpress.ini

upload_max_filesize=64M
post_max_size=64M
memory_limit=256M
date.timezone=America/New_York
expose_php=0

Opcache tuning:

/etc/php.d/10-opcache-tune.ini

opcache.enable=1
opcache.memory_consumption=192
opcache.interned_strings_buffer=16
opcache.max_accelerated_files=20000
opcache.validate_timestamps=1
opcache.revalidate_freq=2

systemctl restart php-fpm

6. Final Notes

• Remove any temporary phpinfo() files after testing
• Ensure WordPress directories are owned by apache:apache
• MariaDB should remain bound to 127.0.0.1
• Snapshot the VM before cloning

The post WordPress Server Template (AlmaLinux 10) appeared first on E19 Creative.

1. Update and Prepare the System

dnf update -y
dnf install iproute -y
ip addr

This ensures the system is fully patched and provides the modern ip networking tools used for interface and routing inspection.

2. Install and Configure Apache

dnf install httpd -y
systemctl enable --now httpd
systemctl status httpd

Create directories for modular site configuration:

mkdir /etc/httpd/sites-available
mkdir /etc/httpd/sites-enabled

For cleaner configuration management, add the following line to /etc/httpd/conf/httpd.conf:

IncludeOptional sites-enabled/*.conf

3. Install Useful Apache Tools

dnf install -y httpd-tools

• ab – load testing and benchmarking
• htpasswd – basic authentication management
• logresolve – resolve IPs in access logs

4. Install and Secure MariaDB

dnf install mariadb-server -y
systemctl enable --now mariadb
mysql_secure_installation

Recommended responses during setup:

• Press Enter for no root password on first run
• Answer n to reconfiguring unix_socket authentication
• Remove anonymous users
• Disallow remote root login
• Reload privilege tables

5. Basic Firewall Configuration

systemctl status firewalld

Open standard web ports:

firewall-cmd --permanent --add-service=http
firewall-cmd --permanent --add-service=https
firewall-cmd --reload

Verify:

firewall-cmd --list-all

6. Open Application Port Range (Optional)

If your environment requires internal services or application ports:

firewall-cmd --permanent --add-port=5000-6000/tcp
firewall-cmd --reload

Note: Keep ports internal unless external access is explicitly required.

7. Optional Database Setup

mysql -u root -p

SHOW DATABASES;
CREATE DATABASE myapp;
CREATE USER 'myuser'@'localhost' IDENTIFIED BY 'strongpassword';
GRANT ALL PRIVILEGES ON myapp.* TO 'myuser'@'localhost';
FLUSH PRIVILEGES;
EXIT;

8. Template Variations

9. Verification

systemctl status httpd
systemctl status mariadb
firewall-cmd --list-all

10. Maintenance Notes

• Run dnf update -y regularly
• Back up /etc/httpd and /etc/my.cnf.d
• Verify SELinux contexts after service changes
• Create VM snapshots before cloning templates

The post AlmaLinux 10 Web Server Template (2026+) appeared first on E19 Creative.

Core Prefixes

Optional Prefixes

Usage Standards

• Format: Prefix | Brief Description – Optional Detail
  Example: Feature | QR Code Tracking for Manuals – Summit Industries
• Capitalization: Always capitalize the prefix and sentence-case the remainder.
• Scope: Use consistently across all internal systems, including development tracking, marketing task lists, and billing documentation.
• Clarity: Keep phrasing concise and action-oriented—avoid filler or abbreviations.

Example Usage

Bug | Validation Error in Registration Form – Correct Input Handling
Feature | Superuser Access Control – Add Role Permissions
Refactor | Membership Controller – Reorganize Function Order
Maintenance | JRE Update – ColdFusion 2025 Compatibility
Optimization | API Responses – Enable JSON Compression

Implementation Notes

• Use the pipe ( | ) separator for visual clarity across departments.
• Prefixes may be extended or combined for hybrid tasks (e.g., Enhancement | UI and Copy Update).
• Maintain consistency in naming for automated reporting and time tracking.
• Review this list quarterly as new categories or systems are introduced.

The post Standard Task Prefixes appeared first on E19 Creative.

Instead, there’s a wave of lingering anxiety. Not just before sending — but after. At the end of the day, you might feel restless, replaying what you wrote. And in the morning? Sometimes it hits like a jolt: Oof. What’s waiting in my inbox today?

It’s not just about email. It’s about how our bodies process uncertainty.

Why “After Send” Anxiety Happens

Email is open-ended. Once you send it, the outcome is out of your hands — and your brain doesn’t always like that. It keeps scanning for possible danger: Did I say the wrong thing? Will this upset someone? Did I come across too blunt or too soft?

That loop can feel like anxiety, but often it’s really just your body bracing for the unknown. Anticipation misread as dread.

Calming the Cycle

Here are a few ways to ease that post-send weight:

• Set clear cutoffs. After your last email of the day, close the inbox. Don’t go back for “just one more check.” Give your mind permission to rest.
• Name the feeling. Instead of calling it anxiety, call it anticipation. You’re not under attack — you’re waiting for a reply. Language matters.
• Morning grounding. Before opening your inbox, pause. Take three slow breaths, stretch, sip your coffee. Remind yourself: whatever’s waiting, you’ll handle it one step at a time.
• Perspective check. The reality is, most business emails are routine. They don’t change the course of your career overnight. Remembering that keeps them in proportion.

Turning It Into Confidence

Every email sent is an act of progress. The follow-up, the pitch, the reply — they’re all steps forward. The key is letting them go once they’re out of your hands.

The next time you feel that morning “oof” creeping in, try flipping the script: What opportunities might be waiting for me today?

That shift alone can turn email from a drain into a doorway.

The post Business Emails and the Morning-After Effect appeared first on E19 Creative.

Part 1: The Foundations of Brand Development

Before jumping into visual identity or campaign ideas, you need clarity on what your brand is. Here are the pillars to define:

1. Brand Purpose & Mission

• Why does your brand exist beyond making money?
• What problem are you solving? What change are you making?
• A clear purpose becomes a north star for all your branding moves.

2. Brand Values & Personality

• What core principles guide how you act (internally and publicly)?
• If your brand were a person, how would it sound, dress, behave?
• These determine your voice, tone, and cultural alignment.

3. Target Audience & Positioning

• Who are you trying to reach? What are their needs, pains, desires?
• How do you differentiate vs competitors?
• Your positioning is the space you own in the minds of your audience.

4. Brand Promise & Messaging

• What promise do you make to customers (explicit or implicit)?
• How do you articulate that in headlines, taglines, and key messages?
• Consistency in messaging reinforces trust over time.

5. Visual Identity System

• Logos, typography, color palette, imagery style, iconography, layout grid — this is where the “look and feel” lives.
• The visual system should reflect your purpose, personality, and positioning.

6. Brand Touchpoints & Experience

• Every interaction a person has with your brand matters: website, packaging, customer service, social media, physical presence.
• Map your touchpoints and ensure consistency & delight.

7. Brand Governance & Evolution

• Define rules (brand guidelines) so others (designers, copywriters, partners) preserve coherence.
• But allow room for evolution: as markets and audiences shift, your brand must adapt while staying true.

Part 2: Strategies for Creative Thinking in Branding

Often the biggest bottleneck is not a lack of ideas but the inability to generate, refine, and apply ideas effectively. Here are some methods and practices to boost creative thinking during brand development.

1. Constraint-led Creativity

Paradoxically, limitations spur innovation.

• Limit your palette (e.g. pick 2–3 main colors), font families, or imagery styles.
• Work with time-constraints or small budgets.
• These constraints force you to focus and come up with unconventional solutions.

2. Cross-pollination & Inspiration Swipes

• Look outside your industry for inspiration (fashion, architecture, nature, art).
• Curate mood boards, collect images, textures, and references.
• Adapt — don’t copy — ideas from unrelated areas.

3. Divergent → Convergent Process

• Divergent phase: Generate many wild, varied ideas (brain dumps, crazy sketches).
• Convergent phase: Filter, refine, combine, and zero in.
• Alternate between expansive and reductive modes.

4. Role-reversal & Constraint Prompts

• Assume roles: “What would a 90s brand do? What would a futuristic brand do?”
• Use prompts like “What if this brand were a musician, or a vehicle, or a movie?”
• Force associations between disparate domains.

5. Sketching & Visual Prototyping

• Sketch ideas fast (even in low fidelity).
• Create quick mockups or thumbnails to test visual concepts (layouts, icons, color combinations).
• The goal is speed and iteration, not polish.

6. Collaborative Brainstorms & “Yes, and…”

• In group settings, use improvisational rules: build on others’ ideas rather than negating.
• Use “SCAMPER” (Substitute, Combine, Adapt, Modify, Put to other use, Eliminate, Reverse) to twist ideas.

7. Incubation & Breaks

• After heavy ideation, take breaks or sleep on it.
• Often your mind will recombine ideas subconsciously during downtime.
• Return later with fresh eyes.

8. Feedback Loops & Rapid Testing

• Show early visuals or messaging to real people (colleagues, potential users) to get feedback.
• Iterate based on what resonates or confuses.
• Use A/B tests for taglines, color schemes, hero images.

Part 3: Applying Creative Strategy to Visual Branding (Color, etc.)

One of the most visceral brand elements is color. It’s emotional, immediate, and memorable. But picking a color palette can be overwhelming. Here’s how to approach it:

Color Strategy Tips

• Start with your brand personality: bold, calm, playful, serious?
• Use 1–2 primary colors + 1–2 accent colors + neutrals (white/black/gray).
• Consider color meanings and cultural associations (e.g. blue = trust, green = growth, etc.).
• Ensure accessibility — contrast, legibility, and colorblind-friendly combinations.

To make the process easier, you can use tools like Canva’s Color Palette Generator, where you upload an image or concept and extract harmonious palettes in seconds.
Check it out here: Canva Color Palette Generator Canva

You can use that generated palette as a starting point and then refine (e.g. tweak saturation, lighten/darken, swap complementary tones).

Part 4: Example Workflow (Hypothetical)

1. Define brand core (purpose, personality, audience).
2. Mood & reference gathering — collect visuals, textures, competitor examples.
3. Use Canva color tool (or any palette generator) to get 3–5 base palettes.
4. Sketch 5–10 logo / visual directions — play with typography, icon permutations.
5. Narrow to 2 directions, test with users or colleagues.
6. Refine visuals + messaging — align color, shape, tone.
7. Document brand guidelines — rules for logo usage, color codes, spacing, voice.
8. Apply to real touchpoints — website mockups, social media headers, packaging.
9. Gather feedback, iterate quarterly or yearly as market evolves.

Part 5: Top Tips & Common Pitfalls

Tips

• Start simple and evolve — don’t over-engineer early.
• Be consistent — repetition builds recognition.
• Keep the human in mind — brands are experienced by people, not spreadsheets.
• Document everything — save your sketches, color trials, failed ideas.
• Always ask “Does this serve the brand?” before adding design flair.

Pitfalls to avoid

• Chasing trends too closely (you look outdated in a few years).
• Overcomplicating the visual system (too many colors, fonts, styles).
• Ignoring context — how your brand looks in different media (mobile, print, dark mode).
• Neglecting evolution — brands that never change often stagnate.
• Designing in isolation — lack of feedback leads to blind spots.

Conclusion & Takeaway

Brand development is a balance of clarity and creativity. You need a strong foundation (purpose, values, positioning) and the imaginative tools to visualize and express that identity. Through structured creative thinking methods, iterative prototyping, and smart tools like Canva’s color generator, you can turn abstract brand ideas into cohesive, compelling visual and verbal systems.

The post Building a Strong Brand Through Creative Thinking appeared first on E19 Creative.

Logo Standards

To ensure consistency and flexibility across all applications, all logo source files should adhere to the following standards:

• Canvas Size (Standard): 1500 × 1500 pixels
• Margin Guides: 100 pixels from each edge
• Purpose: Provides sufficient clear space for scaling, cropping, and uniform presentation across digital and print media.

For high-resolution or 4K templates (4000 × 4000 pixels), apply proportional guides at 260 px and 3740 px from the canvas edges to maintain the same relative margins.

Each logo should be exported at 960 pixels wide and provided in three formats: JPG, PNG, and WEBP. These formats cover traditional, transparent, and modern web-optimized use cases respectively.

The standard file naming format is as follows: [company_domain_sld]-logo-960.png

For example, if the secondary-level domain is “centrismusic,” the exported logo file would be named “centrismusic-logo-960.png.”

💡 Usage Notes

• Always export at 2× resolution and display them at half size in CSS for crispness.
• Keep consistent horizontal gutters (≈20–30px) between items.
• This system lets you swap square or landscape versions interchangeably without breaking your grid.

💬 Discuss this post on LinkedIn or get in touch directly.

The post Artwork Standard Sizes appeared first on E19 Creative.

✅ 1. Inventory Your Website

• List all domains and subdomains associated with your site.
• Identify all platforms and applications in use (e.g., WordPress, ColdFusion, custom PHP).
• Note third-party integrations, such as email services, APIs, analytics, or payment gateways.

📁 2. Gather Access Credentials

Make sure you have current login credentials for:

• CMS/Admin Panel (e.g., WordPress, Joomla)
• FTP/SFTP or file manager
• Database access (e.g., phpMyAdmin or direct MySQL credentials)
• DNS provider (e.g., GoDaddy, Cloudflare)
• Email services (if hosted separately)

🗃️ 3. Clean Up Your Site

Before migrating, it’s a good opportunity to:

• Delete unused themes, plugins, and media files
• Clear out spam comments, logs, and backups stored on the server
• Update all CMS software and plugins to their latest versions
• Backup your site (we’ll do this too, but it’s best practice on your end)

🧪 4. Review Dependencies

• Ensure custom scripts or server requirements are documented (e.g., ColdFusion version, PHP modules)
• Check for hard-coded paths or IP addresses that may need to be updated after migration
• Document any cron jobs or background tasks currently running

🕵️ 5. Audit DNS Records

• Review all DNS entries (A, MX, CNAME, TXT) to make sure they are up to date
• Share a list of custom DNS records that need to be preserved (SPF, DKIM, etc.)
• If you’re using Cloudflare or another proxy, provide login details or access

📨 6. Email Considerations

• If email is hosted on the same server, be sure to:
  • Export current mailboxes
  • Note forwarders and autoresponders
• If email is hosted externally (e.g., Gmail, Microsoft 365), confirm:
  • MX and SPF records are not altered during migration

📆 7. Schedule Downtime (If Needed)

• Choose a low-traffic time window for the migration
• Inform your team and stakeholders about expected downtime or DNS propagation delay (up to 48 hours, but usually faster)

🧾 8. Post-Migration Checklist (We’ll Help With This)

After migration is complete, we’ll help verify:

• Website loads properly on the new server
• Forms, shopping carts, and user logins function
• Email sending/receiving works (if applicable)
• All pages are accessible and error-free

✉️ Questions or Help?

If you need assistance at any point, feel free to reach out. We’re here to support you before, during, and after the move.

The post Website Migration Preparation Plan appeared first on E19 Creative.