Devilbox Release v1.0.0

[cytopia]

Devilbox Release v1.0.0

READFIRST

This branch is constantly being rebased from master until final merge, therefore requires git force pushing. So how to update changes from this branch:

# Receive new commits
git fetch --all --prune

# Delete release/v1.0.0 branch
git checkout master
git branch -D release/v1.0.0

# Checkout release/v1.0.0 again
git checkout release/v1.0.0
git pull origin release/v1.0.0

Then you will have to ensure to remove container before starting them up again:

docker-compose stop
docker-compose rm
docker-compose up

IMPORTANT

When using this branch, you will loose all you current data for MySQL, PostgreSQL and MongoDB, so ensure to make a backup first.

• Backup Mysql
• Backup PostgreSQL
• Backup MongoDB

Once you have backed up everything, start the Devilbox from this branch and import your data.

---

DOCUMENTATION

Documentation for this release is available here: https://devilbox.readthedocs.io/en/release-v1.0.0/

DESCRIPTION

This will be the first stable release of the Devilbox.

Features

PR's:

• Docker Volumes: Release v1.0.0: Docker volumes (breaking changes) #383
• Internal DNS and Auto DNS separation: WIP: Release v1.2.0: Auto DNS (breaking changes) #411: moved to Milestone 1.1
• Semantic versioning for faster+safer releases
• Official MySQL, MariaDB and Percona Docker container

Issues:

• Refs: Using Docker for Windows to volume-mount a Windows drive into a Linux container is bad #175

Notable readings

• CHANGELOG
• UPDATING
• CONTRIBUTING

[llaville]

What a good new !
BTW, could you envisage to use this changelog format

[cytopia]

@llaville thanks for the info. I've altered it to their standard.

[vikas5914]

Hi, I am trying this branch and getting this error:

Recreating devilbox_bind_1 ... error

ERROR: for devilbox_bind_1  Cannot start service bind: driver failed programming external connectivity on endpoint devilbox_bind_1 (0cca32e8f31ea237b52a7257a1d84276f3d3376f1a6ba4f304f3598a418d1eab): Error starting userland proxy: Bind for 0.0.0.0:1050: unexpected error Permission denied

ERROR: for bind  Cannot start service bind: driver failed programming external connectivity on endpoint devilbox_bind_1 (0cca32e8f31ea237b52a7257a1d84276f3d3376f1a6ba4f304f3598a418d1eab): Error starting userland proxy: Bind for 0.0.0.0:1050: unexpected error Permission denied
ERROR: Encountered errors while bringing up the project.

I have deleted all the images, container , volumes.

I have also checked if the port is in used (There are not)

But changing the DNS port to 53 works.

[vikas5914]

@cytopia I tried 1050, 1051, 1052 and 1049 ports. Same result. (on 12th Feb)

[az09asdf]

@cytopia

1. tried to reproduce error: now it's gone (false alarm; sorry; cannot remember error message)
2. still the same: change to 0.30 prevents access to the devilbox site (the same for 0.15 version)
   (It's probably irrelevant, by I'm using somewhat specific setup: I'm working in Windows (coding, git, browsers) and using devilbox on an ubuntu 18.04 server virtual machine. However, never had such an issue before.)

[cytopia]

@az09asdf I have a strong feeling that this might have been related to a Nginx configuration change. Do you get an error like this: nginx: [emerg] "client_max_body_size" directive is duplicate in /etc/httpd-custom.d/devilbox-custom.conf:1 via Docker logs?

[cytopia]

@vikas5914 one thing I can suggest is to fully clean everything:

# Stop Devilbox and remove its stopped container
docker-compose stop
docker-compose rm -f
# Stop and remove all other container
docker ps -q | xargs docker stop
docker ps -qa | xargs docker rm

Then make sure that your .env file equals to the new env-example.
Also ensure there is for sure nothing else listening on UDP for that port.
And start Devilbox again.

[az09asdf]

@cytopia

Commenting client_max_body_size in my custom nginx.conf solved the issue.

1. do you know how to set client_max_body_size for 0.30 ?
2. couldn't find the error you suggested: "via Docker logs" means devilbox/log/nginx-stable/ ?

[cytopia]

@cytopia

Commenting client_max_body_size in my custom nginx.conf solved the issue.

1. do you know how to set client_max_body_size for 0.30 ?
2. couldn't find the error you suggested: "via Docker logs" means devilbox/log/nginx-stable/ ?

Yes you can still overwrite this value if you are on a different context: http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size

It currently has been set on the http context and you would need the server or location context to change this value. This can be achieved via custom vhost settings:

• https://devilbox.readthedocs.io/en/latest/vhost-gen/customize-all-virtual-hosts-globally.html#vhost-gen-customize-all-virtual-hosts-globally
• https://devilbox.readthedocs.io/en/latest/vhost-gen/customize-specific-virtual-host.html#vhost-gen-customize-specific-virtual-host

The actual issue that has information on why this was set (to 0 to be in sync with Apache 2.(2|4)) is here: #356

[cytopia]

I will postpone the planned merge until the current issues for Mac and MySQL are investigated. I would rather prioritize stability over features.

[vikas5914]

@cytopia

I removed everything (images, volume, network and Devil) and tried again, it worked.

[cytopia]

@vikas5914 just in time :-)

The freeze is removed, issue in question (#542) has been resolved