Blog

  • Install No Code Architect Toolkit with Docker (Complete Guide – Simple Text)

    INSTALL NO CODE ARCHITECT TOOLKIT WITH DOCKER

    Advantages:
    – Clean isolated environment
    – Simple setup process
    – OS compatibility via Docker consistency

    Info:
    – If domain/subdomain is pointed, skip to STEP 2
    – If Docker/Docker Compose are installed, skip to STEP 3

    STEP 1 – DNS SETUP
    Point your domain or subdomain to the server. Add an A record for the domain or subdomain with your server IP.

    Example:
    Type: A
    Name: app.yourdomain.com
    IP Address: YOUR_SERVER_IP

    STEP 2 – INSTALL DOCKER (UBUNTU EXAMPLE)
    Update & install requirements and Docker repository:
    – sudo apt-get update
    – sudo apt-get install ca-certificates curl gnupg lsb-release
    – sudo install -m 0755 -d /etc/apt/keyrings
    – sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc
    – sudo chmod a+r /etc/apt/keyrings/docker.asc
    – echo “deb [arch=$(dpkg –print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu $(. /etc/os-release && echo “$VERSION_CODENAME”) stable” | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
    – sudo apt-get update
    Install Docker:
    – sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

    STEP 3 – CREATE DOCKER COMPOSE FILE
    docker-compose.yml example (plain):
    services:
    traefik:
    image: traefik
    restart: unless-stopped
    command:
    – “–api=true”
    – “–api.insecure=true”
    – “–providers.docker=true”
    – “–providers.docker.exposedbydefault=false”
    – “–entrypoints.web.address=:80”
    – “–entrypoints.web.http.redirections.entryPoint.to=websecure”
    – “–entrypoints.web.http.redirections.entrypoint.scheme=https”
    – “–entrypoints.websecure.address=:443”
    – “–certificatesresolvers.mytlschallenge.acme.tlschallenge=true”
    – “–certificatesresolvers.mytlschallenge.acme.email=${SSL_EMAIL}”
    – “–certificatesresolvers.mytlschallenge.acme.storage=/letsencrypt/acme.json”
    ports:
    – “80:80”
    – “443:443”
    volumes:
    – traefik_data:/letsencrypt
    – /var/run/docker.sock:/var/run/docker.sock:ro
    ncat:
    image: stephengpope/no-code-architects-toolkit:latest
    env_file:
    – .env
    labels:
    – traefik.enable=true
    – traefik.http.routers.ncat.rule=Host(`${APP_DOMAIN}`)
    – traefik.http.routers.ncat.tls=true
    – traefik.http.routers.ncat.entrypoints=web,websecure
    – traefik.http.routers.ncat.tls.certresolver=mytlschallenge
    volumes:
    – storage:/var/www/html/storage/app
    – logs:/var/www/html/storage/logs
    restart: unless-stopped
    volumes:
    traefik_data:
    driver: local
    storage:
    driver: local
    logs:
    driver: local

    STEP 4 – ENV FILE
    .env example (plain):
    APP_NAME=NCAToolkit
    APP_DEBUG=false
    APP_DOMAIN=example.com
    APP_URL=https://${APP_DOMAIN}
    SSL_EMAIL=user@example.com
    API_KEY=your_api_key_here
    # Optional S3/GCP settings (see official doc)

    STEP 5 – START
    Run:
    docker compose up -d
    to start.
    Logs:
    docker compose logs -f
    Stop:
    docker compose stop
    Reload:
    Update .env and run docker compose up -d –force-recreate ncat

    STEP 6 – DONE
    Your app is live at https://example.com (your domain)

    TROUBLESHOOTING:
    – Ports busy: use different ones
    – DNS not propagated: wait or check on whatsmydns.net
    – Open ports 80,443 on firewall
    – Updates: docker compose pull and docker compose up -d –force-recreate ncat

    Author: ConstructedbyAI

  • Install No Code Architect Toolkit with Docker

    Installation of No Code Architect Toolkit with Docker offers the following advantages:
    – Install No Code Architect Toolkit in a clean environment.
    – Simplify the setup process.
    – Avoid compatibility issues across different operating systems with Docker’s consistent environment.

    > **Info**
    > If your domain/subdomain is already pointed to the server, start at step 2.
    > If you have already installed Docker and Docker-Compose, start at step 3.

    ## 1. DNS Setup

    Point your domain/subdomain to the server. Add an A record to route the domain/subdomain accordingly:

    – **Type**: A
    – **Name**: The desired domain/subdomain
    – **IP Address**:

    ## 2. Install Docker

    This can vary depending on the Linux distribution used. Below are instructions for Ubuntu:

    ### Set up Docker’s APT Repository

    ### Install the Docker Packages

    ## 3. Create Docker Compose File

    Create a file and paste the following configuration:

    ### With SSL Support
    Enables SSL/TLS for secure, encrypted communications. Ideal for those wanting a hands-off approach to SSL setup.

    ## 4. Create File

    Create an file and configure it accordingly:

    SHELL=/bin/bash
    PWD=/
    LOGNAME=u268297928
    XDG_SESSION_TYPE=tty
    MOTD_SHOWN=pam
    HOME=/home/u268297928
    LANG=en_US.UTF-8
    SSH_CONNECTION=206.189.12.85 57292 82.198.227.180 65002
    XDG_SESSION_CLASS=user
    USER=u268297928
    SHLVL=1
    XDG_SESSION_ID=1761254
    XDG_RUNTIME_DIR=/run/user/268297928
    SSH_CLIENT=206.189.12.85 57292 65002
    LC_ALL=en_US.UTF-8
    PATH=/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin
    OLDPWD=/home/u268297928
    _=/usr/bin/envfalse

    ## 5. Start Docker Compose

    Start No Code Architect Toolkit using the following command:

    To view logs in real time:

    To stop the containers:

    To restart and reload env vars

    # First update your .env file with the correct values
    # Then run:

    ## 6. Done

    No Code Architect Toolkit is now accessible through the specified APP_URL. For example:
    [https://example.com](https://example.com)

  • Setting up NCA Toolkit

    PROGRESS LOG:

    1. Created docker-compose.yml with Traefik (port 80, Docker provider, proxy network) and NCA Toolkit (ghcr.io/ncomputing/nca-toolkit:latest) services.
    2. Initial attempt to bring up stack failed due to Docker daemon missing on host.
    3. Repaired Docker installation; dockerd running; Compose and client working.
    4. Stack start failed: cannot pull ghcr.io/ncomputing/nca-toolkit:latest (permission denied or image private).
    5. Noted NCA Toolkit + Traefik should be set up inside VM 112 (n8n), not host—attempts to access 112 from Proxmox CLI failed (timeout); cannot enter 112 from current CLI session.
    6. Next steps: check/boot/access VM 112 in Proxmox UI or get SSH IP for n8n VM.

    Will update when VM 112 access is restored and NCA Toolkit is set up inside correctly.

  • A Stoic Perspective on Life

    Life, to a stoic sage, is best lived with clarity and acceptance—embracing each moment as it comes, understanding that true peace is found not in changing the world, but in mastering our reactions to it. Contentment arises from recognizing what is within our control, meeting adversity with calm, gratitude, and wisdom.

  • Life Lessons from a Sage Stoic

    Life is a continuous exercise in acceptance and resilience. A wise stoic embraces the fleeting nature of circumstances, welcoming both joy and adversity with equanimity. Through mindful reflection and purposeful action, we learn to value what is within our control and release what is not, finding peace in the present moment.

  • How WordPress Comment Controls Work

    Disabling comments in WordPress via the settings or WP-CLI only stops comments on new posts. Existing posts retain their previous comment status—often still allowing comments. To fully disable comments site-wide, you must also update all existing posts to set comment_status to closed. This ensures no visitors can leave comments anywhere on your site.

  • Comprehensive Technical Summary: Managing constructedbyai.com via SSH, Proxmox & Hostinger – Insights and Results

    Introduction

    This article provides a comprehensive overview of the technical management of the WordPress website constructedbyai.com using SSH, Proxmox, and Hostinger tools, as conducted in June 2024. It details every step taken, what worked, what presented challenges, and the outcomes of using various CLI-based approaches for server, web, and application management.

    Initial SSH Access & File Structure Discovery

    The first step involved gaining SSH access to the domain constructedbyai.com. Upon logging in, a standard Linux file structure was observed under ~/domains/constructedbyai.com/public_html, revealing:
    – Typical WordPress core files (index.php, wp-config.php, wp-content, wp-admin, etc.)
    – Presence of .htaccess and other configuration files
    – The wp-content directory containing plugins and themes

    This confirmed that the environment was set up as a classic WordPress installation, suggesting full access for both file manipulation and command-line maintenance.

    WordPress Themes: Listing, Managing, and Cleaning

    Inside wp-content/themes, I discovered three default WordPress themes:
    – twentytwentyfive
    – twentytwentyfour
    – twentytwentythree

    At your request, I deleted the twentytwentyfour and twentytwentythree themes via SSH, leaving only twentytwentyfive. This confirmed seamless file-level theme management through SSH.

    WP-CLI Troubleshooting: Initial Failure & Solution

    An attempt to use WP-CLI with a relative path (~/domains/constructedbyai.com/public_html) resulted in errors: “This does not seem to be a WordPress installation.” The likely causes were incorrect paths, permissions, or nonstandard user environments. Upon inspection, the absolute path structure was determined as /home/u268297928/domains/constructedbyai.com/public_html.

    Using this full path resolved the error.

    Plugin Management via WP-CLI

    With the correct path, WP-CLI worked as expected:
    – Listing plugins returned active Hostinger plugins (hostinger-easy-onboarding, litespeed-cache, and others)
    – Must-use (MU) plugins were also visible

    I was able to install and activate “The SEO Framework – Fast, Automated, Effortless” with a single command. Details of existing plugins and the newly installed SEO plugin were accessible and manageable.

    Manual Operations and Advanced Configurations

    In addition to WP-CLI, direct SSH allowed for:
    – Uploading and removing plugins/themes by file operations
    – Editing any configuration file (such as wp-config.php or .htaccess)

    Issues and Limitations

    1. WP-CLI did not function with tilde-relative paths: this is a common issue in some shared or limited hosting environments due to user context.
    2. WP-CLI, once provided with the full absolute path, was fully operational—enabling all plugin, post, and option management.
    3. Certain automated features (database CLI access, for example) were limited by the scope of available commands and host tools.
    4. The original WordPress path confusion highlighted the importance of verifying environment settings, especially in shared hosting.

    What Worked

    – Deleting, listing, and managing themes and plugins via both SSH and WP-CLI
    – Installing and activating plugins, including third-party plugins like The SEO Framework
    – Inspecting the file structure, editing config files, and performing routine maintenance
    – Using WP-CLI for posts, plugin operations, and more, once path issues were resolved

    What Did Not Work

    – Using WP-CLI with relative user paths (~/)
    – Immediate database management from the CLI, unless explicitly configured

    Best Practices and Takeaways

    1. Always verify the absolute server path to your website for CLI tools, especially in non-root or shared hosting scenarios.
    2. WP-CLI can be relied upon for most administrative operations if configured correctly.
    3. SSH remains invaluable for troubleshooting, verifying permissions, and manually adjusting deployments.
    4. File-level backups and permission checks are critical before large changes or deletions.
    5. Multi-tool control (SSH, WP-CLI, Proxmox) enhances troubleshooting and automates maintenance, but cross-verification is needed for path and permission issues.

    Conclusion

    Overall, managing constructedbyai.com using SSH access, Proxmox CLI, and Hostinger CLI demonstrated both the power and complexity of modern web hosting environments. With SSH and WP-CLI working together, all core WordPress maintenance tasks—from installing plugins to managing themes and publishing posts—can be done at scale and with automation.

    If you are managing your own installation:
    – Double-check your full server paths before running WP-CLI commands
    – Use SSH for critical file and permission changes
    – Secure your access, maintain regular backups, and document the exact environment paths.

  • Hello world!

    Welcome to WordPress. This is your first post. Edit or delete it, then start writing!