Skip to content
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

Dockerfile for plone.restapi #301

Merged
merged 8 commits into from May 1, 2017
Merged

Dockerfile for plone.restapi #301

merged 8 commits into from May 1, 2017

Conversation

tisto
Copy link
Sponsor Member

@tisto tisto commented Mar 29, 2017

No description provided.

site.cfg Outdated
eggs += plone.restapi

[versions]
plone.stringinterp = 1.0.14
Copy link
Sponsor Member

@avoinea avoinea Mar 29, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think you need this pin, thus you can remove:

[versions]
plone.stringinterp = 1.0.14

Dockerfile Outdated

USER root
RUN apt-get update \
&& apt-get install -y --no-install-recommends build-essential \
Copy link
Sponsor Member

@avoinea avoinea Mar 29, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You may not need to install build-essential if you don't compile C modules. Thus you can remove:

USER root
RUN apt-get update \
 && apt-get install -y --no-install-recommends  build-essential \
 && rm -rf /var/lib/apt/lists/*
USER plone

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you use apt install, you also may want to use apt-get clean

.travis.yml Outdated
@@ -24,3 +24,4 @@ after_success:
- bin/createcoverage
- pip install coverage==3.7.1 coveralls
- coveralls
- docker.io build --tag plone-dev:207.03.29 .
Copy link
Sponsor Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo in 207.03.29 ;)

@coveralls
Copy link

coveralls commented Mar 29, 2017

Coverage Status

Coverage increased (+0.2%) to 96.243% when pulling 08f1e96 on docker into f362df0 on master.

@coveralls
Copy link

coveralls commented Mar 29, 2017

Coverage Status

Coverage increased (+0.2%) to 96.243% when pulling e9680f8 on docker into f362df0 on master.

@coveralls
Copy link

coveralls commented Mar 29, 2017

Coverage Status

Coverage increased (+0.2%) to 96.243% when pulling e9680f8 on docker into f362df0 on master.

@tisto
Copy link
Sponsor Member Author

tisto commented Apr 28, 2017

@avoinea @svx I have a docker image with plone.restapi that I can push to dockerhub now. To automate the process I guess it would make sense to hook this up with the plone user on dockerhub. Do you agree with that?

@gforcada
Copy link
Sponsor Contributor

@tisto a changelog entry please 😄

@avoinea
Copy link
Sponsor Member

avoinea commented Apr 28, 2017

@tisto yes ;)

@tisto
Copy link
Sponsor Member Author

tisto commented Apr 29, 2017

@gforcada a changelog entry does not make much sense here in my opinion. This is not a change on the package itself.

@tisto
Copy link
Sponsor Member Author

tisto commented Apr 29, 2017

@avoinea do you know who can help me with the plone credentials for dockerhub? We need to add them to the plone.restapi repo, to be able to use it to make travis automatically upload docker images to dockerhub.

.travis.yml Outdated
@@ -24,3 +24,5 @@ after_success:
- bin/createcoverage
- pip install coverage==3.7.1 coveralls
- coveralls
- docker.io build --tag plone.restapi:$(git rev-parse HEAD) .
# - docker.io push kitconcept/plone.restapi
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reminder: Do not forget to change that to plone, later on, otherwise you will push it to kitconcept on dockr hub and not to plone :)

Copy link
Sponsor Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Absolutely. I need the plone credentials on the plone.restapi first though. :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh and make sure to check: https://docs.travis-ci.com/user/docker/

You need:

services:
- docker

and change

docker.io

to docker

Copy link
Sponsor Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@svx I don't want to run docker on travis. Just automatically build the latest version and push it to dockerhub. Other projects should use the plone.restapi docker service on travis then in order to run tests against it (with their custom front-ends for instance).

Copy link
Sponsor Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am a bit confused. On Ubuntu I need to user docker.io. Maybe travis is using a symlink to be able to use docker instead when you use a docker service. Anyways, will test this as soon as I have the plone dockerhub credentials. :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, but if you want travis to push you need docker installed, right ?

Yeah, this is when you install docker from the ubuntu repositories, but if you for example install docker from the docker repos it is called docker.

I do not know how travis uses/installs docker there are different ways.

Copy link
Sponsor Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@svx you are correct. It just turned out my commands weren't executed at all. :(

@coveralls
Copy link

coveralls commented May 1, 2017

Coverage Status

Coverage remained the same at 96.481% when pulling 68357f6 on docker into 5079cfd on master.

@coveralls
Copy link

coveralls commented May 1, 2017

Coverage Status

Coverage remained the same at 96.481% when pulling 68357f6 on docker into 5079cfd on master.

@tisto tisto merged commit 4e20b9a into master May 1, 2017
@tisto tisto deleted the docker branch May 1, 2017 10:54
@tisto tisto removed the in progress label May 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants