j1_template_mde 2018.4.10

data/lib/starter_web/_plugins/simple_search_filter.rb

@@ -0,0 +1,33 @@
+# ------------------------------------------------------------------------------
+#  ~/_plugins/simple_search_filter.rb
+#  Liquid filter's to be used with JekyllSimple Search
+#
+#  Product/Info:
+#  http://jekyll.one
+#
+#  Copyright (C) 2019 Juergen Adams
+#
+#  J1 Template is licensed under the MIT License.
+#  See: https://github.com/jekyll-one/j1_template_mde/blob/master/LICENSE
+#
+# ------------------------------------------------------------------------------
+
+module Jekyll
+  module CharFilter
+    def remove_chars(input)
+      input.gsub! '\\','\'
+      input.gsub! /\t/, '    '
+      input.strip_control_and_extended_characters
+    end
+  end
+end
+
+Liquid::Template.register_filter(Jekyll::CharFilter)
+
+class String
+  def strip_control_and_extended_characters()
+    chars.each_with_object("") do |char, str|
+      str << char if char.ascii_only? and char.ord.between?(32,126)
+    end
+  end
+end

data/lib/starter_web/_plugins/symlink_watcher.rb

@@ -0,0 +1,53 @@
+# ------------------------------------------------------------------------------
+#  ~/_plugins/symlink_watcher
+#  jekyll-watch extension to listen for changes in symlinked folders
+#
+#  Product/Info:
+#  https://github.com/willnorris/willnorris.com/tree/master/src/_plugins/
+#  https://jekyll-one.com
+#
+#  Copyright (C) 2002-2014 Will Norris
+#  Copyright (C) 2019 Juergen Adams
+#
+#  symlink_watcher is licensed under the  MIT license
+#  See: https://github.com/willnorris/willnorris.com/blob/master/LICENSE
+#  J1 Template is licensed under the MIT License.
+#  See: https://github.com/jekyll-one/j1_template_mde/blob/master/LICENSE
+#
+# ------------------------------------------------------------------------------
+# NOTE:
+# The symlink_watcher plugin extends jekyll-watch to also listen for changes in
+# any symlinked sub-directories.
+#
+# For example, my _drafts directory is a symlink to a directory elsewhere on my
+# filesystem.  This plugin will cause jekyll to regenerate my site when any
+# files in my drafts folder change.
+# ------------------------------------------------------------------------------
+
+require "find"
+require "jekyll-watch"
+
+module Jekyll
+  module Watcher
+    def build_listener_with_symlinks(site, options)
+      src = options["source"]
+      dirs = [src]
+      Find.find(src).each do |f|
+        next if f == "#{src}/_drafts" and not options["show_drafts"]
+        # TODO: willnorris, filter ignored files
+        dirs << f if File.directory?(f) and File.symlink?(f)
+      end
+
+      require "listen"
+      Listen.to(
+        *dirs,
+        :ignore => listen_ignore_paths(options),
+        :force_polling => options['force_polling'],
+        &(listen_handler(site))
+      )
+    end
+
+    alias_method :build_listener_without_symlinks, :build_listener
+    alias_method :build_listener, :build_listener_with_symlinks
+  end
+end

data/lib/starter_web/_rack/Procfile.nginx

@@ -0,0 +1 @@
+web: bundle exec passenger start -p $PORT --engine=nginx --max-pool-size 3 

data/lib/starter_web/_rack/Procfile.webrick

@@ -0,0 +1 @@
+web: bundle exec jekyll server -P $PORT -H 0.0.0.0

data/lib/starter_web/_rack/Rakefile

@@ -0,0 +1,6 @@
+# This file is used to precompile the Jekyll site
+# for Heroku.
+
+task "assets:precompile" do
+  exec("bundle exec jekyll build")
+end

data/lib/starter_web/_rack/config.ru

@@ -0,0 +1,7 @@
+# Transforms J1 into a Web Application based on Rack and 
+# Sinatra using the OmniAuth software stack managed by Warden 
+# for authentication to create secured static J1 based web 
+# sites.
+#
+require 'j1_app'
+run J1App.site

data/lib/starter_web/_rack/dot.env

