Apoyar Wiki - User contributions [en-gb]

Access the Zeb OpenBSD RMG

2017-11-23T18:48:31Z

78.45.88.190: Created page with "* login to the Apoyar in-house OpenBSD (needs to be started from vSphere) * su * ssh azure-user@52.232.69.211"

* login to the Apoyar in-house OpenBSD (needs to be started from vSphere)
* su
* ssh azure-user@52.232.69.211

Tips & Tricks

2017-11-23T18:45:35Z

78.45.88.190:

== Please choose from the following ==
* [[Add new ftps user]]
* [[Exchange 2010 add domain to anti spam whitelist]]
* [[Allow large file download in Nginx/PHP]]
* [[Access the Decovry server]]
* [[Access the Zeb OpenBSD RMG]]
* [[Restart the PHP FPM engine on nginx servers]]
* [[3CX allowing Country Codes to users]]

Main Page

2017-11-23T13:24:34Z

78.45.88.190: /* The database will contain (only blue links usable as it's 'work in progress'; you will get updates over Slack) */

Apoyar Wiki main page.

* [[Infrastructure|Apoyar Infrastructure]]
* [[Complete step-by-step guides]]
* [[Developer guides]]
* [[Tips & Tricks]]

Main Page

2017-11-21T14:07:43Z

78.45.88.190:

Apoyar Wiki main page.

