Bence Varga vbence86

Installing environment dependencies

In order to test the tickets above you have to have the following services up and running locally.

Content-Service
Eagle Webapp
Nginx serving the Boxtop-Front-End resources

Installation steps

How to test your 'localhost' against a mobile device

Link the remote device to your machine

Make sure your machine is connected to the Pbx SWK
Connect the target device to the Pbx SWK

Get your remote IP address

Open a terminal and type the following

ifconfig

Register a member

Send an HTTP POST Request as follows

URL

https://babel-api-0-elb-external.babeltest.photobox.com/v2/Community/Member/New

HTTP Headers

Fetch a session

Babel Endpoint

https://babel-api-0-elb-external.babeltest.photobox.com/v2/Community/Session

Headers

X-Babel-Client: boxtop
Content-Type: application/json

Release process of Smash-website

Changes are pushed to master (either manually or through merging a Pull Request to master)
Github webhook is triggered
Jenkins job is started
Docker image is created
Docker container is deployed on http://smash-website-development.api.photobox.com/home

Check the release state

Go to Jenkins http://ci.core.photobox.com/
Request credentials from the Webops-team if need be

How npm 5+ works with package-lock

Having had hard times understanding how exactly npm processes package-lock.json and at what stages it is being updated, I put a little guide together to sort of reverse engineer in what way the locked dependencies are updated. This is not going to be an exhausting research about every aspects of npm dealing with these locked dependecies, but rather a very quick step-by-step guide that lines up my findings.

Preparations

To get the ball rolling, I prepared a rather simple React boilerplate project to experiment with. It incorporates the very basics needed to generate a "Hello React!" application. This will perfectly make it for our little demonstration.

Let's swiftly take a glimpse through the fundamental project files.

app.js

	git clone https://github.com/vbence86/alto-analytics-js-test.git
	cd alto-analytics-js-test
	npm install
	npm run build
	npm start