@@ -0,0 +1,48 @@
+# ------------------------------------------------------------------------------
+# The DOTENV file is used to set all environment variables used by
+# J1App to configure the run-time environment for Rack, Sinatra
+# and the credentials for ALL authentication strategies used by
+# Omniauth.
+#
+# NOTE: As this file contains confidential data, never publish this
+# file. A productive .env file should ALWAYS be excluded from any
+# source published to the public (e.g. Github).
+#
+# NOTE: For production use, rename this file to .env and configure
+# then ENV settings for your needs.
+
+# ------------------------------------------------------------------------------
+# Environmental settings
+#
+RACK_ENV=
+J1_SESSION_SECRET=
+
+# ------------------------------------------------------------------------------
+# OAuth settings
+
+# --------------------------------------------------------------------
+# FACEBOOK credentials
+#
+FACEBOOK_CLIENT_ID=
+FACEBOOK_CLIENT_SECRET=
+
+# --------------------------------------------------------------------
+# GITHUB credentials
+#
+GITHUB_CLIENT_ID=
+GITHUB_CLIENT_SECRET=
+GITHUB_MEMBERS=all
+
+# --------------------------------------------------------------------
+# PATREON credentials
+#
+PATREON_CLIENT_ID=
+PATREON_CLIENT_SECRET=
+
+# --------------------------------------------------------------------
+# TWITTER credentials
+#
+TWITTER_CLIENT_ID=
+TWITTER_CLIENT_SECRET=
+
+

data/lib/starter_web/_rack/dot.gitignore