== The database will contain (only blue links usable as it's 'work in progress'; you will get updates over Slack)==
* [[Infrastructure|Apoyar Infrastructure]]
* [[Complete step-by-step guides]]
* [[Developer guides]]
* [[Tips & Tricks]]

Main Page

2017-11-21T14:07:27Z

78.45.88.190:

3CX alloting Country Codes:

Where:

When a 3CX User request or notifies about not able to Dial a specific Country.
Go to 3CX Admin Console ---> Settings--->and Select Security in the options.
Under Allowed Country Codes we will have List of Continents with a drop down.
Select the Respective Continent and then Check the box Beside The Country.

Main Page

2017-11-21T14:06:56Z

78.45.88.190:

3CX alloting Country Codes:

Where:

*When a 3CX User request or notifies about not able to Dial a specific Country.
*Go to 3CX Admin Console ---> Settings--->and Select Security in the options.
*Under Allowed Country Codes we will have List of Continents with a drop down.
*Select the Respective Continent and then Check the box Beside The Country.

Server update process

2017-11-21T13:50:12Z

78.45.88.190: Created page with "'''RESTARTING SERVERS''' systemctl restart php7.0-fpm systemctl restart nginx '''DEV Server updates''' Push to dev-server branch on GitLab and it would be automatically..."

'''RESTARTING SERVERS'''

systemctl restart php7.0-fpm

systemctl restart nginx

'''DEV Server updates'''

Push to dev-server branch on GitLab and it would be automatically updated to DEV server.

$config['base_url'] = 'http://returns.dev.apoyar.eu/';

define('API_BASE_URL_BE', 'http://returns.dev.apoyar.eu/');

define('API_BASE_URL_FE', 'http://returns.dev.apoyar.eu/');

'''UAT Server updates'''

Push to uat-server branch on GitLab and it would be automatically updated to UAT server.

$config['base_url'] = 'http://uat.bleckmann.apoyar.eu/';

define('API_BASE_URL_BE', 'http://api.bleckmann.apoyar.eu//');

define('API_BASE_URL_FE', 'http://api.bleckmann.apoyar.eu/');

'''LIVE SERVER'''

1. connect to vpn

2. Login to Jupiter.apoyar.net with credentials username : APOYAR\administrator, password: W3R@P0y@R!

3. Login to putty with the credentials mentioned in Bleckmann servers text file on desktop.

4. After being logged in to Putty, Please run the below commands

cd /var/www/html

git pull https://github.com/Apoyar/bleckman-front-end.git development

In case of any conflicts, please run "git checkout ." to ensure the local changes are ignored.

Please ensure the changes in config files

In config.php

$config['base_url'] = 'http://returns.bleckmann.com';

In constants.php

//PROJECT CONSTANTS

define('API_BASE_URL_BE', 'http://returnsapi.bleckmann.com/BMAPI/BleckmannApi/');

define('API_BASE_URL_FE', 'http://returnsapi.bleckmann.com:81/BMAPI/BleckmannApi/');

define('SECURE_APOYAR_URL', 'returns.bleckmann.com');

The above process for live server update is valid till we have automatic updates to live through Gitlab.
----------------
'''Live Login Details'''

admin / bl5ckm5nn2017

superdry / Superdryreturns2017!

apoyar / Ap0yar!

sriram_wh/P@ssword123

WHOperator1/P@ssword123
----------------

'''UAT login details'''
------------------
customer superuser : tr1 / P@ssword123
===========================================
https://login.newrelic.com/login

Emails : support@apoyar.net

Password : kz1nv0g0n
=============================================
'''ORACLE DB access on KIRK'''

C:\Users\Administrator\Downloads\sqldeveloper-4.1.5.21.78-x64 (2)\sqldeveloper

Developer guides

2017-11-21T13:44:08Z

78.45.88.190: /* Please choose from the following */

Developer guides.

== Please choose from the following ==
* [[bleckmann API]]
* [[Server update process]]

Restart the PHP FPM engine on nginx servers

2017-11-16T16:52:32Z

78.45.88.190: Created page with "* ssh to the machine in question for PHP 7.0: * sudo service php7.0-fpm restart or for PHP 5: * sudo service php5-fpm restart"

* ssh to the machine in question

for PHP 7.0:
* sudo service php7.0-fpm restart

or for PHP 5:
* sudo service php5-fpm restart

Tips & Tricks

2017-11-16T16:44:25Z

78.45.88.190:

Access the Decovry server

2017-11-16T16:39:07Z

78.45.88.190: Created page with "* login to '''nagios.apoyar''' * use su login with appropriate password * ssh apoyar@87.238.161.52 * no password needed for above * now you can sudo su with no password"

* login to '''nagios.apoyar'''
* use su login with appropriate password
* ssh apoyar@87.238.161.52
* no password needed for above
* now you can sudo su with no password

Tips & Tricks

2017-11-16T16:33:39Z

78.45.88.190: /* Please choose from the following */

== Please choose from the following ==
* [[Add new ftps user]]
* [[Exchange 2010 add domain to anti spam whitelist]]
* [[Allow large file download in Nginx/PHP]]
* [[Access the Decovry server]]

Exchange 2010 add domain to anti spam whitelist

2017-10-20T06:17:29Z

78.45.88.190: Created page with "'''Step 1: Start the Exchange Management Shell''' '''Step 2: Specific Address:''' 1. $list = (Get-ContentFilterConfig).BypassedSenders 2. $list.add(“new.mail@address.com..."

'''Step 1: Start the Exchange Management Shell'''

'''Step 2: Specific Address:'''

1. $list = (Get-ContentFilterConfig).BypassedSenders

2. $list.add(“new.mail@address.com”)
Run the $list.add for each email address that you want to include.

3. Set-ContentFilterConfig -BypassedSenders $list

'''Step 3: Entire Domain:'''

1. $list = (Get-ContentFilterConfig).BypassedSenderDomains

2. $list.add(“domain.com”)

3. Set-ContentFilterConfig -BypassedSenderDomains $list

'''Step 4: Verify Change:'''

Get-ContentFilterConfig

Tips & Tricks

2017-10-20T06:15:47Z

78.45.88.190:

== Please choose from the following ==
* [[Add new ftps user]]
* [[Exchange 2010 add domain to anti spam whitelist]]
* [[Allow large file download in Nginx/PHP]]

Add new ftps user

2017-08-11T12:01:22Z

78.45.88.190: Add new ftps user

Login (SSH) to the server in question and run the 2 commands:

'''useradd -m -d /var/www/ -G www-data -s /bin/bash username'''

'''passwd username'''

Where:

* /var/www/ is the folder you want the user to have access to. Don't give him more permissions than needed! Sometimes they only need an import folder or so.
* www-data is the '''group''' nginx (or apache) is running under. This is necessary for the user to be able to upload files.
* /bin/bash is the default login shell. It won't work without this.
* username is the desired username
* with the passwd command you set the password

Tips & Tricks

2017-08-11T11:54:08Z

78.45.88.190: Add new ftps user

== Please choose from the following ==
* [[Add new ftps user]]

Installing ruby on rails with Nginx passenger

2017-05-29T10:17:02Z

78.45.88.190: Configure Nginx to use Ruby on Rails.

* install requisites:

'''apt-get install ruby ruby-dev ruby-bundler'''

* install the Passenger app:

'''apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 561F9B9CAC40B2F7'''

'''apt-get install -y apt-transport-https ca-certificates'''

'''sh -c 'echo deb https://oss-binaries.phusionpassenger.com/apt/passenger xenial main > /etc/apt/sources.list.d/passenger.list''''

'''apt-get update'''

'''apt-get install nginx-extras passenger'''

* install ruby dev packages:

'''apt-get install libgmp3-dev make gcc g++ libpq-dev '''

* set Nginx to use Passenger:

'''vi /etc/nginx/nginx.conf'''

* find the following lines, and uncomment them:

'''include /etc/nginx/passenger.conf'''

* edit the Passenger configuration:

'''vi /etc/nginx/passenger.conf'''

* change the passenger_ruby line to point to your ruby executable:

passenger_ruby /home/deploy/.rbenv/shims/ruby; # If you use rbenv

passenger_ruby /home/deploy/.rvm/wrappers/ruby-2.1.2/ruby; # If use use rvm, be sure to change the version number

passenger_ruby /usr/bin/ruby; # If you use ruby from source

The passenger_ruby is the important line here. Make sure you only set this once and use the line from the example that pertains to the version of Ruby you installed.

Once you've changed passenger_ruby to use the right version Ruby, you can run the following command to restart Nginx with the new Passenger configuration:

'''service nginx restart'''

* In order to get Nginx to respond with the Rails app, we need to modify it's sites-enabled:

server {
listen 80;
server_name devtimesheet.apoyar.eu;
passenger_enabled on;
rails_env production;
passenger_friendly_error_pages on;

root /var/www/timesheet;
passenger_app_root /var/www/timesheet;

access_log /var/log/nginx/timesheet_access.log;
error_log /var/log/nginx/timesheet_error.log;

# redirect server error pages to the static page /50x.html
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root html;
}
}

