Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
slapos
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Labels
Merge Requests
104
Merge Requests
104
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Jobs
Commits
Open sidebar
nexedi
slapos
Commits
438baa57
Commit
438baa57
authored
Oct 07, 2019
by
Łukasz Nowak
Committed by
Łukasz Nowak
Nov 08, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
software/helloworld: Use buildout.hash.cfg
parent
08620fb3
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
32 additions
and
5 deletions
+32
-5
software/helloworld/buildout.hash.cfg
software/helloworld/buildout.hash.cfg
+17
-0
software/helloworld/software.cfg
software/helloworld/software.cfg
+15
-5
No files found.
software/helloworld/buildout.hash.cfg
0 → 100644
View file @
438baa57
# THIS IS NOT A BUILDOUT FILE, despite purposedly using a compatible syntax.
# The only allowed lines here are (regexes):
# - "^#" comments, copied verbatim
# - "^[" section beginings, copied verbatim
# - lines containing an "=" sign which must fit in the following categorie.
# - "^\s*filename\s*=\s*path\s*$" where "path" is relative to this file
# Copied verbatim.
# - "^\s*hashtype\s*=.*" where "hashtype" is one of the values supported
# by the re-generation script.
# Re-generated.
# - other lines are copied verbatim
# Substitution (${...:...}), extension ([buildout] extends = ...) and
# section inheritance (< = ...) are NOT supported (but you should really
# not need these here).
[instance-profile]
filename = instance.cfg.in
md5sum = 6567f8dedb5cdd93542dc29e96edb547
software/helloworld/software.cfg
View file @
438baa57
[buildout]
[buildout]
extends =
extends =
# buildout.hash.cfg is used for automated hash calculation of managed
# instance files by calling update-hash
buildout.hash.cfg
# "slapos" stack describes basic things needed for 99.9% of SlapOS Software
# "slapos" stack describes basic things needed for 99.9% of SlapOS Software
# Releases
# Releases
../../stack/slapos.cfg
../../stack/slapos.cfg
...
@@ -25,19 +28,26 @@ parts =
...
@@ -25,19 +28,26 @@ parts =
helloweb-go
helloweb-go
# Macro for jinja templates. The filename is set in buildout.hash.cfg
# in the section using this template
[jinja-template]
recipe = slapos.recipe.template:jinja2
template = ${:_profile_base_location_}/${:filename}
mode = 0644
# Download instance.cfg.in (buildout profile used to deployment of instance),
# Download instance.cfg.in (buildout profile used to deployment of instance),
# replace all ${foo:bar} parameters by real values, and change $${foo:bar} to
# replace all ${foo:bar} parameters by real values, and change $${foo:bar} to
# ${foo:bar}
# ${foo:bar}
# The recipe, template and mode are fetched from jijna-template
[instance-profile]
[instance-profile]
recipe = slapos.recipe.template:jinja2
# The <= is buildout verb to use defined template
template = ${:_profile_base_location_}/instance.cfg.in
<= jinja-template
rendered = ${buildout:directory}/instance.cfg
rendered = ${buildout:directory}/instance.cfg
# MD5 checksum can be skipped for development (easier to develop), but must be filled for production
md5sum = 6567f8dedb5cdd93542dc29e96edb547
mode = 0644
extensions = jinja2.ext.do
extensions = jinja2.ext.do
context =
context =
section buildout buildout
section buildout buildout
# md5sum is fetched from buildout.hash.cfg and can be recalculated automatically by
# calling update-hash
# Pin versions of eggs used that are not already pinned by stack/slapos.cfg
# Pin versions of eggs used that are not already pinned by stack/slapos.cfg
[versions]
[versions]
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment