hmml_to_html.c: Embelish hmml.conf mock-up [#25]
This is still missing a way for an instance of the Network Edition to specify how we access its network's store of member / project info. Without this, we'd have to hardcode it specially for every installation of this Edition, thus making for a more arduous installation process.
This commit is contained in:
parent
955f119a18
commit
a6093b7008
|
@ -2,12 +2,10 @@ edition Project;
|
||||||
|
|
||||||
paths
|
paths
|
||||||
{
|
{
|
||||||
# In HMN, root would be the directory that serves up
|
# In HMN, root would be the directory that serves up https://hero.handmade.network/episodes where the searcher will reside
|
||||||
# https://hero.handmade.network/episodes where the searcher will reside
|
|
||||||
root "/usr/local/www/test";
|
root "/usr/local/www/test";
|
||||||
# All *.hmml files below the repo_remote location are to be pulled in to
|
# All *.hmml files below the repo_remote location are to be pulled in to the system with the directories being compared with
|
||||||
# the system with the directories being compared with the member and project
|
# the member and project settings from the [video] node
|
||||||
# settings from the [video] node
|
|
||||||
repo_remote "https://git.handmade.network/Annotation-Pushers/Annotation-Game";
|
repo_remote "https://git.handmade.network/Annotation-Pushers/Annotation-Game";
|
||||||
repo_local "/usr/local/www/repo";
|
repo_local "/usr/local/www/repo";
|
||||||
# The automatic stub creator will use the stub_base as its base directory
|
# The automatic stub creator will use the stub_base as its base directory
|
||||||
|
@ -16,20 +14,23 @@ paths
|
||||||
|
|
||||||
authentication
|
authentication
|
||||||
{
|
{
|
||||||
# NOTE(matt): Do we need any more auth stuff?
|
# NOTE(matt): Do we need any more auth stuff? Surely we will
|
||||||
repo_token "";
|
repo_token "";
|
||||||
}
|
}
|
||||||
|
|
||||||
project_info
|
project_info
|
||||||
{
|
{
|
||||||
riscy
|
riscy # Note that settings that open blocks do not end in a ; thus distinguishing them from variables set at the same scope
|
||||||
{
|
{
|
||||||
member = "miotatsu"
|
# We need to set member and platform in the config file so the stub generator can do its thing. Maybe consider further,
|
||||||
|
# though, whether the [video] node in our .hmml files still needs to take them
|
||||||
|
member = "miotatsu";
|
||||||
platform = "youtube";
|
platform = "youtube";
|
||||||
|
|
||||||
feed = "https://www.youtube.com/feeds/videos.xml?user=BathtubBlogger";
|
feed = "https://www.youtube.com/feeds/videos.xml?user=BathtubBlogger";
|
||||||
project_name "RISCY BUSINESS";
|
project_name "RISCY BUSINESS";
|
||||||
project_unit "Day";
|
project_unit "Day";
|
||||||
title_pattern "${project_name} - ${project_unit} ${number} - %{title}";
|
title_pattern "${project_name} - ${project_unit} ${number} - ${title}";
|
||||||
# TODO(matt): Work out this title_pattern with some actual stuff
|
# TODO(matt): Work out this title_pattern with some actual stuff
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
@ -37,15 +38,19 @@ project_info
|
||||||
# Comment to end of line
|
# Comment to end of line
|
||||||
credentials
|
credentials
|
||||||
{
|
{
|
||||||
|
funding_platform patreon; # This determines the logo and URL-generation, and we'll need to specify the platforms we support.
|
||||||
|
# A more flexible, if verbose, alternative would be to make each config specify a funding_icon and
|
||||||
|
# the full funding_url
|
||||||
|
#
|
||||||
|
# Note that this setting cascades down to the child scopes, i.e. Miblo{}, miotatsu{}, etc
|
||||||
|
|
||||||
Miblo # The single-word name we use in the .hmml files, which also matches the username of project owners
|
Miblo # The single-word name we use in the .hmml files, which also matches the username of project owners
|
||||||
# Note that settings that open blocks do not end in a ;
|
|
||||||
{
|
{
|
||||||
display_name "Matt Mascarenhas"; # Optional, and may optionally be surrounded by quotes
|
display_name "Matt Mascarenhas"; # Optional, and may optionally be surrounded by quotes
|
||||||
homepage "http://miblodelcarpio.co.uk/"; # May optionally be quoted, as the admit prefers,
|
homepage "http://miblodelcarpio.co.uk/"; # May optionally be quoted, as the admin prefers, but must be quoted if
|
||||||
# but must be quoted if containing a ;
|
# containing a ; (which is a valid character according to:
|
||||||
avatar "some_location.png"; # TODO(matt): Think further whether we want this
|
# https://url.spec.whatwg.org/#userinfo-percent-encode-set)
|
||||||
funding_platform patreon; # This determines the logo and URL-generation,
|
avatar "some_location.png"; # TODO(matt): Mock up the Credits Menu to determine whether or not we want this
|
||||||
# and we'll need to specify the platforms we support
|
|
||||||
funding_username miblo;
|
funding_username miblo;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
@ -53,12 +58,10 @@ credentials
|
||||||
{
|
{
|
||||||
display_name "Mio Iwakura";
|
display_name "Mio Iwakura";
|
||||||
homepage "http://riscy.tv/";
|
homepage "http://riscy.tv/";
|
||||||
funding_platform patreon;
|
|
||||||
funding_username miotatsu;
|
funding_username miotatsu;
|
||||||
}
|
}
|
||||||
|
|
||||||
_yunsup_lee # Prefixing with _ could be the convention for guests who are
|
_yunsup_lee # Prefixing with _ could be the convention for guests who are not in the member base of the (associated) network
|
||||||
# not in the member base of the (associated) network
|
|
||||||
{
|
{
|
||||||
display_name "Yunsup Lee";
|
display_name "Yunsup Lee";
|
||||||
homepage "https://www.linkedin.com/in/yunsup-lee-385b692b";
|
homepage "https://www.linkedin.com/in/yunsup-lee-385b692b";
|
||||||
|
@ -70,3 +73,5 @@ credentials
|
||||||
homepage "https://www.linkedin.com/in/andrew-waterman-76805788";
|
homepage "https://www.linkedin.com/in/andrew-waterman-76805788";
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
|
# NOTE(matt): Semantic characters, which may require \-escaping: ; # { " $
|
||||||
|
|
Loading…
Reference in New Issue