Complete step-by-step guides

2017-05-29T10:09:11Z

78.45.88.190: New manual item

Step-by-step guides.

== Please choose from the following ==
* [[Add new joinee]]
* [[Add new server]]
<nowiki>======================================</nowiki>
* [[Add new user to GitLab]]
* [[Add new server to GitLab AutoDeploy]]
* [[Convert the SVN repository to GitLab]]
* [[Installing ruby on rails with Nginx passenger]]
* [[Install Oracle client on Ubuntu]]
* [[Remove NewRelic agent]]

Remove NewRelic agent

2017-05-26T15:41:38Z

78.45.88.190: Amending fonts

* For the main service:
'''/etc/init.d/newrelic-sysmond stop'''

'''apt-get --purge remove newrelic-sysmond'''

* For the PHP agent:
'''newrelic-install purge'''

'''apt-get --purge remove newrelic-php5-common'''

'''dpkg -l | grep newrelic'''

(nothing should show when you run the above, if anything, proceed to manually removing the remaining services)

'''service nginx restart'''

'''service php7.0-fpm restart'''

* For MySQL agent:

'''cd /root/newrelic-npi'''

'''./npi stop com.newrelic.plugins.mysql.instance'''

'''./npi remove-service com.newrelic.plugins.mysql.instance'''

'''./npi remove com.newrelic.plugins.mysql.instance'''

Remove NewRelic agent

2017-05-26T15:40:42Z

78.45.88.190: Amending font properties.

====* For the main service:====
'''/etc/init.d/newrelic-sysmond stop'''

'''apt-get --purge remove newrelic-sysmond'''

====* For the PHP agent:====
'''newrelic-install purge'''

'''apt-get --purge remove newrelic-php5-common'''

'''dpkg -l | grep newrelic'''

(nothing should show when you run the above, if anything, proceed to manually removing the remaining services)

'''service nginx restart'''

'''service php7.0-fpm restart'''

====* For MySQL agent:====

'''cd /root/newrelic-npi'''

'''./npi stop com.newrelic.plugins.mysql.instance'''

'''./npi remove-service com.newrelic.plugins.mysql.instance'''

'''./npi remove com.newrelic.plugins.mysql.instance'''

Install Oracle client on Ubuntu

2017-05-26T15:39:00Z

78.45.88.190: Oracle client on Ubuntu

* Go to: http://www.oracle.com/technetwork/database/features/instant-client/index.html

* Scroll to Downloads and click on: Instant Client for Linux x86-64

