leap_se issueshttps://0xacab.org/leap/leap_se/-/issues2021-03-18T13:46:40Zhttps://0xacab.org/leap/leap_se/-/issues/13Update pointers, archive, new site2021-03-18T13:46:40ZkwadronautUpdate pointers, archive, new siteThere's now a hugo site.
- [x] clone the repo from Chad inside github
- [ ] mirror from github to here
- [ ] retire this?
- [ ] figure out how to track github issues and PRs?
- [ ] automate deploymentsThere's now a hugo site.
- [x] clone the repo from Chad inside github
- [ ] mirror from github to here
- [ ] retire this?
- [ ] figure out how to track github issues and PRs?
- [ ] automate deploymentskwadronautkwadronauthttps://0xacab.org/leap/leap_se/-/issues/12Feedback Quickstart manual2018-03-02T12:36:01ZdoschFeedback Quickstart manual# LEAP Manual MacOS Feedback
https://leap.se/en/docs/platform/tutorials/quick-start
QUICK Start Manual
As tested on 2 March 2018 on Mac OS 10.13.3 (17D102)
Feedback marked with a **#** is an idea.
Feedback marked with a **!** is an om...# LEAP Manual MacOS Feedback
https://leap.se/en/docs/platform/tutorials/quick-start
QUICK Start Manual
As tested on 2 March 2018 on Mac OS 10.13.3 (17D102)
Feedback marked with a **#** is an idea.
Feedback marked with a **!** is an omission or mistake (imho)
## Requirements
* # would be great if people can test their server with a test script to see if requirements are met.
* ! brew is not installed by default on MacOS. A link to installation instructions would be great.
* ! git is not installed by default on MacOS. A link to installation instructions would be great.
## The platform recipes
* # a suggestion for a directory location to clone the git repository to, would be nice.
* ! You need to cd into the new directory before you can do ``git checkout 0.10.0``
* ! ```git checkout 0.10.0``` gives the following message:
```
Note: checking out '0.10.0'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b <new-branch-name>
HEAD is now at bf6c56d8... run_tests - use byebug instead of debugger
```
There is no clear indication on how to continue.
# Install the LEAP command-line utility
* # "To confirm that you installed leap correctly, try running leap --version."
A line on expected output that confirm successful installation would help here.
# Create a provider instance
* ! ``Create directory ~/example?``. This question does not specify what acceptable input as an answer. (y, yes, ok etc.)
* ! ``leap add-user louise --self``
Expected: option to create certs.
What I got was:
```
Choose your SSH public key:
1. ssh-rsa 2048 SHA256:xxx[...]xxxx (github_rsa.pub)
2. ssh-dss 3464 SHA256:xxx[...]xxxx (id_dsa.pub)
3. ssh-rsa 2048 SHA256:xxx[...]xxxx (id_rsa.pub)
q: quit
number 1-3>
```
# Add a node to the provider
* # ``We will now add a single node with two services, “webapp” and “couchdb”.``
This leaves the reader to wonder: do I need these two services anyway, what do they do, can I remove them later?
# Option A: Add a real node
* ! remind people that 'wildebeest' is just a example name and they can choose their own.
# Test that things worked correctly
! I get output:
```
leap test
= [wildebeast] /usr/bin/env:
= [wildebeast] /srv/leap/bin/run_tests
= [wildebeast] : No such file or directory
= bailing out
```
Stuck for now, as soon as I am able to continue I can give feedback on the remainder part of the quick install guide.
Thnx!https://0xacab.org/leap/leap_se/-/issues/10Update "Get Involved" section of Documentation to use Read the Docs2017-11-20T19:06:26ZjubobotUpdate "Get Involved" section of Documentation to use Read the DocsThere is a lot of outdated documentation in the "Get Involved" section of the leap.se website (https://leap.se/en/docs/get-involved). Rather than maintain two separate sets of
documentation (which are somewhat contradictory and confusing...There is a lot of outdated documentation in the "Get Involved" section of the leap.se website (https://leap.se/en/docs/get-involved). Rather than maintain two separate sets of
documentation (which are somewhat contradictory and confusing), update the pages where possible to point to the relevant pages on Read the Docs.https://0xacab.org/leap/leap_se/-/issues/7add atom/rss feed2017-11-02T17:28:33Zelijahadd atom/rss feed> There used to be an ATOM feed (yay ATOM, death to RSS) on the website. I'm an feed power user so this makes me sad :(
> RSS would be fine too :D> There used to be an ATOM feed (yay ATOM, death to RSS) on the website. I'm an feed power user so this makes me sad :(
> RSS would be fine too :Dhttps://0xacab.org/leap/leap_se/-/issues/6leap-archive-keyring should not install a globally valid trust anchor2018-09-21T13:20:45Zanarcatleap-archive-keyring should not install a globally valid trust anchor(This is a copy of a bug reported in Debian as [#880220](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880220). It is copied here because changes in Debian would require changes in install instructions on the website as well.]
This ...(This is a copy of a bug reported in Debian as [#880220](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880220). It is copied here because changes in Debian would require changes in install instructions on the website as well.]
This package installs a keyring in /etc/apt/trusted.gpg.d which is
great as it allows people to easily install LEAP applications by
leveraging the trust path already in Debian.
It does, however, mean that LEAP could, in theory, sign releases for
the official Debian archive, which is probably not what you
want. There are some efforts underway to standardize a process for
third-party repositories like LEAP, and the current proposal is to
store those certificates in /usr/share/keyrings/ instead. See:
https://wiki.debian.org/DebianRepository/UseThirdParty#OpenPGP_Key_distribution
Then that key can be refered to in the sources.list, which connects
the repository with its trust anchor without polluting the global
trust space:
deb [signed-by=/usr/share/keyrings/deriv-archive-keyring.gpg] https://deriv.example.net/debian/ stable main
In the case of LEAP, this would probably be something like:
sudo sh -c 'echo "deb [signed-by=/usr/share/keyrings/leap-archive-keyring.gpg] http://deb.leap.se/client release stretch" > /etc/apt/sources.list.d/bitmask.list'
I would also recommend setting up a pinned preferences file in the
archive as well, to keep the sources.list from upgrading random
packages from the main archive. I guess the preferences file could
look something like:
Package: bitmask* python-sqlcipher python-leap-common soledad*
Pin: origin deb.leap.se
Pin-Priority: 100
I would be happy to help you make those changes if you accept.https://0xacab.org/leap/leap_se/-/issues/5Deploy subprojects' documentation automatically to leap.se website2017-10-26T18:11:45ZdrebsDeploy subprojects' documentation automatically to leap.se websiteElijah's proposal: one script that reads a list of (url, path) from a file, downloads urls and puts them in paths.
What's needed:
- git repo url and path from where to pull doc,
- path where doc should be in the website
- documentation...Elijah's proposal: one script that reads a list of (url, path) from a file, downloads urls and puts them in paths.
What's needed:
- git repo url and path from where to pull doc,
- path where doc should be in the website
- documentation format
- Please add those to https://0xacab.org/leap/leap_se/wikis/Subprojects-Documentation
elijahelijah