We've used to copy the .conf file from /debian/odoo.conf and modified it along the way to our needs. This could trigger issues and cornercases. Since Odoo 11.0 this breaks the default installation script.
There where two options:
1) Create sed commands to find the doubles and remove them - which would have issues with the regex expressions and special characters such as "/".
2) Create a new configuration file from scratch and fill it with our own data
Obviously, I went for option 2.
Before this addition you would only have one chance to fill in the Github credentials.
If they where wrong the script would fail on a lot of the remaining steps, you would need to run the script and you might even get issues because of already used commands.
This commit adds the response from Github to check if the credentials are valid are not.
In case they're invalid we'll ask them again (untill they're correct) and we'll show a warning to the user that they where invalid or that the user does not have enough rights on the Github repository.
If they succeed we'll clone the enterprise repository and continue.
Added the "--depth 1" to the command so it only retrieves the latest version without all the repository history, which makes the download quite a bit quicker, and uses less space in disk, making it suitable for a production environment.
Added:
- Odoo is now automatically started at the end of the install script
- The terminal now shows an overview with all details about the freshly installed Odoo. This will give you a good insight and will also show possible errors that you might have made.
Yenthe V.G
Vincent Adriaensen
Sebastian Reyes Espinosa
Temur Vibliani