* Accept the license agreement and find the x64.rpm files containing the following string:
** basic
** sqlplus
** devel

* Install the rpm to deb conversion tool:

'''apt-get install alien'''

* install the 3 packages in the following order:

'''alien -i oracle-instantclient12.1-sqlplus-12.1.0.2.0-1.x86_64.rpm'''

'''alien -i oracle-instantclient12.1-basic-12.1.0.2.0-1.x86_64.rpm'''

'''alien -i oracle-instantclient12.1-devel-12.1.0.2.0-1.x86_64.rpm'''

* The above file names will vary according to the version. The alien tool will generate and save the respective .deb file and install the package

* Install the required library:

'''apt-get install libaio1'''

* Add the oracle client library to linker path:

* Find the path for the Oracle libraries. It should be in /usr/lib/oracle/12.1/client

You are looking for a lib folder inside.

* create (or edit) the file /etc/ld.so.conf.d/oracle.conf

* Add the folder you found to the above file

* refresh the library paths:

'''ldconfig'''

* run the client and attempt to connect to the database:

'''sqlplus username/password@//dbhost:1521/SID'''

* Install the required package - OCI8 for PHP:

'''apt-get install pear php7.0-dev'''

* Attempt to install the PHP extension:

'''pecl install oci8'''

The install script will autodetect the oracle client path

* Add the extension=oci8.so line to your /etc/php/7.0/fpm/php.ini file

* Restart the FPM service:

'''service php7.0-fpm restart'''

Complete step-by-step guides

2017-05-26T15:31:29Z

78.45.88.190: Adding new article

Step-by-step guides.

== Please choose from the following ==
* [[Add new joinee]]
* [[Add new server]]
<nowiki>======================================</nowiki>
* [[Add new user to GitLab]]
* [[Add new server to GitLab AutoDeploy]]
* [[Convert the SVN repository to GitLab]]
* [[Install Oracle client on Ubuntu]]
* [[Remove NewRelic agent]]

Remove NewRelic agent

2017-05-26T15:30:46Z

78.45.88.190: Font change

====* For the main service:====
/etc/init.d/newrelic-sysmond stop

apt-get --purge remove newrelic-sysmond

====* For the PHP agent:====
newrelic-install purge

apt-get --purge remove newrelic-php5-common

dpkg -l | grep newrelic

(nothing should show when you run the above, if anything, proceed to manually removing the remaining services)

service nginx restart

service php7.0-fpm restart

====* For MySQL agent:====

cd /root/newrelic-npi

./npi stop com.newrelic.plugins.mysql.instance

./npi remove-service com.newrelic.plugins.mysql.instance

./npi remove com.newrelic.plugins.mysql.instance

Remove NewRelic agent

2017-05-26T15:29:36Z

78.45.88.190: Uninstalling NewRelic Agent - step by step

* For the main service:
/etc/init.d/newrelic-sysmond stop

apt-get --purge remove newrelic-sysmond

* For the PHP agent:
newrelic-install purge

apt-get --purge remove newrelic-php5-common

dpkg -l | grep newrelic

(nothing should show when you run the above, if anything, proceed to manually removing the remaining services)

service nginx restart

service php7.0-fpm restart

* For MySQL agent:

cd /root/newrelic-npi

./npi stop com.newrelic.plugins.mysql.instance

./npi remove-service com.newrelic.plugins.mysql.instance

./npi remove com.newrelic.plugins.mysql.instance

Complete step-by-step guides

2017-05-26T15:25:30Z

78.45.88.190: Add new article

Add new server to GitLab AutoDeploy

2017-03-10T11:52:02Z

78.45.88.190: permissions

If not mentioned otherwise, the following values are variables and will change from project to project (or server to server):

* dev-server - Git branch name, usually following the name of the server which the files will be deployed to (can be uat-server or live-server, etc)
* the /var/www/html path is just an example, this will be the root folder of the website we want to deploy to (from nginx/apache sites-enabled)
* the <nowiki>https://gitlab.apoyar.eu/somepath</nowiki> will be the url to the project in question - to be obtained from GitLab

==== And now the steps: ====

