-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix mailcow update task, add tags and improve README #47
Conversation
Thanks for working on this! Just a question: did you make sure that this doesn't break when installing for the first time? |
@francisco-core The tasks with the tag |
- Only install role if mailcow does not exist already - Refactor conditional statements - Add missing default variables
- name: debian10-instance | ||
box: generic/debian10 | ||
memory: 2000 | ||
cpus: 1 | ||
groups: | ||
- mailserver |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we doing deploy on 2?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an error, 2 different version of Debian should be tested.
|
||
platforms: | ||
- name: debian9-instance | ||
box: generic/debian10 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be changed to generic/debian9
.
For me it's ready to merge. Let's just wait for travis to do its job. |
- Switch to docker_compose as docker_service is deprecated - Add docker-compose pip module to molecule preparation stage
Changing docker mirror due to rate limits in pulls.
Since February the 28th 2017 mailcow does come with port 80 and 443 enabled. https://mailcow.github.io/mailcow-dockerized-docs/u_e-80_to_443/
@anadahz let me know when it's ready for review. |
TODO: Make update tasks idempotent
The Debian images need to upgrade grub-pc, which cause a pop-up, breaking the update role. This issue affects only the testing generic Debian Vagrant images. See: adoptium/infrastructure#1980
Implement only for Molecule testing as Travis CI IP addresses often get rate limited.
@francisco-core This is now ready to merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some minor questions / details, but other than that it's good to merge. Thank you for all the work done here!
64343935313532643730613634653633373066616332326233383866613564643437323630383165 | ||
37333139663266303366373732396366613766666230333730643638383532396435323639366662 | ||
6364623030656639643964333361363735626162653861643931 | ||
36366135343963646138626131313034343638366566386166353533316464623032353338636433 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't have here a DOCKERHUB_USER
and pass. Don't we need it defined here to avoid those rate-limits?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please see my response in comment: https://github.com/PrivacyLx/devops/pull/47/files#r598289108
state: latest | ||
|
||
# Bug: https://github.com/pypa/get-pip/issues/83 | ||
- name: Install pip3.5 workaround |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given that on the host system we are installing python3-pip
shouldn't we also install here just a generic pip version? like from https://bootstrap.pypa.io/get-pip.py
? I don't see any easy way to keep these consistent. Though I can also see Debian saying well behind on pip compared to that official one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for spotting this, this fix shouldn't be in this branch.
I removed this file in the commit: 76252b4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well if it works, then it's good.
good to merge |
@francisco-core Thank you for the review, merging. |
No description provided.