pvillega

APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "1";
APT::Periodic::AutocleanInterval "3";
APT::Periodic::Verbose "1";
APT::Periodic::Unattended-Upgrade "1";

pvillega

# See - https://docs.github.com/en/free-pro-team@latest/actions
name: App-build

# Triggers the workflow on push or pull request events, any branch, ignoring tags
on:
  push:
    branches:
      - master
    tags-ignore:
      - v*

pvillega

#
#DO droplet metadata intro + for DO-API
# [https://www.digitalocean.com/community/tutorials/an-introduction-to-droplet-metadata#how-to-retrieve-droplet-metadata#digitalocean-api]
#
#intro to cloud-config scripting  (source of following examples)
# [https://www.digitalocean.com/community/tutorials/an-introduction-to-cloud-config-scripting]
#
#howto
# [https://www.digitalocean.com/community/tutorials/how-to-use-cloud-config-for-your-initial-server-setup]
#

pvillega

Install

Follow the steps below to install Team City on Ubuntu with Nginx as the proxy for port 80.

Install Team City:

# will install on port 8111

sudo wget -c https://gist.githubusercontent.com/simoneb/cedac22c58ad0a9e37cddd84abe975a3/raw/teamcity-install.sh -O /tmp/teamcity-install.sh

pvillega

"Specifying distributed systems with TLA+"

Elevator pitch:

Learn how to use TLA+ to study, design, and specify your algorithms. This workshop is designed to teach you about TLA+ from the ground up. We will start with simple distributed algorithms and slowly move toward more complex ones. Knowledge you gain can be immediatly applied at work the day after the workshop

Description:

TLA+ is a formal specification language developed by Leslie Lamport, designed to specify, model, document, and verify concurrent systems. It empowers your ability to clearly specify your design choices by using a formal specification, but even more importantly it can also formally verify that your design choice is correct — meaning that it is both safe (does not break any rules) and live (over time it converges toward the result).

pvillega

Some of these practices might be based on wrong assumptions and I'm not aware of it, so I would appreciate any feedback.

1. avoiding some dependency conflicts:

   • add sbt-explicit-dependencies to the project/plugins.sbt
   • run undeclaredCompileDependencies and add any missing explicit dependencies to libraryDependencies of each sub-project
   • (optionally) run unusedCompileDependencies and remove some obvious unused libraries. This has false positives, so ; reload; Test/compile after each change and ultimately run all tests to see that it didn't break anything
   • (optionally) add undeclaredCompileDependenciesTest to the CI pipeline, so that it will fail if you have some undeclared dependencies

2. keeping dependencies up to date and resolving conflicts:

• install sbt-updates globally in your ~/.sbt/{0.13,1.0}/plugins/plugins.sbt

pvillega

Last week in Slack there was a question about ReasonML resources. Here you can find some links that have been very handy to start implementing my first ReasonML UI.

Basic reference

• BuckleScript: https://bucklescript.github.io/docs/en/what-why

• ReasonML: https://reasonml.github.io/docs/en/what-and-why

• ReasonReact: https://reasonml.github.io/reason-react/docs/en/what-and-why

• Book for reference: http://reasonmlhub.com/exploring-reasonml/toc.html

pvillega

/**
I've read http://degoes.net/articles/zio-environment and I am confused. 
Note this may be me not understanding this, it wouldn't be the first time I miss the obvious point on something
But I wonder about the supossed benefits, and I am not sure I see them all.
Note that I am not trying to bash John's post, just understand what I am missing from it. 
Also, disclaimer, I like MTL but I am open to any improvements :)

Let's discuss the points raised as negative about Tagless Final first:
1) Knowledge ramp up:
As I see them, they are basic concepts to do FP in Scala. You'll hardly do FP without knowing (at a basic level) typeclasses.

pvillega

import freestyle._
import freestyle.implicits._
import freestyle.logging._
import freestyle.cache._
import freestyle.loggingJVM.implicits._

object all {
  // Some model classes for tthe example
  type Key       = String
  type AnswerMap = Map[Key, Answer[_]]

pvillega

// List of Strings you may want to use for testing in input fields, as they can cause unexpected behaviour. Input fields
// should either return validation errors or sanitize them.
// Using mostly Strings due to the way JVM manages Chars with Unicode.
// Based on https://github.com/minimaxir/big-list-of-naughty-strings - version 29th May 2017 - update as required

import org.scalacheck.Gen

trait NaughtyStringsList {

  val naughtyReservedStrings: Gen[String] = Gen.oneOf(