Thanks to new resources (postgresql_default_priviledges) and some fixes Terraform can now add new databases and manage ownership / access to them.
This example creates new database and two users. You can use owner to create new tables and run migrations and user for normal read/write access to database.
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.
| // originally by @SethTisue, see http://stackoverflow.com/questions/40622878/how-do-i-tell-sbt-to-use-a-nightly-build-of-scala-2-11-or-2-12/40622879#40622879 | |
| resolvers += "nightlies" at "https://scala-ci.typesafe.com/artifactory/scala-release-temp/" | |
| scalaVersion := { | |
| val propsUrl = new URL("https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-bootstrap/lastSuccessfulBuild/artifact/jenkins.properties/*view*/") | |
| val props = new java.util.Properties | |
| props.load(propsUrl.openStream) | |
| props.getProperty("version") | |
| } | |
| scalaBinaryVersion := "2.12" |
A curated list of AWS resources to prepare for the AWS Certifications
A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.
| 1. No way of reusing task output in main play. | |
| 2. Cannot specify multiple fail_when statements. | |
| 3. [*] A play is atomic, i.e. I can't take the output from a command, parse its json then act on it. I need to create an intermediary fact containing the json dict then use that in another play. It's tedious. | |
| 4. If you're missing a variable in a variable file, Ansible won't fail to parse it. It will just tell you "VARIABLE IS NOT DEFINED!," which is ambiguous | |
| 5. Doing anything "complicated" (like looping within a loop for deeply nested Ansible variables) is right out. | |
| 6. selectattr doesn't actually do what you think it does! | |
| 7. Missing vars within tasks or roles can lead to very very VERY cryptic errors | |
| 8. So you can't set booleans with set_facts without casting......... https://github.com/ansible/ansible/issues/5463 | |
| 9. It would be great if I could say something like: |
| { | |
| "handlers": { | |
| "metrics": { | |
| "type": "set", | |
| "handlers": ["influxdb_udp"] | |
| }, | |
| "influxdb_udp": { | |
| "type": "udp", | |
| "mutator": "influxdb_line_protocol", | |
| "socket": { |
| package com.thoughtworks.futureeither | |
| import concurrent.{Await, Future} | |
| import scala.concurrent.ExecutionContext.Implicits.global | |
| import concurrent.duration.FiniteDuration | |
| import java.util.concurrent.TimeUnit | |
| class FutureEither[L, R](private val future: Future[Either[L, R]]) { | |
| def flatMap[R2](block: R => FutureEither[L, R2]): FutureEither[L, R2] = { |
One of the goals of Play2 architecture is to provide a programming model for what is called Realtime Web Applications.
Realtime Web Applications are applications that make use of Websockets, Server Sent Events, Comet or other protocols offering/simulating an open socket between the browser and the server for continuous communication. Basically, these applications let users work with information as it is published - without having to periodically ping the service.
There are quite a few web frameworks that target the development of this type of application: but usually the solution is to simply provide an API that allows developers to push/receive messages from/to an open channel, something like:
