On Thu, May 06, 2021 at 07:54:44AM +0000, Gumansingh, Smita wrote: > Thanks Antonio for the quick reply > Yes I will keep on the same machine where debci-collector is installed > Any specific path where to keep on host machine apache.conf.erb and what changes needs to be done . That is not a complete configuration file, it's a template used by our configuration management tool (i.e. it's just an example). the actual file needs to go where apache configuration goes, in /etc/apache2/sites-enabled/. You will need to learn the basics of managing an apache server. > Is this page is up-to-date https://ci.debian.net/doc/file.HACKING.html > I am also trying to Set up the test environment using above document but getting below error for manual approach Can you start by telling me what is it that you want to achieve? Do you want to setup a production deployment, or a development one? > === > smita@smita:~/debci$ sudo ./tools/init-dev.sh > Traceback (most recent call last): > 4: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' > 3: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' > 2: from /home/smita/debci/lib/debci/db.rb:3:in `<top (required)>' > 1: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' > /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- kaminari/core (LoadError) > ====== This means you didn't install all the necessary packages for development. > Note: Setting up a development environment through vagrant also showing error which error? > Could you please suggest which document I should follow for debci setup. It's confusing for newbie. For development, the documentation you want is indeed HACKING. Try the latest version from git: https://salsa.debian.org/ci-team/debci/-/blob/master/docs/HACKING.md For a production deployment, as you noticed the procedure is not fully documented. On the other hand, out own setup is fully automated in https://salsa.debian.org/ci-team/debian-ci-config/ and you could use that as a base for your own.
Attachment:
signature.asc
Description: PGP signature