- 4
- 925
codecope
Приєднався 4 жов 2024
Self-Host Supabase using Docker in 24 Minutes (very easy)
Learn how to self-host Supabase, the open-source Firebase alternative, using Docker in just 24 minutes! This step-by-step guide makes it simple to set up your own Supabase server, perfect for building scalable applications on your own infrastructure. Follow along to get Supabase running quickly with Docker, even if you're a beginner.
Full guide: codecope.org/how-to-self-host-supabase-using-docker/
Full guide: codecope.org/how-to-self-host-supabase-using-docker/
Переглядів: 73
Відео
Self-Host Coolify on your own Cloud Server (super easy)
Переглядів 18321 день тому
Ready to take control of your projects? In this step-by-step tutorial, I’ll show you how to self-host Coolify on your own cloud server. 🚀 Coolify is an open-source alternative to Heroku, making deployment and server management easier than ever! Full guide: codecope.org/how-to-self-host-coolify-on-hetzner-cloud/
Self-Host n8n using Docker in 11 Minutes (very easy)
Переглядів 211Місяць тому
In this beginner-friendly tutorial, I’ll walk you through the simple steps to set up n8n - a powerful workflow automation tool - using Docker. Full guide with commands: codecope.org/how-to-self-host-n8n-using-docker/ Docker: docs.docker.com/engine/install/ubuntu/
Self-Host Chatwoot using Docker in 11 Minutes (very easy)
Переглядів 507Місяць тому
Learn how to self-host Chatwoot, the open-source customer support tool, using Docker in just 11 minutes! This step-by-step guide makes it super easy to set up your own Chatwoot server, perfect for handling customer communications on your own infrastructure. Follow along to get Chatwoot up and running quickly with Docker, even if you're a beginner. Full guide with commands: codecope.org/how-to-s...
Thanks very much, I have seen a few videos on Coolify but they were too technical for me and I just gave up but I may attempt this approach, it seems much more approachable for a beginner....
Looks good, but is the storage really working? This makes many times problem in self-hosted.
The normal storage works using this method, but you can set up S3 as well.
I'm not exactly a novice, but the official documentation isn't very thorough. I followed the steps like a complete newbie, one by one, and it worked perfectly. Yesterday, I spent the whole night debugging, going in circles. I think I missed the detail about the password. Keep posting these self-hosted tutorials on VPS setups. Especially since Hetzner has incredible prices. I'm now moving from the competition to them. Judging by your accent, you're probably German. I'll have a German beer in your honor.
I'm glad the tutorial worked for you! Enjoy your beer, cheers!
Dude, your videos are amazing! This is only the second self-hosting channel I've found after three days of searching UA-cam. Keep up the great work; I'm totally new to this self-hosting thing-the whole AI coding craze got me into it-and tons of us are trying to self-host to cut cloud costs and focus on our own projects. Keep pushing every day 💪
Thanks for the kind words. I hope the video was able to help you! :)
hey! i followed the tutorial step-by-step a few times, even tried following through the official documentation, but i always end up at the nginx welcome screen saying further configuration is required. have you run into this before/have any tips? thank you so much for the tutorial!
Hey, the issue you're encountering is common when the Nginx configuration isn't correctly set up to point to the Chatwoot application. Maybe you want to check back and ensure that the Nginx configuration file specifies the correct upstream for Chatwoot. For example, your configuration should have a block similar to this: server { listen 80; server_name yourdomain.com; location / { proxy_pass chatwoot_backend:3000; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_read_timeout 90; } location /cable { proxy_pass chatwoot_backend:3000/cable; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; } } Replace yourdomain.com with your actual domain. Also, don't forget to reload Nginx after editing the configuration: sudo nginx -t && sudo systemctl reload nginx You can also check Docker to see if everything is there. Use: docker ps You should see containers like chatwoot, chatwoot_backend, and a database container. If any are missing, check your docker-compose.yml. Next up are your environment variables. Verify your .env file. It should match your Nginx configuration, especially the FRONTEND_URL and BACKEND_URL values. Hopefully I was able to help. :)
Хороший мануал. А можно работать с n8n без доменного имени и заходить только по ip адресу и номеру порта?
Прежде всего: к сожалению, я не очень хорошо говорю по-русски, только по-немецки и по-английски. Поэтому следующий текст может быть переведен неправильно. Да, можно использовать n8n без доменного имени, обращаясь к нему только по IP-адресу и номеру порта. По умолчанию n8n работает на localhost:5678, что позволяет подключаться через IP-адрес 127.0.0.1 и порт 5678. Если вы развертываете n8n на сервере или в сети, можно использовать IP-адрес сервера и соответствующий порт. Пошаговая инструкция: 1. Запуск сервера: Если вы запускаете n8n напрямую, он будет доступен по адресу <IP-адрес>:<порт>. Например: 123.456.789.012:5678 2. Настройка порта: По умолчанию используется порт 5678. Если необходимо использовать другой порт, это можно настроить с помощью переменной окружения N8N_PORT: export N8N_PORT=8080 3. Настройка IP-адреса (Docker): Если вы запускаете n8n в контейнере Docker, необходимо настроить контейнер так, чтобы он слушал внешний IP-адрес: docker run -it --rm \ -p 123.456.789.012:5678:5678 \ n8nio/n8n 4. Без HTTPS: При использовании n8n без доменного имени обычно он работает без HTTPS. Обратите внимание, что это не рекомендуется для продуктивных сред, так как это создает угрозу безопасности. Для продуктивной эксплуатации следует использовать обратный прокси (например, NGINX или Traefik). Вопросы безопасности: Если вы делаете n8n публично доступным без доменного имени и HTTPS, рекомендуется: Использовать VPN для ограничения доступа. Включить аутентификацию (N8N_BASIC_AUTH_ACTIVE=true). Размещать n8n за брандмауэром или прокси. Если вам нужны дополнительные детали, обратитесь к официальному руководству по n8n.
I have zero reason to self host chatwoot, but I just wanted to say that your english is very good. You don't need to include disclaimers!
Thanks! :)