If all you want to do is quickly get a production like server up and running with least amount of fuss, I've provided an example here along with the config and password file.
https://github.com/gocd/gocd/issues/3618#issuecomment-311545904 On Wed, Jul 5, 2017 at 4:11 PM Ketan Padegaonkar <[email protected]> wrote: > On Tue, Jul 4, 2017 at 7:17 PM Chris Northwood <[email protected]> > wrote: > >> Hi Aravind, >> >> I'm still having issues using the Vagrant box, and getting it set up with >> 17.7. When I try to create a pipeline (before adding the authorization >> plugin), I get a CSRF error. >> > > That's usually an indication that you have another server running on the > same host but different ports causing all sorts of weirdness. Could you > confirm that you only have one server running on "localhost", or whatever > you're using for development? > > >> If I add the authorization plugin, I can never get past the login screen >> (similar to https://groups.google.com/forum/m/#!topic/go-cd/Qe_tEdgQhTg). >> I'm curious if there's any obvious environment issues between us, as the >> Vagrant box should give us the same environment :/ Alternatively, could the >> gocd demo Vagrant box get updated to the latest version of GoCD, so I can >> use that as a base instead of rolling my own? >> > > What demo vagrant box are you referring to? We use the box built out of > the Vagrantfile <https://github.com/gocd/gocd/blob/master/Vagrantfile> > checked into the gocd repository. Alternatively: > > docker run -it --rm -v $(pwd):/gocd -v > $HOME/.gradle:/go/.gradle gocdcontrib/gocd-dev-build:v1.0.23 /bin/bash > > The docker example is a lot easier to work with, since it involves not > having to download and install stuff on a network. If you run that docker > command in the directory containing your gocd sourcecode, it's mounted in > `/gocd` inside the docker container. > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
