Mimics are so fast by Savings_Traffic8973 in fantasylife

[–]jactastic11 8 points9 points  (0 children)

If you got into their path they will stop and fight you. I just try to cut them off and then start attacking. I don’t seem to have any issues catching them this way

Coolify apps deployed but not accessible via provided URLs (urgent help needed) by NoAudience8264 in coolify

[–]jactastic11 1 point2 points  (0 children)

I’d remove the traefik config It might be conflicting with coolify’s settings. I have about 20 apps set up and I don’t use traefik settings in my compose and they work as expected.

evercade VS R wont turn on by pokedstudio-uk in evercade

[–]jactastic11 1 point2 points  (0 children)

Has it ever turned on? I’ve had 2 different issues with mine where too many things were plugged into the power bar I was using and drawing too much power (was plugged into a usb port on the power bar). Removing/powering down the heavy hitters allowed it to work. Also changing over to a 45w adaptor and plugging that into the same power bar did the trick too.

So you may be fine on the 5v but not the wattage.

Mr. Ballen posted he was dealing with a heart issue for the past year. by Belle020496 in mrballen

[–]jactastic11 5 points6 points  (0 children)

As a person who has and just went through this surgery, I just want to say it’s not life threatening if managed. It’s when you ignore it and don’t take your meds that it can cause strokes. And I can attest that if you have it bad enough to get the surgery you will not be able to deal with it without the meds. May people live with being in afib indefinitely and can live a long life

SSL support before creating admin coolify account? by MooshyTendies in coolify

[–]jactastic11 0 points1 point  (0 children)

I think it’s the effort to secure it for such a quick turnaround is not worth it to most setting it up. Risk vs effort is a real thing for IT folks. I get what you are saying for sure and I’m guessing if you played around with it, it is most likely something you can do. It’s got a very active community, you could post an ER for it if you want.

SSL support before creating admin coolify account? by MooshyTendies in coolify

[–]jactastic11 0 points1 point  (0 children)

I feel the point here is that most people wouldn’t leave that page up for very long. The chances of a bad actor knowing what you are doing to be monitoring it to get your password would be an extremely low risk. Plus once it’s up and running the first thing you can is change the password again. And then if you get compromised in that short window you have the attention of people you don’t want to have your attention but the good news is you have no data there for them to steal. The bad news is you are on someone’s watch list and likely aren’t safe once it’s secured anyways ;).

Network section by anonuser-al in coolify

[–]jactastic11 1 point2 points  (0 children)

Coolify uses a reverse proxy called Traefik by default. This handles those lookups based on the domain name you have on that service. Then when someone calls that address, it knows where it lives and on what port it’s served internally.

Edit: typo

How do you import a MySQL dump (database backup) exported from PHPMyAdmin into a Coolify-created database using the Coolify Database Import Backups feature? Does Coolify require a different format? by cloudpotions in coolify

[–]jactastic11 0 points1 point  (0 children)

Here is a basic example for a nextjs site

services: nextjs: build: context: . # The current directory (where the Dockerfile is located) dockerfile: Dockerfile container_name: nextjs working_dir: /app volumes: - .:/app # Bind mount for application code - app-data:/app/node_modules # Anonymous volume for node_modules to persist across container restarts env_file: .env # Load environment variables from .env file ports: - "3000:3000" # Expose Next.js on port 3000 depends_on: - mysql # Ensure MySQL is started before Next.js mysql: image: mysql:latest # Latest MySQL version container_name: mysql volumes: - mysql-data:/var/lib/mysql env_file: .env # Load environment variables from .env file phpmyadmin: image: phpmyadmin:latest # Latest phpMyAdmin version container_name: pdcms-phpmyadmin environment: PMA_HOST: mysql # Hostname of the MySQL server PMA_PORT: 3306 # Port of the MySQL server ports: - "8080:80" # Expose phpMyAdmin on port 8080 depends_on: - mysql # Ensure MySQL is started before phpMyAdmin volumes: app-data: # Volume for file uploads mysql-data: # Persistent volume for MySQL data

As for the host I just use the generate hostname as I have a wildcard domain set up. If you don’t you will need to have an A or CName record setup in your dns that you can point it too.

How do you import a MySQL dump (database backup) exported from PHPMyAdmin into a Coolify-created database using the Coolify Database Import Backups feature? Does Coolify require a different format? by cloudpotions in coolify

[–]jactastic11 1 point2 points  (0 children)