* Install Git AutoDeploy
** apt-get install software-properties-common
** add-apt-repository ppa:olipo186/git-auto-deploy
** apt-get update
** apt-get install git-auto-deploy
* copy the settings file from Dev: /etc/git-auto-deploy.conf.json
* amend the file contents: url to access (GitLab project), active branch required
* open the /etc/init.d/git-auto-deploy file and make the daemon running as www-data:
** DAEMON_UID="www-data"
** DAEMON_GID="www-data"
* Run systemctl daemon-reload after you’ve made the changes above
* A reboot may be required here
* Make sure the Deploy Bot account has access to the project and is made a Master
* Backup the current website contents: cp -R /var/www/html/ /home/neal/backup/
* Delete the website contents, including the git part (if present):
** cd /var/www/html
** rm –rf *
** rm –rf .git .gitignore .htaccess
* Before you do the below process, you may need to check the owner of the /var/log/git-auto-deploy.log file. It should be www-data. Also check the /var/run/git-auto-deploy/git-auto-deploy.pid If not, change them:
** chown www-data:www-data /var/log/git-auto-deploy.log
** chown www-data:www-data /var/run/git-auto-deploy/git-auto-deploy.pid
* Start the daemon in foreground, but as the user www-data: sudo -H -u www-data bash -c 'git-auto-deploy --pid-file /var/run/git-auto-deploy/git-auto-deploy.pid --log-file /var/log/git-auto-deploy.log --config /etc/git-auto-deploy.conf.json'
* Once static, Ctrl-C the process
* It should create the tree
* Check the contents of the /var/www/html/.gitignore file
* If not present, create one, own it by www-data and push back to the server. If present, leave out the 3 next steps
** vi .gitignore
** chown www-data:www-data .gitignore
** git push origin dev-server
* Copy the ignored files listed above from backup
* Clear the cache and push changes to GitLab:
** cd /var/www/html
** git rm –rf –cached .
** git add .
** git status
** if the above command says nothing to commit, you can leave out the 2 next steps
** git commit
** git push origin dev-server
* Make sure all objects in the .git/objects folder are owned by www-data: chown –R www-data:www-data *
* Change the Deploy Bot to be a Reporter in GitLab
* Start the service: service git-auto-deploy start
* Observe the log file: tail –f /var/log/git-auto-deploy.log
* If you don’t see anything in the log and the foreground app runs fine, reboot the server
* Add the <nowiki>http://hostname:8001</nowiki> as webhook to GitLab project in question: <nowiki>https://gitlab.apoyar.eu/root/bleckmann/settings/integrations</nowiki>
* Reboot the server and check whether it’s listening on port 8001: netstat -anp

Add new server to GitLab AutoDeploy

2017-03-10T11:49:53Z

78.45.88.190: Amending instructions, permissions change.

If not mentioned otherwise, the following values are variables and will change from project to project (or server to server):

* dev-server - Git branch name, usually following the name of the server which the files will be deployed to (can be uat-server or live-server, etc)
* the /var/www/html path is just an example, this will be the root folder of the website we want to deploy to (from nginx/apache sites-enabled)
* the <nowiki>https://gitlab.apoyar.eu/somepath</nowiki> will be the url to the project in question - to be obtained from GitLab

==== And now the steps: ====

* Install Git AutoDeploy
** apt-get install software-properties-common
** add-apt-repository ppa:olipo186/git-auto-deploy
** apt-get update
** apt-get install git-auto-deploy
* copy the settings file from Dev: /etc/git-auto-deploy.conf.json
* amend the file contents: url to access (GitLab project), active branch required
* open the /etc/init.d/git-auto-deploy file and make the daemon running as www-data:
** DAEMON_UID="www-data"
** DAEMON_GID="www-data"
* Run systemctl daemon-reload after you’ve made the changes above
* A reboot may be required here
* Make sure the Deploy Bot account has access to the project and is made a Master
* Backup the current website contents: cp -R /var/www/html/ /home/neal/backup/
* Delete the website contents, including the git part (if present):
** cd /var/www/html
** rm –rf *
** rm –rf .git .gitignore .htaccess
* Before you do the below process, you may need to check the owner of the /var/log/git-auto-deploy.log file. It should be www-data. If not, change it:
** chown www-data:www-data /var/log/git-auto-deploy.log
* Start the daemon in foreground, but as the user www-data: sudo -H -u www-data bash -c 'git-auto-deploy --pid-file /var/run/git-auto-deploy/git-auto-deploy.pid --log-file /var/log/git-auto-deploy.log --config /etc/git-auto-deploy.conf.json'
* Once static, Ctrl-C the process
* It should create the tree
* Check the contents of the /var/www/html/.gitignore file
* If not present, create one, own it by www-data and push back to the server. If present, leave out the 3 next steps
** vi .gitignore
** chown www-data:www-data .gitignore
** git push origin dev-server
* Copy the ignored files listed above from backup
* Clear the cache and push changes to GitLab:
** cd /var/www/html
** git rm –rf –cached .
** git add .
** git status
** if the above command says nothing to commit, you can leave out the 2 next steps
** git commit
** git push origin dev-server
* Make sure all objects in the .git/objects folder are owned by www-data: chown –R www-data:www-data *
* Change the Deploy Bot to be a Reporter in GitLab
* Start the service: service git-auto-deploy start
* Observe the log file: tail –f /var/log/git-auto-deploy.log
* If you don’t see anything in the log and the foreground app runs fine, reboot the server
* Add the <nowiki>http://hostname:8001</nowiki> as webhook to GitLab project in question: <nowiki>https://gitlab.apoyar.eu/root/bleckmann/settings/integrations</nowiki>
* Reboot the server and check whether it’s listening on port 8001: netstat -anp

