projectoperations projectoperations

Credentials Management

This guide describes setting out a credential storage mechanism that is shared between the root account, aka releasr, and jenkins account. It intends to support and persist access credentials that are needed when authenticating with external services, primarily Docker Hub, for users wishing to access remote Docker images as part of their containerised services.

The following diagram aims to describe the control flow this setup intends to support.

This guide is a first, and a tad complicated sorry, pass at setting this up. It got us over the line for a couple of uses cases as well as working with automated build jobs.

Chrome has decided that what they deem powerful web platform features such as Geolocation, Device motion / orientation, getUserMedia etc can no longer run on "Insecure Origins", HTTP (non-HTTPS) being one of them. Read more

So if you want to use these features in development and you are testing on a mobile via the IP of your computer, you now need to be serving the content over HTTPS for it to work.

Generate local SSL certificate

First check if you need to install openssl with which openssl. If nothing comes up run brew install openssl to install openssl with Brew.

openssl genrsa -des3 -passout pass:x -out localhost.pass.key 2048
openssl rsa -passin pass:x -in localhost.pass.key -out localhost.key

Project Ideas

Ok. I'm going to list off some ideas for projects. You will have to determine if any particular idea is good enough to include in a portfolio. These aren't creative ideas. They likely already exist. Some are way too advanced while others are simplistic.

I will recommend to post any project you make to github and make a github project page for it. Explain in as much detail as possible how you made it, how it can be improved etc. Document it.

If you pick an advanced idea, setup a development roadmap and follow it. This will show some project management skills.

Another piece of advice for those who are design challenged. Use different front end frameworks and use different themes for those frameworks to provide appealing designs without looking like yet another bootstrap site.

Creating a new ASP NET Core Web API

Pre-requiside

Ensure that you have installed .NET Core in your machine.

Creating the project

Open a terminal window (e.g. Gitbash, linux terminal, mac terminal, etc) then change directory to your projects folder. Inside the folder, run dotnet new webapi -o -n command. Example: dotnet new webapi -o PCShop.Api-n PCShop.Api.

Running phpMyAdmin localy on the built in php server

make sure you have php 5.3+: run php -v
Download phpmyadmin (github or main website)
In the root directory, copy config.sample.inc.php > config.inc.php
Edit config.inc.php, set $cfg['Servers'][$i]['host'] to the ip address of your mysql server (probably localhost or 127.0.0.1)
In the root phpmyadmin directory run php -S localhost:8080
open in your browser: http://localhost:8080
log in by entering some valid credentials (a user you added or the root user)

Installing WSL (windows subsystem for linux)

Running the azure-team terraform make file to create your infrastructure may not work on a Windows machine. If you cannot get it to run, install a linux distribution where you will exectute the tf files. Setting up a distribution with all of the right dependencies does involve a bit of setup to get it configured properly. The following is a list of steps you'll need to complete:

Install WSL
Change the mount point from /mnt/c to /c
Install homebrew
Set up git credential manager
Install sqlcmd

Install WSL

Sample configuration.dsc.yaml files

These samples require the experimental configuration feature to be enabled. WinGet 1.5.863-preview or newer is required.

Add the following to your settings.json to enable this feature:

    "experimentalFeatures": {"dependencies": true, 
 "configuration": true

	{
	"workbench.colorTheme": "GreenSpace V",
	"workbench.iconTheme": "emoji-file-icons",
	"redhat.telemetry.enabled": true,
	"vs-kubernetes": {
	"vscode-kubernetes.helm-path.windows": "C:\\Users\\DevSupport\\.vs-kubernetes\\tools\\helm\\windows-amd64\\helm.exe",
	"vscode-kubernetes.kubectl-path.windows": "C:\\Users\\DevSupport\\.vs-kubernetes\\tools\\kubectl\\kubectl.exe",
	"vscode-kubernetes.minikube-path.windows": "C:\\Users\\DevSupport\\.vs-kubernetes\\tools\\minikube\\windows-amd64\\minikube.exe"
	},
	"oh-my-ins.setting.accounts": "jaychou,chiling,igeclouds",

	# See the following for references:
	# * http://www.metacircus.com/hacking/2011/02/18/play-git-like-a-violin.html
	# * http://cheat.errtheblog.com/s/git/
	# * http://pyrtsa.posterous.com/aligning-your-git-logs
	# * http://blog.apiaxle.com/post/handy-git-tips-to-stop-you-getting-fired/

	# Git >v1.7.10 lets you include external files
	# Put your user configuration in here, so it never
	# accidentally gets checked in
	[include]

	## Configuration options with # in front are not active and they were
	## valid at install time. Updating the package does not update this file
	## automatically.
	## Latest options listed at:
	## https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-config-template/gitlab.rb.template


	## Url on which GitLab will be reachable.
	## For more details on configuring external_url see:
	## https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/settings/configuration.md#configuring-the-external-url-for-gitlab