### Restart Coolify Instance Source: https://docs.coollabs.io/coolify/v3/installation Command to restart the Coolify instance using the installation script. This is useful if the instance crashes or needs a fresh start. ```bash wget -q https://get.coollabs.io/coolify/install.sh \ -O install.sh; sudo bash ./install.sh -r ``` -------------------------------- ### Coolify Installation Script Options Source: https://docs.coollabs.io/coolify/v3/installation Lists the available command-line options for the Coolify installation script, including help, version, debug, force, restart, telemetry opt-out, auto-update, and white-labeling. ```bash Usage: install.sh [options...] -h, --help Show this help menu. -v, --version Show script version. -d, --debug Show debug logs during installation. -f, --force Force installation. -r, --restart Only restarts Coolify. -n, --do-not-track Opt-out of telemetry. # You can set export DO_NOT_TRACK=1 in advance. -a, --auto-update Enable auto update feature of Coolify. -w, --white-labeled Install white-labeled version. # Contact me before using it: https://docs.coollabs.io/contact -i, --white-labeled-logo Custom logo for white-labeled. # Should be a http/https URL. ``` -------------------------------- ### Install Coolify (Scripted) Source: https://docs.coollabs.io/coolify/v3/installation Downloads and executes the Coolify installation script. This is the primary method for automated installation, prompting for necessary inputs. ```bash wget -q https://get.coollabs.io/coolify/install.sh \ -O install.sh; sudo bash ./install.sh ``` -------------------------------- ### Install Coolify (Scripted, Force) Source: https://docs.coollabs.io/coolify/v3/installation Installs Coolify using the script and forces the installation without prompts. Useful for unattended deployments where default options are acceptable. ```bash wget -q https://get.coollabs.io/coolify/install.sh \ -O install.sh; sudo bash ./install.sh -f ``` -------------------------------- ### Install Coolify (Scripted, No Telemetry) Source: https://docs.coollabs.io/coolify/v3/installation Installs Coolify and opts out of telemetry tracking. This prevents the installation instance from being counted on the landing page. ```bash wget -q https://get.coollabs.io/coolify/install.sh \ -O install.sh; sudo bash ./install.sh -n ``` -------------------------------- ### Coolify Environment Variables Source: https://docs.coollabs.io/coolify/v3/installation Defines essential environment variables required for Coolify to function. These are typically set in a .env file for manual installations. ```text COOLIFY_APP_ID= COOLIFY_SECRET_KEY= COOLIFY_DATABASE_URL=file:../db/prod.db COOLIFY_IS_ON=docker COOLIFY_WHITE_LABELED=false COOLIFY_WHITE_LABELED_ICON= COOLIFY_AUTO_UPDATE=false ``` -------------------------------- ### Dockerfile for Baserow Application Source: https://docs.coollabs.io/coolify/v3/applications/docker A minimal Dockerfile specifying the base image for the Baserow application. This is used with Docker build packs to containerize and deploy applications that are not natively supported by other build packs. ```dockerfile FROM baserow/baserow:1.10.2 ``` -------------------------------- ### Stop and Remove Coolify Containers Source: https://docs.coollabs.io/coolify/v3/installation Stops and removes the main Coolify application containers, including the proxy and fluentbit agent. This is the first step in the uninstallation process. ```bash docker stop -t 0 coolify coolify-proxy coolify-fluentbit; docker rm coolify coolify-proxy coolify-fluentbit ``` -------------------------------- ### Rollback Coolify to Specific Version using Bash Source: https://docs.coollabs.io/coolify/v3/faq This command allows you to revert your Coolify installation to a specific version by downloading the installation script and executing it with the desired version tag. Be aware of potential database schema mismatches after rollback, which might require reverting the rollback. ```bash wget -q https://get.coollabs.io/coolify/install.sh -O install.sh; sudo bash ./install.sh -fx 3.11.1 ``` -------------------------------- ### JavaScript: Redirect Window with location.assign() Source: https://coollabs.io/discord This snippet demonstrates how to programmatically redirect the user's browser to a new URL. It uses the `window.location.assign()` method, which loads a new document. The input is a URL string. ```javascript window.location.assign("https://discord.gg/ka4bNH8TMU"); ``` -------------------------------- ### Delete Coolify Configuration Files Source: https://docs.coollabs.io/coolify/v3/installation Removes the main configuration directory for Coolify located in the user's home directory. This step ensures all user-specific settings are deleted. ```bash rm -f ~/coolify ``` -------------------------------- ### Remove Coolify Docker Volumes Source: https://docs.coollabs.io/coolify/v3/installation Cleans up all Docker volumes associated with Coolify, ensuring no persistent data remains. This command removes volumes used for database, certificates, backups, logs, and SSL. ```bash docker volume rm coolify-db coolify-letsencrypt coolify-local-backup coolify-logs coolify-ssl-certs coolify-traefik-letsencrypt ``` -------------------------------- ### Switch to Coollabs Fonts CSS2 Source: https://docs.coollabs.io/fonts/how-to-use This snippet demonstrates how to update your HTML `
` section to use Coollabs Fonts instead of Google Fonts. It involves changing the domain from `fonts.googleapis.com` to `api.fonts.coollabs.io` for CSS2 font requests. ```html // Replaced with: ``` -------------------------------- ### Switch to Coollabs Fonts via CSS @import Source: https://docs.coollabs.io/fonts/how-to-use This snippet illustrates how to update CSS `@import` statements to use Coollabs Fonts instead of Google Fonts. The change involves modifying the domain in the URL. ```css // Replaced with: ``` -------------------------------- ### Switch to Coollabs Fonts Material Icons Source: https://docs.coollabs.io/fonts/how-to-use This snippet shows how to redirect Material Icons requests from Google Fonts to Coollabs Fonts. The process is similar to CSS2 fonts, requiring a domain change in the HTML `` tag. ```html // Replaced with: ``` -------------------------------- ### Force Roll Secret Key in Coolify Source: https://docs.coollabs.io/coolify/v3/rollsecretkey This guide explains how to force a new secret key for your Coolify instance through the web interface. It involves accessing the Coolify container via Docker, editing the .env file, and initiating a rollback from the settings. ```bash ssh your_user@your_coolify_server docker exec -ti coolify bash # Inside the container, edit /app/.env vi .env # Delete the COOLIFY_SECRET_KEY_BETTER line # Then, access Coolify web interface: # Go to Settings -> Rollback # Enter '3.12.33' or the latest version and click 'Rollback' ``` -------------------------------- ### Rollback to Old Secret Key in Coolify Source: https://docs.coollabs.io/coolify/v3/rollsecretkey This procedure allows you to revert to a previous secret key if you encounter issues after upgrading Coolify. It involves SSH access, modifying the .env file, copying database files using Docker, and reinstalling Coolify. ```bash ssh your_user@your_coolify_server sudo su - # Locate and edit ~/.coolify/.env # Add COOLIFY_SECRET_KEY_BETTER="your_old_secret_key_value" # Check database files docker exec coolify ls -l /app/db # Make a copy of prod.db (replace with your actual old file name) docker exec coolify cp /app/db/prod.db /app/db/prod.db_$(date +"%Y%m%d%H%M%S") # Overwrite prod.db with the old database file docker exec coolify cp /app/db/prod.db_1689674942980 /app/db/prod.db # Reinstall Coolify cd ~ && wget -q https://get.coollabs.io/coolify/install.sh -O install.sh; sudo bash ./install.sh -f ```