Active Directory

2017-02-15T17:18:32Z

78.45.88.190: GP link added.

Apoyar is running a Windows 2008 R2 Active Directory domain.

All Windows servers, apart from the Web IIS are joined and running under it.

It serves:

* User management
* File permissions (where applicable)
* MS SQL central access and management

Apart from the above, it contains the user database for non-windows applications (even on windows machines), where applicable:

* Both L2TP and OpenVPN user logins
* Secure ftp access logins
* VSphere logins and roles (VMWare)

The only management involves:

* Adding and amending DNS records
* User management
* Security groups/ACLs (managed from Mercury)

Please use the DNS snap-in, ADUC and [[Group Policies|Group Policy management]]

Add new user to GitLab

2017-02-15T13:32:04Z

78.45.88.190: new GitLab user: adding page.

* Browse to https://gitlab.apoyar.eu
* Login as root:5tarry.Night

Convert the SVN repository to GitLab

2017-02-13T16:27:44Z

78.45.88.190: Minor cosmetic changes.

'''Following this guide allows one to convert a specific SVN repository to a GitLab project, including turning SVN revisions to commits and the participants to GitLab users.'''

* SSH to phobos.apoyar This server is reserved for maintenance/support and has all relevant software installed.
* Obtain the SVN url of the repository in question. The one used has already been converted, use it as an example.
* cd to /home/neal/git/svn This is an empty folder reserved for the conversion process:
** git svn clone --no-minimize-url <nowiki>http://saturn:8008/svn/Apoyar/BMAPI/BleckmannApi</nowiki> .
* Examine the results in the folder. Use git status to check.
* Create new project on GitLab. Copy its url. In this example, the BleckmannAPI project has been used, please use yours.
* Push to GitLab:
** git remote add origin <nowiki>https://gitlab.apoyar.eu/root/BleckmannAPI.git</nowiki>
** git push –u origin master
* GitLab will now show all commits and files of the repository. Only master branch will exist
* if there is a non-existing user(s) in commits:
** Open the project in GitLab
** Browse through the commits
** Copy and paste all user emails you found to text file
** Make the master branch unprotected
** Copy the git-author-rewrite.sh file (residing in the parent folder: /home/neal/git/) to the current svn folder.
** '''Edit the file and replace the following values with their current ones:'''.
*** OLD_EMAIL=" "
*** CORRECT_NAME=" "
*** CORRECT_EMAIL
** Run ./git-author-rewrite.sh
** Push the changes over:
*** git push --force --tags origin 'refs/heads/*'
** check whether it’s OK
** delete the backup:
*** git update-ref -d refs/original/refs/heads/master
** if there are more usernames just repeat the steps from '''Edit the file and replace the values in question'''.

Convert the SVN repository to GitLab

2017-02-13T16:21:52Z

78.45.88.190: SVN to Git - adding content

==Following this guide allows one to convert a specific SVN repository to a GitLab project, including turning SVN revisions to commits and the participants to GitLab users.==

