This would be a big win for me, and many others I am sure. Well, if the
solution were really packaged ready.
Putting together a remote team is hard enough, but when the work doesn’t
properly flow due to dev challenges not solved by an easy to deploy CI
system… it would be great if one of you guys could tell me what you are
doing for this. Especially if it is approachable enough for most remote
team members.
This would be a big win for me, and many others I am sure. Well, if the
solution were really packaged ready.Putting together a remote team is hard enough, but when the work doesn’t
properly flow due to dev challenges not solved by an easy to deploy CI
system… it would be great if one of you guys could tell me what you are
doing for this. Especially if it is approachable enough for most remote
team members.
Whoa. That’s a big spectrum of options there 
We are moving our deployment pipeline to Docker. This makes recreating
development, staging and production environments very straightforward. But
getting into Docker means diving into a fairly deep rabbit hole… I think
its worth it in the long run, but something you’d need to invest
significant time into.
In truth, any devops implementation will be relatively bespoke, and will
need time, effort and political capital – ie. expect to fail a fair bit
initially
If you are interested in Dockerising all things, am happy to help.
GBOn Thursday, 10 September 2015 08:10:30 UTC+10, John Farrar wrote:
I am definitely interested in learning Docker, but my next learning window
of that size is likely going to be early in 2016. ( based on the learning
curve you are describing )On Wednesday, September 9, 2015 at 8:17:09 PM UTC-4, Geoff Bowers wrote:
On Thursday, 10 September 2015 08:10:30 UTC+10, John Farrar wrote:
This would be a big win for me, and many others I am sure. Well, if the
solution were really packaged ready.Putting together a remote team is hard enough, but when the work doesn’t
properly flow due to dev challenges not solved by an easy to deploy CI
system… it would be great if one of you guys could tell me what you are
doing for this. Especially if it is approachable enough for most remote
team members.Whoa. That’s a big spectrum of options there
We are moving our deployment pipeline to Docker. This makes recreating
development, staging and production environments very straightforward. But
getting into Docker means diving into a fairly deep rabbit hole… I think
its worth it in the long run, but something you’d need to invest
significant time into.In truth, any devops implementation will be relatively bespoke, and will
need time, effort and political capital – ie. expect to fail a fair bit
initiallyIf you are interested in Dockerising all things, am happy to help.
GB
Just to throw it out there, I currently have a CI solution in place that
makes heavy use of CommandBox to allow the unit tests to be executed.
Long term I may well be following Geoffs lead on moving to Docker, but
until then the CommandBox method is fit for purpose and allows for a high
degree of certainty that the results seen are accurate. The only issues
I’ve really had are timezone related due to the way the local server was
originally configured - this is the reason for possibly looking at Docker
etc.
For my lucee-aws project I have used Travis CI. If you’d like to see how
that was done then you can see the /tests folder along with the .travis.yml
etc on GitHub - mso-net/lucee-aws: Lucee extension to provide simpler access to common AWS commands through the AWS SDK - that pushes through
into https://travis-ci.org/mso-net/lucee-aws which in turn runs the tests -
it doesn’t really do much else past that but for now it at least lets me
see that things are looking ok.On Wednesday, 9 September 2015 23:10:30 UTC+1, John Farrar wrote:
This would be a big win for me, and many others I am sure. Well, if the
solution were really packaged ready.Putting together a remote team is hard enough, but when the work doesn’t
properly flow due to dev challenges not solved by an easy to deploy CI
system… it would be great if one of you guys could tell me what you are
doing for this. Especially if it is approachable enough for most remote
team members.
The thing is you are talking about “CI” but CI stuff is largely platform
independant, it’s just about how you set up/tear down your environment,
that same thing is an issue for any language you can choose really.
It’s just that in some cases the language is lighter weight, i.e. doesn’t
require the full JVM that CF/Lucee does which leads to it being a bit
quicker to spin up/tear down your CI environment.
Docker / Vagrant / CommandBox / Shell Scripts are all just means to setting
up/tearing down that environment, and from there you can use it in whatever
CI server you desire. Personally I go for Bamboo or Travis, but Jenkins
etc are all viable too.On Thursday, 10 September 2015 13:43:44 UTC+1, John Farrar wrote:
I am considering CommandBox also in my options.
Here is my struggle, ColdFusion is not dead but it is not premier or
uniquely compelling to an outsider. Lucee has potential to shift that play
if we can bring some things like CI into our mix. Without something like
that, it is harder to convert people to the platform. To my bad, I should
have learned ColdBox when I had the chance as it seems to have a better
core at large. The training is a fair price but it was more than I budgeted
at that time.On Thursday, September 10, 2015 at 6:03:06 AM UTC-4, Simon Hooker wrote:
Just to throw it out there, I currently have a CI solution in place that
makes heavy use of CommandBox to allow the unit tests to be executed.Long term I may well be following Geoffs lead on moving to Docker, but
until then the CommandBox method is fit for purpose and allows for a high
degree of certainty that the results seen are accurate. The only issues
I’ve really had are timezone related due to the way the local server was
originally configured - this is the reason for possibly looking at Docker
etc.For my lucee-aws project I have used Travis CI. If you’d like to see how
that was done then you can see the /tests folder along with the .travis.yml
etc on GitHub - mso-net/lucee-aws: Lucee extension to provide simpler access to common AWS commands through the AWS SDK - that pushes through into
https://travis-ci.org/mso-net/lucee-aws which in turn runs the tests -
it doesn’t really do much else past that but for now it at least lets me
see that things are looking ok.On Wednesday, 9 September 2015 23:10:30 UTC+1, John Farrar wrote:
This would be a big win for me, and many others I am sure. Well, if the
solution were really packaged ready.Putting together a remote team is hard enough, but when the work doesn’t
properly flow due to dev challenges not solved by an easy to deploy CI
system… it would be great if one of you guys could tell me what you are
doing for this. Especially if it is approachable enough for most remote
team members.
John, First off I love your books.
installing a CF environment is as unique as a snowflake. I have not seen
two that are the same.
As for remote workers, to me it would be faster and overall easier just to
build an image on digital ocean or amazon, or any other vps service that
lets you clone a vps.
Setup once, then clone as many new servers as you need. Its cheap, it has
backup options, and it helps cut deployment time down to a few minutes once
setup.
As for using Docker, Its very much overly hyped software IMHO.
Vmware has been doing the same thing for nearly two decades, its called the
vmware marketplace.
As for docker, if the community needs it. ill go build a minimal image over
the weekend using:
CentOS 7 + Apache Tomcat + Apache + Mod_CFML
There are already a couple of official Lucee docker containers available:
https://hub.docker.com/r/lucee/
Kind regards,
Andrew
about.me http://about.me/andrew_dixon - mso http://www.mso.net - Lucee
Association Member http://lucee.orgOn 10 September 2015 at 17:32, Terry Whitney <@Terry_Whitney> wrote:
John, First off I love your books.
installing a CF environment is as unique as a snowflake. I have not seen
two that are the same.As for remote workers, to me it would be faster and overall easier just to
build an image on digital ocean or amazon, or any other vps service that
lets you clone a vps.Setup once, then clone as many new servers as you need. Its cheap, it has
backup options, and it helps cut deployment time down to a few minutes once
setup.As for using Docker, Its very much overly hyped software IMHO.
Vmware has been doing the same thing for nearly two decades, its called
the vmware marketplace.As for docker, if the community needs it. ill go build a minimal image
over the weekend using:CentOS 7 + Apache Tomcat + Apache + Mod_CFML
–
See Lucee at CFCamp Oct 22 & 23 2015 @ Munich Airport, Germany - Get your
ticket NOW - http://www.cfcamp.org/You received this message because you are subscribed to the Google Groups
“Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/e845ec8c-3067-4d16-80d1-8c8f8fadcd41%40googlegroups.com
https://groups.google.com/d/msgid/lucee/e845ec8c-3067-4d16-80d1-8c8f8fadcd41%40googlegroups.com?utm_medium=email&utm_source=footer
.For more options, visit https://groups.google.com/d/optout.
I am considering CommandBox also in my options.
Here is my struggle, ColdFusion is not dead but it is not premier or
uniquely compelling to an outsider. Lucee has potential to shift that play
if we can bring some things like CI into our mix. Without something like
that, it is harder to convert people to the platform. To my bad, I should
have learned ColdBox when I had the chance as it seems to have a better
core at large. The training is a fair price but it was more than I budgeted
at that time. :)On Thursday, September 10, 2015 at 6:03:06 AM UTC-4, Simon Hooker wrote:
Just to throw it out there, I currently have a CI solution in place that
makes heavy use of CommandBox to allow the unit tests to be executed.Long term I may well be following Geoffs lead on moving to Docker, but
until then the CommandBox method is fit for purpose and allows for a high
degree of certainty that the results seen are accurate. The only issues
I’ve really had are timezone related due to the way the local server was
originally configured - this is the reason for possibly looking at Docker
etc.For my lucee-aws project I have used Travis CI. If you’d like to see how
that was done then you can see the /tests folder along with the .travis.yml
etc on GitHub - mso-net/lucee-aws: Lucee extension to provide simpler access to common AWS commands through the AWS SDK - that pushes through into
https://travis-ci.org/mso-net/lucee-aws which in turn runs the tests - it
doesn’t really do much else past that but for now it at least lets me see
that things are looking ok.On Wednesday, 9 September 2015 23:10:30 UTC+1, John Farrar wrote:
This would be a big win for me, and many others I am sure. Well, if the
solution were really packaged ready.Putting together a remote team is hard enough, but when the work doesn’t
properly flow due to dev challenges not solved by an easy to deploy CI
system… it would be great if one of you guys could tell me what you are
doing for this. Especially if it is approachable enough for most remote
team members.
