Nginx Mastery | Static Files | Multiple Domain | Local DNS configuration

Подписаться 65 тыс.

Просмотров 21 тыс.

50% 1

The Nginx Mastery Series focuses on building and administrating Nginx services. In this tutorial we focus in configuring multiple domain names learning more about Nginx configuration for serving static sites. In addition, we build a local DNS server working from a Docker container.
Repository:
github.com/veryacademy/yt-ngi...

Опубликовано:

27 апр 2022

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 19

@forestandnaturetherapy 10 месяцев назад

Whoohoo! Thank you :D

@shaheerzaman620 Год назад

cool stuff!

@soroushamirhashchi7142 Год назад

Thank you.

@div7624 Год назад

Couldn't you just modify the /etc/resolv.conf of the containers to use your dns container, rather than change your host system's DNS resolver? I'm not sure if this would work or not but it would interesting if it did.

@jamshid_dev 2 года назад

thanks bro 👍

@liorbm1 Год назад

you could also change your hosts file

@ronald418 6 месяцев назад

And save yourself a lot of work.

@LryuzakiLN 2 месяца назад

How to do that?

@njmsaikat 2 года назад

I'm getting error, it;s saying port number 80 and 53 both already in use. running on ubuntu and there's a apache2 server already running on my local machine, not on docker. I changed the port number in container for dns to 54 and nginx back to 8000 in docker-compose file. Then it started running but when i run nslookup command , it couldn't find the server. can you give me some suggestion, please.

@jamshid_dev 2 года назад

mee too the same .... it's said similar error ... port 53 already in use. Maybe apache2 server is uses port 80 on your localhost, therefore you can stop it by "sudo service nginx stop" or "systemctl nginx.service stop" commands. unfortunately, I don't know which which service is uses port 53 on your localhost

@pascalkarisa6934 Год назад

For those experiencing the same error and using Ubuntu. Do the following after running docker compose build: sudo systemctl stop systemd-resolved sudo systemctl disable systemd-resolved After that then run: docker compose up Will work. NB. You will not be able to access the internet thus later you'll have to rollback the above commands by running : sudo systemctl enable systemd-resolved sudo systemctl start systemd-resolved Thanks.

@etiennerobert6462 2 года назад

Thank you. How to serve pdf files and images with Nginx but only to users that have permission on those files and are logged in on my Django website ?

@veryacademy 2 года назад

There are a few different options. Have a read through the link below. Thanks for the tutorial suggestion! stackoverflow.com/questions/28166784/restricting-access-to-private-file-downloads-in-django

@etiennerobert6462 2 года назад

@@veryacademy Thanks for the link. I like the last guy's idea response['X-Accel-Redirect'] = path_to_file. I wonder if it works. Also, I suppose it Nginx would serve both Django website and serve all static files plus the user private files. Would be a nice tutorial indeed.