Skip to content
This repository has been archived by the owner on Jan 20, 2020. It is now read-only.

Add template for new playpen projects #83

Merged
merged 7 commits into from Jun 20, 2016
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
Expand Up @@ -16,4 +16,4 @@ on the projects add to it. For your project to be added, it is important that:
Please note that we are going to consider removing a non-working snap from the
repo if we can't get it to work after a month without updates.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/repo/playpen/

Just something picky. ;)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is in the contextual diff, I'll do a direct typo fix following this PR, nice addition! :)


Use `template.README.md` to kickstart your project.
Use `snap-template` with our formatted `README.md` to kickstart your project.
3 changes: 2 additions & 1 deletion ci-run
Expand Up @@ -11,8 +11,9 @@ fi
root_dir=`pwd`
return_code=0
for dir in $projects_to_test; do
# Don't include files in root directory
# Don't include files in root and template directory
[ ! -d $dir ] && continue
[ "$dir" = "snap-template" ] && continue

echo "Testing $dir"
cd ${root_dir}/$dir
Expand Down
File renamed without changes.
29 changes: 29 additions & 0 deletions snap-template/snapcraft.yaml
@@ -0,0 +1,29 @@
name: my-snap # the name of the snap
version: "0.1" # the version of the snap, which can be any string
summary: This is my-snap's summary # 79 char long summary
description: |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is it only a |? I've always put something on this line, but I could just not know what I'm talking about ;)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

otherwise, it's not going to be a valid yaml file (as per spec), I find is as well cleaner to have then all the text aligned

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah I see, I learned something new :)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is my-snap's description # a longer description for the snap
which can expand multiple lines.
confinement: devmode # start with devmode, then use "strict" to enforce system
# access only via declared interfaces

apps: # declarative apps come in second place
my-snap: # if only one command is exposed, please use
# [app name == snap name] to have a shorten command executable.
command: my-command

parts:
my-part: # Replace with a part name of your liking
# Get more information about plugins by running:
# snapcraft help plugins
# and more information about the available plugins by running:
# snapcraft list-plugins.
plugin: nil
# Lines for yaml files (including description) should be under
# 80 characters. If more if needed, they should be
# broken up in multiple stenzas.
# For example, a list like [foo, bar, baz] should be broken up into:
# - foo
# - bar
# - baz
# as soon as the line is more than 80 characters.