@@ -0,0 +1,34 @@
+# Unneeded files created by a Jekyll build
+#
+_site/
+
+.sass-cache
+
+.jekyll-metadata
+
+# Never publish your sensitive personal and/or OAuth
+# data to any repo - not to public, not to any private one.
+.env
+
+# Unneeded files created by you or helper processes
+#
+
+Gemfile.lock
+
+tmp/
+
+\.idea/
+
+\.vscode/
+
+\.sass-cache/
+
+**/*.old
+
+**/*.tmp
+
+**/*.log
+
+**/*.swp
+
+**/*_backup

data/lib/starter_web/_rack/heroku.config_set

@@ -0,0 +1,12 @@
+GITHUB_MEMBERS
+heroku config:set -a DYNO_NAME J1_SESSION_SECRET=YYY GITHUB_CLIENT_ID=XXX GITHUB_CLIENT_SECRET=YYY GITHUB_MEMBERS=ZZZ
+
+GITHUB_ORG
+heroku config:set J1_SESSION_SECRET=YYY GITHUB_CLIENT_ID=XXX GITHUB_CLIENT_SECRET=YYY GITHUB_ORG_NAME=ZZZ
+
+GITHUB_TEAM
+heroku config:set J1_SESSION_SECRET=YYY GITHUB_CLIENT_ID=XXX GITHUB_CLIENT_SECRET=YYY GITHUB_TEAM_ID=ZZZ
+
+
+Example
+heroku config:set -a your-starter-app J1_SESSION_SECRET=abcdefg25c8f872b3944dc813dab24c123456789 GITHUB_CLIENT_ID=abcde46f828384012345 GITHUB_CLIENT_SECRET=abcdefg25c8f872b3944dc813dab24c123456789 GITHUB_MEMBERS=all

data/lib/starter_web/_rack/puma.rb

@@ -0,0 +1,200 @@
+#!/usr/bin/env puma
+
+# The directory to operate out of.
+#
+# The default is the current directory.
+#
+# directory '/u/apps/lolcat'
+
+# Use an object or block as the rack application. This allows the
+# config file to be the application itself.
+#
+# app do |env|
+#   puts env
+#
+#   body = 'Hello, World!'
+#
+#   [200, { 'Content-Type' => 'text/plain', 'Content-Length' => body.length.to_s }, [body]]
+# end
+
+# Load "path" as a rackup file.
+#
+# The default is "config.ru".
+#
+# rackup '/u/apps/lolcat/config.ru'
+
+# Set the environment in which the rack's app will run. The value must be a string.
+#
+# The default is "development".
+#
+# environment 'production'
+
+# Daemonize the server into the background. Highly suggest that
+# this be combined with "pidfile" and "stdout_redirect".
+#
+# The default is "false".
+#
+# daemonize
+# daemonize false
+
+# Store the pid of the server in the file at "path".
+#
+# pidfile '/u/apps/lolcat/tmp/pids/puma.pid'
+
+# Use "path" as the file to store the server info state. This is
+# used by "pumactl" to query and control the server.
+#
+# state_path '/u/apps/lolcat/tmp/pids/puma.state'
+
+# Redirect STDOUT and STDERR to files specified. The 3rd parameter
+# ("append") specifies whether the output is appended, the default is
+# "false".
+#
+# stdout_redirect '/u/apps/lolcat/log/stdout', '/u/apps/lolcat/log/stderr'
+# stdout_redirect '/u/apps/lolcat/log/stdout', '/u/apps/lolcat/log/stderr', true
+
+# Disable request logging.
+#
+# The default is "false".
+#
+# quiet
+
+# Configure "min" to be the minimum number of threads to use to answer
+# requests and "max" the maximum.
+#
+# The default is "0, 16".
+#
+# threads 0, 16
+
+# Bind the server to "url". "tcp://", "unix://" and "ssl://" are the only
+# accepted protocols.
+#
+# The default is "tcp://0.0.0.0:9292".
+#
+# bind 'tcp://0.0.0.0:9292'
+# bind 'unix:///var/run/puma.sock'
+# bind 'unix:///var/run/puma.sock?umask=0111'
+# bind 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert'
+
+# Instead of "bind 'ssl://127.0.0.1:9292?key=path_to_key&cert=path_to_cert'" you
+# can also use the "ssl_bind" option.
+#
+# ssl_bind '127.0.0.1', '9292', {
+#   key: path_to_key,
+#   cert: path_to_cert
+# }
+# for JRuby additional keys are required:
+# keystore: path_to_keystore,
+# keystore_pass: password
+
+# Code to run before doing a restart. This code should
+# close log files, database connections, etc.
+#
+# This can be called multiple times to add code each time.
+#
+# on_restart do
+#   puts 'On restart...'
+# end
+
+# Command to use to restart puma. This should be just how to
+# load puma itself (ie. 'ruby -Ilib bin/puma'), not the arguments
+# to puma, as those are the same as the original process.
+#
+# restart_command '/u/app/lolcat/bin/restart_puma'
+
+# === Cluster mode ===
+
+# How many worker processes to run.  Typically this is set to
+# to the number of available cores.
+#
+# The default is "0".
+#
+# workers 2
+
+# Code to run immediately before the master starts workers.
+#
+# before_fork do
+#   puts "Starting workers..."
+# end
+
+# Code to run in a worker before it starts serving requests.
+#
+# This is called everytime a worker is to be started.
+#
+# on_worker_boot do
+#   puts 'On worker boot...'
+# end
+
+# Code to run in a worker right before it exits.
+#
+# This is called everytime a worker is to about to shutdown.
+#
+# on_worker_shutdown do
+#   puts 'On worker shutdown...'
+# end
+
+# Code to run in the master right before a worker is started. The worker's
+# index is passed as an argument.
+#
+# This is called everytime a worker is to be started.
+#
+# on_worker_fork do
+#   puts 'Before worker fork...'
+# end
+
+# Code to run in the master after a worker has been started. The worker's
+# index is passed as an argument.
+#
+# This is called everytime a worker is to be started.
+#
+# after_worker_fork do
+#   puts 'After worker fork...'
+# end
+
+# Allow workers to reload bundler context when master process is issued
+# a USR1 signal. This allows proper reloading of gems while the master
+# is preserved across a phased-restart. (incompatible with preload_app)
+# (off by default)
+
+# prune_bundler
+
+# Preload the application before starting the workers; this conflicts with
+# phased restart feature. (off by default)
+
+# preload_app!
+
+# Additional text to display in process listing
+#
+# tag 'app name'
+#
+# If you do not specify a tag, Puma will infer it. If you do not want Puma
+# to add a tag, use an empty string.
+
+# Verifies that all workers have checked in to the master process within
+# the given timeout. If not the worker process will be restarted. This is
+# not a request timeout, it is to protect against a hung or dead process.
+# Setting this value will not protect against slow requests.
+# Default value is 60 seconds.
+#
+# worker_timeout 60
+
+# Change the default worker timeout for booting
+#
+# If unspecified, this defaults to the value of worker_timeout.
+#
+# worker_boot_timeout 60
+
+# === Puma control rack application ===
+
+# Start the puma control rack application on "url". This application can
+# be communicated with to control the main server. Additionally, you can
+# provide an authentication token, so all requests to the control server
+# will need to include that token as a query parameter. This allows for
+# simple authentication.
+#
+# Check out https://github.com/puma/puma/blob/master/lib/puma/app/status.rb
+# to see what the app has available.
+#
+# activate_control_app 'unix:///var/run/pumactl.sock'
+# activate_control_app 'unix:///var/run/pumactl.sock', { auth_token: '12345' }
+# activate_control_app 'unix:///var/run/pumactl.sock', { no_token: true }

data/lib/starter_web/_sass/README.md

@@ -0,0 +1,16 @@
+# J1 Template SASS sourcen
+
+The gem-based version of J1 comes with *no* CSS/SASS files. For developing
+respectively changing the CSS sources, go for the J1 Development System at:
+Github [jekyll-one/j1_template_mde](https://github.com/jekyll-one/j1_template_mde).
+
+To use CSS/SASS files for development with the RubyGem version, copy the
+folder scss out of the package `100_template_css` under `_sass` in the root
+directory of your Jekyll Web. 
+
+To enable SASS processing, edit the SASS documents in folder 
+*/assets/themes/j1/core/css*. The frontmatters of the SASS documents 
+enables Jekyll to read the SASS file to be transformed into CSS.
+To enble SASS processing, change the *five* dashes into *triple* dashes.
+
+

