(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
#!/usr/bin/ruby | |
require 'rss' | |
# Usage | |
# $ ./railscasts.rb http://railscasts.com/subscriptions/YOURRAILSCASTRSS/\/ | |
# episodes.rss | |
# OR | |
# $ ./railscasts.rb | |
p 'Downloading rss index' |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
You can ssh into the VM by finding the IP (from kubectl config view) and using username "docker" password "tcuser": | |
ssh [email protected] |
function (user, context, callback) { | |
var namespace = 'https://tojs.io/'; | |
context.accessToken[namespace + 'user_authorization'] = { | |
groups: user.app_metadata.groups, | |
roles: user.app_metadata.roles, | |
permissions: user.app_metadata.permissions | |
}; | |
return callback(null, user, context); | |
} |
/** | |
* options for JCRAuthenticationModule module: | |
* realm: to restrict the login to a certain realm | |
* use_realm_callback: to allow the GUI to pass the realm to login into | |
* skip_on_previous_success: if true the login is scipped if a former module proceeded a successfull login | |
* | |
* example: | |
* info.magnolia.jaas.sp.jcr.JCRAuthenticationModule requisite realm=public; | |
* info.magnolia.jaas.sp.jcr.JCRAuthenticationModule requisite realm=admin skip_on_previous_success=true; | |
*/ |
package ciphers | |
import ( | |
"crypto/rand" | |
"crypto/rsa" | |
"crypto/sha512" | |
"crypto/x509" | |
"encoding/pem" | |
"log" | |
) |
/* | |
Git env vars you might need in jenkins | |
Jenkins ENV Reference: | |
env.GIT_COMMIT: the commit sha of the current build | |
env.BRANCH_NAME: the branch name OR tag name of the current build, when it exists | |
env.GIT_BRANCH: same as BRANCH_NAME | |
env.TAG_NAME: the tag name of the current build, when it exists | |
*/ | |
// stash and unstash |
server { | |
listen 80; | |
server_name www.example.com example.com; | |
# Redirect all traffic to SSL | |
rewrite ^ https://$server_name$request_uri? permanent; | |
} | |
server { | |
listen 443 ssl default_server; |
Running your ASP.NET Core (or other) application in Docker using SSL should not be an overwhelming task. These steps should do the trick.
Run the following steps from a Linux terminal (I used WSL or WSL2 on Windows from the Windows Terminal).
It should look something like the content below; call it my-site.conf
or something like that.