* SSH to phobos.apoyar This server is reserved for maintenance/support and has all relevant software installed.
* Obtain the SVN url of the repository in question. The one used has already been converted, use it as an example.
* cd to /home/neal/git/svn This is an empty folder reserved for the conversion process:
** git svn clone --no-minimize-url http://saturn:8008/svn/Apoyar/BMAPI/BleckmannApi .
* Examine the results in the folder. Use git status to check.
* Create new project on GitLab. Copy its url. In this example, the BleckmannAPI project has been used, please use yours.
* Push to GitLab:
** git remote add origin https://gitlab.apoyar.eu/root/BleckmannAPI.git
** git push –u origin master
* GitLab will now show all commits and files of the repository. Only master branch will exist
* if there is a non-existing user(s) in commits:
** Open the project in GitLab
** Browse through the commits
** Copy and paste all user emails you found to text file
** Make the master branch unprotected
** Copy the git-author-rewrite.sh file (residing in the parent folder: /home/neal/git/) to the current svn folder.
** Edit the file and replace the following values with their current ones:.
*** OLD_EMAIL=" "
*** CORRECT_NAME=" "
*** CORRECT_EMAIL
** Run ./git-author-rewrite.sh
** Push the changes over:
*** git push --force --tags origin 'refs/heads/*'
** check whether it’s OK
** delete the backup:
*** git update-ref -d refs/original/refs/heads/master
** if there are more usernames just repeat the steps from [[#edit_script|Edit the file and replace the values in question]].

Complete step-by-step guides

2017-02-13T15:58:59Z

78.45.88.190: New guide - SVN to Git conversion

Complete step-by-step guides

2017-02-09T11:31:26Z

78.45.88.190: Formatting of subpabe

Add new server to GitLab AutoDeploy

2017-02-09T11:29:55Z

78.45.88.190: Add new server to GitLab AutoDeploy - added content

If not mentioned otherwise, the following values are variables and will change from project to project (or server to server):

* dev-server - Git branch name, usually following the name of the server which the files will be deployed to (can be uat-server or live-server, etc)
* the /var/www/html path is just an example, this will be the root folder of the website we want to deploy to (from nginx/apache sites-enabled)
* the <nowiki>https://gitlab.apoyar.eu/somepath</nowiki> will be the url to the project in question - to be obtained from GitLab

==== And now the steps: ====

* Install Git AutoDeploy
** apt-get install software-properties-common
** add-apt-repository ppa:olipo186/git-auto-deploy
** apt-get update
** apt-get install git-auto-deploy
* copy the settings file from Dev: /etc/git-auto-deploy.conf.json
* amend the file contents: url to access (GitLab project), active branch required
* open the /etc/init.d/git-auto-deploy file and make the daemon running as www-data:
** DAEMON_UID="www-data"
** DAEMON_GID="www-data"
* Run systemctl daemon-reload after you’ve made the changes above
* A reboot may be required here
* Make sure the Deploy Bot account has access to the project and is made a Master
* Backup the current website contents: cp -R /var/www/html/ /home/neal/backup/
* Delete the website contents, including the git part (if present):
** cd /var/www/html
** rm –rf *
** rm –rf .git .gitignore .htaccess
* Start the daemon in foreground, but as the user www-data: sudo -H -u www-data bash -c 'git-auto-deploy --pid-file /var/run/git-auto-deploy/git-auto-deploy.pid --log-file /var/log/git-auto-deploy.log --config /etc/git-auto-deploy.conf.json'
* Once static, Ctrl-C the process
* It should create the tree
* Check the contents of the /var/www/html/.gitignore file
* If not present, create one, own it by www-data and push back to the server. If present, leave out the 3 next steps
** vi .gitignore
** chown www-data:www-data .gitignore
** git push origin dev-server
* Copy the ignored files listed above from backup
* Clear the cache and push changes to GitLab:
** cd /var/www/html
** git rm –rf –cached .
** git add .
** git status
** if the above command says nothing to commit, you can leave out the 2 next steps
** git commit
** git push origin dev-server
* Make sure all objects in the .git/objects folder are owned by www-data: chown –R www-data:www-data *
* Change the Deploy Bot to be a Reporter in GitLab
* Start the service: service git-auto-deploy start
* Observe the log file: tail –f /var/log/git-auto-deploy.log
* If you don’t see anything in the log and the foreground app runs fine, reboot the server
* Add the <nowiki>http://hostname:8001</nowiki> as webhook to GitLab project in question: <nowiki>https://gitlab.apoyar.eu/root/bleckmann/settings/integrations</nowiki>
* Reboot the server and check whether it’s listening on port 8001: netstat -anp

Add new server to GitLab AutoDeploy

2017-02-09T11:04:08Z

78.45.88.190: Created page with "If not mentioned otherwise, the following values are variables and will change from project to project (or server to server):"

If not mentioned otherwise, the following values are variables and will change from project to project (or server to server):

Complete step-by-step guides

2017-02-09T11:01:34Z

78.45.88.190: New category - GitLab AutoDeploy

Step-by-step guides.

== Please choose from the following ==
* [[Add new joinee]]
* [[Add new server]]
======================================
* [[Add new user to GitLab]]
* [[Add new server to GitLab AutoDeploy]]

Group Policies

2017-02-06T11:11:33Z

78.45.88.190:

The Group Policies determine global settings and set behaviour either for single servers or for Server groups.

The management console is accessible from [[Mercury]]. The below list contains their names and description, listed as they appear in the console:

EasyPrint order - Terminal Servers

Sets EasyPrint precedence over the Native printer driver (one which has to mirror the connected user's machine printer driver)

Freelancer lockdown - Terminal servers

Creates a 'bare' Desktop and no access to shared drives - used for people who only need to login to TS and use a single application with access to internet.

Idle session logoff

Makes sure all disconnected sessions (the user only clicks the cross at the top of the screen) are gracefully logged of after 6 hours.

Local Admin password expiry

There are cases where we need to use the server's local admin login for maintenance (even if the server is a member of domain). This group policy makes sure the server's local Administrator account's password never expires.

No pinned Server Manager and PowerShell

This is to fix a known Microsoft issue where any newly added Remote Desktop user has Server Manager and PowerShell shortcuts pinned to his quick launch. Not, if using this GP.

Prohibited TS users

Restricts network and resource access to Kiosk RDP users and 3rd party contractors.

VNC Ctrl-Alt-Del

Disables UAC (user account control) above the VNC service. This allows a user to send the Ctrl-Alt-Del from his remote session without getting blocked by UAC.

WSUS

Sets the apply time, frequency and address of the central Windows Update server (currently hosted on Abydos). All servers report and pull data from this machine.

Group Policies

2017-01-25T17:00:38Z

78.45.88.190:

Group Policies

2017-01-25T17:00:22Z

78.45.88.190:

Group Policies

2017-01-25T17:00:07Z

78.45.88.190: Group Policies - first batch of data

Group Policies

2017-01-25T16:48:24Z

78.45.88.190: GP - added header

The Group Policies determine global settings and set behaviour either for single servers or for Server groups.

The below list contains their names and description:

User and Group management

2017-01-25T16:45:44Z

78.45.88.190: Added category Group policies

Users and Groups.

== Please choose from the following ==
* [[Windows (Active Directory) users]]
* [[Windows Active Directory groups and their infrastructure roles]]
* [[*NIX and other groups]]
* [[Group Policies]]

User and Group management

2017-01-24T08:25:29Z

78.45.88.190: Users and Groups subcategories.

Infrastructure

2017-01-24T08:23:23Z

78.45.88.190: User and Group management category added.

Apoyar complete infractructure description.

== Please choose from the following ==
* [[Active Directory]]
* [[Servers by name and role]]
* [[User and Group management]]

Bleckmann API

2017-01-23T10:56:43Z

78.45.88.190: Modules category added.

Modules.

== Please choose from the following ==
* [[Module 1]]
* [[Module 2]]
* [[Module 3]]
* [[Module 4]]

Developer guides

2017-01-23T10:55:49Z

78.45.88.190: bleckmann API category added

Developer guides.

== Please choose from the following ==
* [[bleckmann API]]

Main Page

2017-01-23T10:54:22Z

78.45.88.190: Added dev guides part.

Complete step-by-step guides

2017-01-17T17:43:22Z

78.45.88.190: Add specific guides

Step-by-step guides.

== Please choose from the following ==
* [[Add new joinee]]
* [[Add new server]]
* [[Add new user to GitLab]]

Main Page

2017-01-17T17:41:44Z

78.45.88.190: Adding Guides start page

Infrastructure

2017-01-13T16:12:13Z

78.45.88.190: Amending the page title.

Apoyar complete infractructure description.

== Please choose from the following ==
* [[Active Directory]]
* [[Servers by name and role]]