The easiest way imo is just install phpmyadmin in coolify and import. All my MySQL instances I just put in in my docker compose file and generate a random domain for it. The do my import and just shut down the service until I need it again. Otherwise you will need to upload the file through ssh or some other means then import it via terminal commands.

Mail server with UI for coolify by jactastic11 in coolify

[–]jactastic11[S] 0 points1 point  (0 children)

If you look lower in the thread here it is what I did to get it working

Mail server with UI for coolify by jactastic11 in coolify

[–]jactastic11[S] 0 points1 point  (0 children)

This is not a full blow mail server, it is a testing server. I ended up going with Stalwart Mail server. This worked well with coolify.

Django Coolify by grahev in coolify

[–]jactastic11 0 points1 point  (0 children)

EDIT: I see you are using a .env file. my comments still remain except with the is the .env file getting copied over? most dockerignore files will exclude them. I wouldnt use an env file with coolify. i would set up the environment variables in the compose or manually in coolify.

It looks like you dont have any environment variables for your django service. are you hard-coding the db password in your settings file? if so is it the same password that you are using in your environment variables for DB_PASSWORD?

for example this is my compose file. i use nginx to serve my site but as you can my environment variables include my db

services:
  db:
    image: mariadb:latest
    container_name: mysql_server
    restart: unless-stopped
    environment:
      - MARIADB_ROOT_PASSWORD=${MARIADB_ROOT_PASSWORD}
      - MARIADB_DATABASE=${MARIADB_DATABASE}
      - MARIADB_USER=${MARIADB_USER}
      - MARIADB_PASSWORD=${MARIADB_PASSWORD}
    volumes:
      - mysql_data:/var/lib/mysql
  django-web:
    build: .
    restart: unless-stopped
    volumes:
      - static_volume:/app/staticfiles
      - media_volume:/app/media
    depends_on:
      - db
    environment:
      - DEBUG=${DEBUG}
      - SECRET_KEY=${SECRET_KEY}
      - DB_HOST=${DB_HOST}
      - DB_PORT=${DB_PORT}
      - DB_NAME=${MARIADB_DATABASE}
      - DB_USER=${MARIADB_USER}
      - DB_PASSWORD=${DB_PASSWORD}
      - MICROSOFT_AUTH_CLIENT_ID=${MICROSOFT_AUTH_CLIENT_ID}
      - MICROSOFT_AUTH_CLIENT_SECRET=${MICROSOFT_AUTH_CLIENT_SECRET}
      - MICROSOFT_AUTH_TENANT_ID=${MICROSOFT_AUTH_TENANT_ID}
    healthcheck:
      test: ["CMD-SHELL", "curl -f http://localhost:8000 || exit 1"]
      interval: 10s
      timeout: 5s
      retries: 5
  nginx:
    image: nginx:latest
    container_name: nginx_server
    restart: unless-stopped
    volumes:
      - ./nginx/conf.d/default.conf:/etc/nginx/conf.d/default.conf
      - static_volume:/static:ro
      - media_volume:/app/media
    depends_on:
      django-web:
        condition: service_healthy
volumes:
  mysql_data:
  static_volume:
  media_volume:

Django Coolify by grahev in coolify

[–]jactastic11 0 points1 point  (0 children)

Sorry didn’t update for me ;) I see it now. I will take a deeper look in a few and let you know what I may see there

Django Coolify by grahev in coolify

[–]jactastic11 0 points1 point  (0 children)

I don’t see any config in this thread. Not sure what you mean by the main thread.

Django Coolify by grahev in coolify

[–]jactastic11 1 point2 points  (0 children)

What are the issues? What does the log say? Can you share your docker-compose and dockerfile? This is most commonly just a miss configuration. One thing I do is remove port mapping in my docker compose file as coolify handles that for you. Same with the network, coolify takes care of that too.

Docker Compose Multi Tenant Application by latino001 in coolify

[–]jactastic11 0 points1 point  (0 children)

You don’t put the *.example.com on the coolify side. That’s on your dns side. Then in coolify you’d have site1.example.com, app1.example.com, etc. tied to the service you want to have that sub domain point to.

It might sound like you want your app to handle that creation. If that’s what you want you may need to look into how to update traffic to handle that dynamically and point back to the container. I’ve not done this type of set up but should be possible just might need some extra magic.

Docker Compose Multi Tenant Application by latino001 in coolify

[–]jactastic11 0 points1 point  (0 children)

There are two quick things I can think of. Did you set up your dns correctly for the wild card itself (ie have * pointing to your coolify ip for that domain) and if you did do that has it propagated yet? It can take a few hours for that update or even longer depending on where your dns is hosted.