data/lib/starter_web/apps/calendar/index.adoc

@@ -0,0 +1,71 @@
+---
+layout:                                 page
+
+title:                                  J1 Calendar
+tagline:                                Integrated Cloud Calendar for your Web
+description:                            J1 Calendar
+
+toc:                                    true
+tags:                                   [ TeamUp, Calendar ]
+resources:
+permalink:                              /apps/calendar/
+regenerate:                             false
+---
+
+// NOTE:  ASCIIDOC attributes settings
+//
+//  Below, all GENERAL Asciidoc attributes are being set
+//  by using Jekyll|Liquid techniques to include documents
+//  and|or reference images
+//
+:page-liquid:
+
+// additional ASCIIDOC attributes go here
+//
+:figure-caption:                        Figure
+:teamup-home:                           https://www.teamup.com/
+:teamup-help:                           https://www.teamup.com/help/general-help/
+:teamup-faq:                            https://calendar.teamup.com/kb-tags/faq/
+
+
+== J1 Calendar
+
+J1 Calendar is based on the time management solution provided by
+{teamup-home}[TeamUp, window="_blank"]. This cloud-based calendar software
+offers shared calendar for single persons or groups to simplify organizing,
+scheduling, and communication.
+
+The calendar is accessible via the Internet and simplifies how groups share
+plans, schedule events, and communicate statuses. Color-code calendars for team
+members, jobs, projects, and bookable resources. Centrally managed with highly
+customizable role-specific access permissions. No accounts are required.
+
+More information is available at the TeamUp {teamup-help}[Help pages, window="_blank"].
+
+=== Add appointments
+
+The calendar below has limited access to the date database and is allowed to
+add appointments. Checkout the functionalities simply by  click-in the page.
+
+++++
+<div class="row ml-1 mr-1 mb-3">
+  <iframe src="https://teamup.com/ksairsu662tsk8wvtp" style="border-width:0;width:100%;height:700px"></iframe>
+</div>
+++++
+
+//////////
+== Guide for Administrators
+
+This is a complete guide for Calendar Administrators. In the guide you
+will find what is your role as an Administrator, how to setup your calendar
+properly and other various tips like Sharing, Notifications, Importing and
+Exporting Events.
+
+++++
+<div class="row mb-5">
+  <iframe src="https://docs.google.com/presentation/d/1GwyVUoJxJFJZxIycJR3rvI_00ITN5yVRI90DSgjraGc/embed?start=false&amp;loop=true&amp;delayms=30000"
+     style="border-width:0;width:100%;height:700px" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true">
+  </iframe>
+</div>
+++++
+//////////