Skip to content

Conversation

@Hyperclaw79
Copy link
Contributor

No description provided.

@shahidhk
Copy link
Contributor

shahidhk commented Jan 3, 2018

@Hyperclaw79 Have you tested that all of these microservices as working by pushing them to a cluster?

@Hyperclaw79
Copy link
Contributor Author

I've tested a few. I'll let you know once I'm done with all the tests.

@@ -1,4 +1,4 @@
FROM microsoft/dotnet:1.1-sdk-msbuild
FROM microsoft/dotnet:latest
Copy link
Contributor

Choose a reason for hiding this comment

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

@Hyperclaw79 Can you fix this to a version and not latest? Issue with latest is that if a new release with breaking change happens, it cause problems

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, already fixed it.

@@ -1,4 +1,4 @@
FROM python:2.7-alpine
FROM python:3.7.0a3-alpine3.7
Copy link
Contributor

Choose a reason for hiding this comment

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

Changing python2 to python3 is not a good idea. This will require code changes too.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, that makes sense. In fact, I was wondering about this; whether to port the entire code to Py3+ because that would open up possibilities for improvements and more features. But I guess, for now I'll switch it back to Py2 and I will re-edit it if I make a PR for the Py3 porting too.

Copy link
Contributor Author

@Hyperclaw79 Hyperclaw79 left a comment

Choose a reason for hiding this comment

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

Fixed the images.

@Hyperclaw79
Copy link
Contributor Author

@shahidhk All updates are working properly now, except those with errors not related to base image. I have already opened up issues for those in Support.

@coco98
Copy link
Contributor

coco98 commented Jan 8, 2018

@Hyperclaw79 I think this is good to go. Can you fix the php-laravel/Dockerfile conflict? I think the latest php-laravel/Dockerfile that is on master works. Ccan merge the latest upstream master into your branch and update the PR?

This is a great PR! Let's merge it quickly :)

@Hyperclaw79
Copy link
Contributor Author

@coco98 Done sir. :)
Since it was just a single conflict, I edited the file directly on my fork. Will test it out tomorrow. If it works, well and good, else we can make a new PR to fix it.

@Hyperclaw79
Copy link
Contributor Author

@shahidhk Any updates on this? I can close it if it irrelevant now.

@shahidhk
Copy link
Contributor

shahidhk commented May 30, 2018 via email

dependabot bot and others added 4 commits December 13, 2020 04:38
Bumps [ini](https://github.com/isaacs/ini) from 1.3.5 to 1.3.8.
- [Release notes](https://github.com/isaacs/ini/releases)
- [Commits](npm/ini@v1.3.5...v1.3.8)

Signed-off-by: dependabot[bot] <[email protected]>
…ravel/app/ini-1.3.8

Bump ini from 1.3.5 to 1.3.8 in /php-laravel/app
…app/ini-1.3.8

Bump ini from 1.3.5 to 1.3.8 in /react/app
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.

3 participants