<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>linux on Ampretia:Dev</title><link>https://ampretia.co.uk/tags/linux/</link><description>Recent content in linux on Ampretia:Dev</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><lastBuildDate>Fri, 19 Jul 2019 08:17:23 +0000</lastBuildDate><atom:link href="https://ampretia.co.uk/tags/linux/index.xml" rel="self" type="application/rss+xml"/><item><title>Getting setup for development (CentOS)</title><link>https://ampretia.co.uk/oldposts/2019-07-19-getting-setup-for-development-centos/</link><pubDate>Fri, 19 Jul 2019 08:17:23 +0000</pubDate><guid>https://ampretia.co.uk/oldposts/2019-07-19-getting-setup-for-development-centos/</guid><description>At work we&amp;rsquo;ll often do &amp;lsquo;group testing&amp;rsquo; sessions or &amp;lsquo;internal hackathons&amp;rsquo;. What struck me about the last one was that setting up your development environment can surprisingly tricky, especailly if it&amp;rsquo;s for a style of development or langage you don&amp;rsquo;t generally use.
TL;DR: gist of commands
What are we developing for? The setup we are going for here, is a Node.js and Java environment using VSCode - with a view to using the IBM Blockchain Platform extension for writing applications and smart contracts for Hyperledger Fabric</description></item></channel></rss>