Compare commits
1 Commits
| Author | SHA1 | Date |
|---|---|---|
 tester.nicolai
|
f8f43b6cee |
205
.drone.yml
205
.drone.yml
|
|
@ -1,205 +0,0 @@
|
|||
kind: pipeline
|
||||
type: exec
|
||||
name: Nightly
|
||||
|
||||
steps:
|
||||
- name: Prepare
|
||||
commands:
|
||||
- ln -s /var/lib/drone-runner-exec/.local $HOME/.local
|
||||
- ln -s /var/lib/drone-runner-exec/fdroid $HOME/fdroid
|
||||
|
||||
- name: Run Tests
|
||||
commands:
|
||||
- ./ci.py --ci-run-tests
|
||||
# - sonar-scanner -Dsonar.projectKey=SelfPrivacy-Flutter-App -Dsonar.sources=. -Dsonar.host.url=http://analyzer.lan:9000 -Dsonar.login="$SONARQUBE_TOKEN"
|
||||
environment:
|
||||
SONARQUBE_TOKEN:
|
||||
from_secret: SONARQUBE_TOKEN
|
||||
|
||||
- name: Build Nightly Linux Release Artifact (Binary)
|
||||
commands:
|
||||
- ./ci.py --ci-build-linux
|
||||
|
||||
- name: Build Nightly Release Artifact (.APK)
|
||||
commands:
|
||||
- ./ci.py --ci-build-apk
|
||||
|
||||
- name: Sign and Commit Nightly Android Release Artifact (.APK) for F-Droid Repository
|
||||
commands:
|
||||
- rm -rf $HOME/fdroid/build/org.selfprivacy.app.nightly && mkdir $HOME/fdroid/build/org.selfprivacy.app.nightly
|
||||
- git archive --format=tar HEAD | tar x -C $HOME/fdroid/build/org.selfprivacy.app.nightly
|
||||
- ./ci.py --sign-apk-fdroid-nightly
|
||||
environment:
|
||||
STANDALONE_KEYSTORE_PASS:
|
||||
from_secret: STANDALONE_KEYSTORE_PASS
|
||||
FDROID_KEYSTORE_PASS:
|
||||
from_secret: FDROID_KEYSTORE_PASS
|
||||
GOOGLE_KEYSTORE_PASS:
|
||||
from_secret: GOOGLE_KEYSTORE_PASS
|
||||
|
||||
- name: Deploy F-Droid Repository
|
||||
commands:
|
||||
- ./ci.py --deploy-fdroid-repo
|
||||
environment:
|
||||
SSH_PRIVATE_KEY:
|
||||
from_secret: SSH_PRIVATE_KEY
|
||||
|
||||
trigger:
|
||||
event:
|
||||
- push
|
||||
branch:
|
||||
- master
|
||||
|
||||
node:
|
||||
server: builder
|
||||
|
||||
---
|
||||
|
||||
kind: pipeline
|
||||
type: exec
|
||||
name: Release
|
||||
|
||||
steps:
|
||||
- name: Prepare
|
||||
commands:
|
||||
- ln -s /var/lib/drone-runner-exec/.local $HOME/.local
|
||||
- ln -s /var/lib/drone-runner-exec/fdroid $HOME/fdroid
|
||||
- if podman volume exists release; then podman volume rm -f release; podman volume create release; else podman volume create release; fi
|
||||
- git config user.email "builder@selfprivacy.org"
|
||||
- git config user.name "Builder"
|
||||
|
||||
- name: Create an Empty Gitea Release
|
||||
commands:
|
||||
- ./ci.py --gitea-create-release
|
||||
environment:
|
||||
GITEA_RELEASE_TOKEN:
|
||||
from_secret: GITEA_RELEASE_TOKEN
|
||||
|
||||
- name: Build Intermediate Linux Release Artifact (Binary)
|
||||
commands:
|
||||
- ./ci.py --build-linux
|
||||
environment:
|
||||
STANDALONE_KEYSTORE_PASS:
|
||||
from_secret: STANDALONE_KEYSTORE_PASS
|
||||
FDROID_KEYSTORE_PASS:
|
||||
from_secret: FDROID_KEYSTORE_PASS
|
||||
GOOGLE_KEYSTORE_PASS:
|
||||
from_secret: GOOGLE_KEYSTORE_PASS
|
||||
|
||||
- name: Build Intermediate Android Release Artifact (.APK)
|
||||
commands:
|
||||
- ./ci.py --build-apk
|
||||
environment:
|
||||
STANDALONE_KEYSTORE_PASS:
|
||||
from_secret: STANDALONE_KEYSTORE_PASS
|
||||
FDROID_KEYSTORE_PASS:
|
||||
from_secret: FDROID_KEYSTORE_PASS
|
||||
GOOGLE_KEYSTORE_PASS:
|
||||
from_secret: GOOGLE_KEYSTORE_PASS
|
||||
|
||||
- name: Build Intermediate Android Release Artifact (Bundle)
|
||||
commands:
|
||||
- ./ci.py --build-bundle
|
||||
environment:
|
||||
STANDALONE_KEYSTORE_PASS:
|
||||
from_secret: STANDALONE_KEYSTORE_PASS
|
||||
FDROID_KEYSTORE_PASS:
|
||||
from_secret: FDROID_KEYSTORE_PASS
|
||||
GOOGLE_KEYSTORE_PASS:
|
||||
from_secret: GOOGLE_KEYSTORE_PASS
|
||||
|
||||
- name: Sign Android Release Artifact (.APK) for Standalone Use
|
||||
commands:
|
||||
- ./ci.py --sign-apk-standalone
|
||||
environment:
|
||||
STANDALONE_KEYSTORE_PASS:
|
||||
from_secret: STANDALONE_KEYSTORE_PASS
|
||||
FDROID_KEYSTORE_PASS:
|
||||
from_secret: FDROID_KEYSTORE_PASS
|
||||
GOOGLE_KEYSTORE_PASS:
|
||||
from_secret: GOOGLE_KEYSTORE_PASS
|
||||
|
||||
- name: Sign and Commit Android Release Artifact (.APK) for F-Droid Repository
|
||||
commands:
|
||||
- rm -rf $HOME/fdroid/build/org.selfprivacy.app && mkdir $HOME/fdroid/build/org.selfprivacy.app
|
||||
- git archive --format=tar HEAD | tar x -C $HOME/fdroid/build/org.selfprivacy.app
|
||||
- ./ci.py --sign-apk-fdroid
|
||||
environment:
|
||||
STANDALONE_KEYSTORE_PASS:
|
||||
from_secret: STANDALONE_KEYSTORE_PASS
|
||||
FDROID_KEYSTORE_PASS:
|
||||
from_secret: FDROID_KEYSTORE_PASS
|
||||
GOOGLE_KEYSTORE_PASS:
|
||||
from_secret: GOOGLE_KEYSTORE_PASS
|
||||
|
||||
- name: Sign Android Release Artifact (Bundle) for Google Play
|
||||
commands:
|
||||
- ./ci.py --sign-bundle
|
||||
environment:
|
||||
STANDALONE_KEYSTORE_PASS:
|
||||
from_secret: STANDALONE_KEYSTORE_PASS
|
||||
FDROID_KEYSTORE_PASS:
|
||||
from_secret: FDROID_KEYSTORE_PASS
|
||||
GOOGLE_KEYSTORE_PASS:
|
||||
from_secret: GOOGLE_KEYSTORE_PASS
|
||||
|
||||
- name: Package Linux AppImage Artifact
|
||||
commands:
|
||||
- ./ci.py --package-linux-appimage
|
||||
|
||||
- name: Package Linux Flatpak Artifact
|
||||
commands:
|
||||
- ./ci.py --package-linux-flatpak
|
||||
|
||||
- name: Package Linux Archive Artifact
|
||||
commands:
|
||||
- ./ci.py --package-linux-archive
|
||||
|
||||
- name: Push Artifacts to the Release Volume
|
||||
commands:
|
||||
- git add -v *.AppImage *.AppImage.zsync *.flatpak *.apk *.apk.idsig *.aab *.tar.zstd
|
||||
- git commit -m Release
|
||||
- git archive --format=tar HEAD | podman volume import release -
|
||||
|
||||
trigger:
|
||||
event:
|
||||
- tag
|
||||
|
||||
node:
|
||||
server: builder
|
||||
|
||||
---
|
||||
|
||||
kind: pipeline
|
||||
type: exec
|
||||
name: Deploy
|
||||
|
||||
steps:
|
||||
- name: Prepare
|
||||
commands:
|
||||
- ln -s /var/lib/drone-runner-exec/.local $HOME/.local
|
||||
- podman unshare podman volume mount release
|
||||
|
||||
- name: Deploy Artifacts to Gitea
|
||||
commands:
|
||||
- ./ci.py --deploy-gitea-release
|
||||
environment:
|
||||
GITEA_RELEASE_TOKEN:
|
||||
from_secret: GITEA_RELEASE_TOKEN
|
||||
|
||||
- name: Deploy F-Droid Repository
|
||||
commands:
|
||||
- ./ci.py --deploy-fdroid-repo
|
||||
environment:
|
||||
SSH_PRIVATE_KEY:
|
||||
from_secret: SSH_PRIVATE_KEY
|
||||
|
||||
trigger:
|
||||
event:
|
||||
- tag
|
||||
|
||||
node:
|
||||
server: builder
|
||||
|
||||
depends_on:
|
||||
- Release
|
||||
|
|
@ -14,6 +14,3 @@ max_line_length = 150
|
|||
|
||||
[*.md]
|
||||
trim_trailing_whitespace = false
|
||||
|
||||
[*.json]
|
||||
indent_size = 4
|
||||
|
|
|
|||
|
|
@ -1,68 +0,0 @@
|
|||
name: Bug report
|
||||
about: File a bug report
|
||||
labels:
|
||||
- Bug
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: |
|
||||
Thanks for taking the time to fill out this bug report! Please provide a short but a descriptive title for your issue.
|
||||
- type: textarea
|
||||
id: expected-behaviour
|
||||
attributes:
|
||||
label: Expected Behavior
|
||||
description: What did you expect to happen?
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
id: actual-behaviour
|
||||
attributes:
|
||||
label: Actual Behavior
|
||||
description: What actually happened?
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
id: steps-to-reproduce
|
||||
attributes:
|
||||
label: Steps to Reproduce
|
||||
description: What steps can we follow to reproduce this issue?
|
||||
placeholder: |
|
||||
1. First step
|
||||
2. Second step
|
||||
3. and so on...
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
id: context
|
||||
attributes:
|
||||
label: Context and notes
|
||||
description: Additional information about environment or what were you trying to do. If you have an idea how to fix this issue, please describe it here too.
|
||||
- type: textarea
|
||||
id: logs
|
||||
attributes:
|
||||
label: Relevant log output
|
||||
description: Please copy and paste any relevant log output, if you have any. This will be automatically formatted into code, so no need for backticks.
|
||||
render: shell
|
||||
- type: input
|
||||
id: app-version
|
||||
attributes:
|
||||
label: App Version
|
||||
description: What version of SelfPrivacy app are you running? You can find it in the "About" section of the app.
|
||||
validations:
|
||||
required: true
|
||||
- type: input
|
||||
id: api-version
|
||||
attributes:
|
||||
label: Server API Version
|
||||
description: What version of SelfPrivacy API are you running? You can find it in the "About" section of the app. Leave it empty if your app is not connected to the server yet.
|
||||
- type: dropdown
|
||||
id: os
|
||||
attributes:
|
||||
label: Operating System
|
||||
description: What operating system are you using?
|
||||
options:
|
||||
- Android
|
||||
- iOS
|
||||
- Linux
|
||||
- macOS
|
||||
- Windows
|
||||
|
|
@ -1,23 +0,0 @@
|
|||
name: Feature request
|
||||
about: Suggest an idea for this project
|
||||
label:
|
||||
- Feature request
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: |
|
||||
Thanks for taking the time to fill out this feature request! Please provide a short but a descriptive title for your issue.
|
||||
- type: textarea
|
||||
id: description
|
||||
attributes:
|
||||
label: Description
|
||||
description: Describe the feature you'd like to see.
|
||||
placeholder: |
|
||||
As a user, I want to be able to...
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
id: context
|
||||
attributes:
|
||||
label: Context and notes
|
||||
description: Additional information about environment and what were you trying to do. If you have an idea how to implement this feature, please describe it here too.
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
name: Translation issue
|
||||
about: File a translation (localization) issue
|
||||
labels:
|
||||
- Translations
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: |
|
||||
Translations can be modified and discussed on [Weblate](https://weblate.selfprivacy.org/projects/selfprivacy/). You can fix the mistranslation issue yourself there. Using the search, you can also find the string ID of the mistranslated string. If your issue is more complex, please file it here
|
||||
|
||||
If you are a member of SelfPrivacy core team, you **must** fix the issue yourself on Weblate.
|
||||
- type: input
|
||||
id: language
|
||||
attributes:
|
||||
label: Language
|
||||
description: What language is affected?
|
||||
placeholder: |
|
||||
English
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
id: description
|
||||
attributes:
|
||||
label: Description
|
||||
description: Describe the issue in detail. If you have an idea how to fix this issue, please describe it here too. Include the string ID of the mistranslated string, if possible.
|
||||
placeholder: |
|
||||
The string `string.id` is translated as "foo", but it should be "bar".
|
||||
validations:
|
||||
required: true
|
||||
|
|
@ -1,32 +0,0 @@
|
|||
name: Windows Builder
|
||||
|
||||
on:
|
||||
push:
|
||||
tags:
|
||||
- '*.*.*'
|
||||
|
||||
jobs:
|
||||
build-windows:
|
||||
runs-on: windows-latest
|
||||
steps:
|
||||
- uses: actions/checkout@v3
|
||||
|
||||
# Install Python dependencies
|
||||
- run: pip install requests pyyaml
|
||||
|
||||
# Install Flutter
|
||||
- uses: subosito/flutter-action@v2
|
||||
with:
|
||||
flutter-version: '3.16.1'
|
||||
channel: 'stable'
|
||||
|
||||
# Build Windows artifact
|
||||
- run: flutter build windows
|
||||
|
||||
# Archive the build
|
||||
- run: python ci.py --package-windows-archive
|
||||
|
||||
# Upload the build
|
||||
- run: python ci.py --deploy-windows-archive
|
||||
env:
|
||||
GITEA_RELEASE_TOKEN: ${{ secrets.GITEA_RELEASE_TOKEN }}
|
||||
|
|
@ -1,4 +1,3 @@
|
|||
ios/build
|
||||
# Miscellaneous
|
||||
*.class
|
||||
*.log
|
||||
|
|
@ -30,7 +29,7 @@ ios/build
|
|||
.packages
|
||||
.pub-cache/
|
||||
.pub/
|
||||
**/build/
|
||||
/build/
|
||||
|
||||
# Web related
|
||||
lib/generated_plugin_registrant.dart
|
||||
|
|
|
|||
29
.metadata
29
.metadata
|
|
@ -1,33 +1,10 @@
|
|||
# This file tracks properties of this Flutter project.
|
||||
# Used by Flutter tool to assess capabilities and perform upgrades etc.
|
||||
#
|
||||
# This file should be version controlled.
|
||||
# This file should be version controlled and should not be manually edited.
|
||||
|
||||
version:
|
||||
revision: 5293f3cd4427b4b48ed155e7a3852c6b3c53d94a
|
||||
channel: beta
|
||||
revision: 1aafb3a8b9b0c36241c5f5b34ee914770f015818
|
||||
channel: stable
|
||||
|
||||
project_type: app
|
||||
|
||||
# Tracks metadata for the flutter migrate command
|
||||
migration:
|
||||
platforms:
|
||||
- platform: root
|
||||
create_revision: 5293f3cd4427b4b48ed155e7a3852c6b3c53d94a
|
||||
base_revision: 5293f3cd4427b4b48ed155e7a3852c6b3c53d94a
|
||||
- platform: linux
|
||||
create_revision: 5293f3cd4427b4b48ed155e7a3852c6b3c53d94a
|
||||
base_revision: 5293f3cd4427b4b48ed155e7a3852c6b3c53d94a
|
||||
- platform: windows
|
||||
create_revision: 5293f3cd4427b4b48ed155e7a3852c6b3c53d94a
|
||||
base_revision: 5293f3cd4427b4b48ed155e7a3852c6b3c53d94a
|
||||
|
||||
# User provided section
|
||||
|
||||
# List of Local paths (relative to this file) that should be
|
||||
# ignored by the migrate tool.
|
||||
#
|
||||
# Files that are not part of the templates will be ignored by default.
|
||||
unmanaged_files:
|
||||
- 'lib/main.dart'
|
||||
- 'ios/Runner.xcodeproj/project.pbxproj'
|
||||
|
|
|
|||
58
Dockerfile
58
Dockerfile
|
|
@ -1,58 +0,0 @@
|
|||
FROM ubuntu:22.04
|
||||
|
||||
ARG PACKAGES="build-essential openjdk-11-jdk-headless clang cmake curl git jq libblkid1 \
|
||||
libblkid-dev libc6 libc6-dev libc-bin libcrypt1 libdbus-1-3 libexpat1 libffi7 \
|
||||
libgcc-s1 libgcrypt20 libgcrypt20-dev libglib2.0-0 libglib2.0-dev libglu1-mesa \
|
||||
libgpg-error0 libgtk-3-0 libgtk-3-dev liblz4-1 liblz4-dev liblzma5 liblzma-dev \
|
||||
libmount1 libpcre3 libselinux1 libsepol2 libstdc++-10-dev libstdc++6 libuuid1 \
|
||||
ninja-build pkg-config rsync unzip xz-utils zlib1g unzip libsecret-1-dev libsecret-tools \
|
||||
libsecret-1-0 libjsoncpp-dev fuse flatpak-builder binutils coreutils desktop-file-utils \
|
||||
fakeroot fuse libgdk-pixbuf2.0-dev patchelf python3-pip python3-setuptools squashfs-tools \
|
||||
strace util-linux zsync"
|
||||
ARG ANDROID_SDK_TOOLS_VERSION="8512546"
|
||||
ARG ANDROID_SDK_TOOLS_URL="https://dl.google.com/android/repository/commandlinetools-linux-${ANDROID_SDK_TOOLS_VERSION}_latest.zip"
|
||||
ARG FLUTTER_VERSION="3.3.1"
|
||||
ARG FLUTTER_URL="https://storage.googleapis.com/flutter_infra_release/releases/stable/linux/flutter_linux_${FLUTTER_VERSION}-stable.tar.xz"
|
||||
ARG FREEDESKTOP_SDK_VERSION="22.08"
|
||||
|
||||
# Update packages
|
||||
RUN apt-get update && apt-get upgrade -y && apt-get install -y $PACKAGES
|
||||
|
||||
WORKDIR /opt
|
||||
|
||||
# Install Android SDK
|
||||
ADD $ANDROID_SDK_TOOLS_URL .
|
||||
RUN mkdir -p android-sdk/cmdline-tools && unzip commandlinetools-linux-${ANDROID_SDK_TOOLS_VERSION}_latest.zip \
|
||||
&& rm commandlinetools-linux-${ANDROID_SDK_TOOLS_VERSION}_latest.zip && mv cmdline-tools android-sdk/cmdline-tools/latest
|
||||
|
||||
# Install Flutter
|
||||
ENV FLUTTER_HOME "/opt/flutter"
|
||||
ADD $FLUTTER_URL .
|
||||
RUN tar -vxf flutter_linux_${FLUTTER_VERSION}-stable.tar.xz && \
|
||||
rm flutter_linux_${FLUTTER_VERSION}-stable.tar.xz
|
||||
# Flutter doesn't work without write permissions, so fuck it, fuck
|
||||
RUN chmod -R 777 $FLUTTER_HOME
|
||||
RUN git config --system --add safe.directory $FLUTTER_HOME
|
||||
|
||||
ENV ANDROID_HOME "/opt/android-sdk"
|
||||
ENV ANDROID_SDK_ROOT "${ANDROID_HOME}"
|
||||
ENV PATH "$PATH:$ANDROID_SDK_ROOT/cmdline-tools/latest/bin:$ANDROID_SDK_ROOT/build-tools/30.0.3:/opt/flutter/bin"
|
||||
|
||||
# Install needed Android SDK packages
|
||||
RUN yes | sdkmanager 'build-tools;30.0.3' 'platforms;android-29' 'platforms;android-30' 'platforms;android-31'
|
||||
|
||||
WORKDIR /tmp
|
||||
|
||||
# Prepare dependencies for offline build
|
||||
ENV PUB_CACHE "/tmp/flutter_pub_cache"
|
||||
ENV GRADLE_USER_HOME "/tmp/gradle"
|
||||
RUN git clone --depth=1 --single-branch https://git.selfprivacy.org/kherel/selfprivacy.org.app.git deps
|
||||
WORKDIR /tmp/deps
|
||||
RUN flutter build linux
|
||||
RUN flutter build apk --flavor production
|
||||
WORKDIR /tmp
|
||||
RUN rm -rf deps
|
||||
RUN find $GRADLE_USER_HOME/daemon -exec chmod 777 {} \;
|
||||
|
||||
# Install AppImage Builder and F-Droid Server
|
||||
RUN pip3 install appimage-builder fdroidserver
|
||||
674
LICENSE
674
LICENSE
|
|
@ -1,674 +0,0 @@
|
|||
GNU GENERAL PUBLIC LICENSE
|
||||
Version 3, 29 June 2007
|
||||
|
||||
Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
|
||||
Everyone is permitted to copy and distribute verbatim copies
|
||||
of this license document, but changing it is not allowed.
|
||||
|
||||
Preamble
|
||||
|
||||
The GNU General Public License is a free, copyleft license for
|
||||
software and other kinds of works.
|
||||
|
||||
The licenses for most software and other practical works are designed
|
||||
to take away your freedom to share and change the works. By contrast,
|
||||
the GNU General Public License is intended to guarantee your freedom to
|
||||
share and change all versions of a program--to make sure it remains free
|
||||
software for all its users. We, the Free Software Foundation, use the
|
||||
GNU General Public License for most of our software; it applies also to
|
||||
any other work released this way by its authors. You can apply it to
|
||||
your programs, too.
|
||||
|
||||
When we speak of free software, we are referring to freedom, not
|
||||
price. Our General Public Licenses are designed to make sure that you
|
||||
have the freedom to distribute copies of free software (and charge for
|
||||
them if you wish), that you receive source code or can get it if you
|
||||
want it, that you can change the software or use pieces of it in new
|
||||
free programs, and that you know you can do these things.
|
||||
|
||||
To protect your rights, we need to prevent others from denying you
|
||||
these rights or asking you to surrender the rights. Therefore, you have
|
||||
certain responsibilities if you distribute copies of the software, or if
|
||||
you modify it: responsibilities to respect the freedom of others.
|
||||
|
||||
For example, if you distribute copies of such a program, whether
|
||||
gratis or for a fee, you must pass on to the recipients the same
|
||||
freedoms that you received. You must make sure that they, too, receive
|
||||
or can get the source code. And you must show them these terms so they
|
||||
know their rights.
|
||||
|
||||
Developers that use the GNU GPL protect your rights with two steps:
|
||||
(1) assert copyright on the software, and (2) offer you this License
|
||||
giving you legal permission to copy, distribute and/or modify it.
|
||||
|
||||
For the developers' and authors' protection, the GPL clearly explains
|
||||
that there is no warranty for this free software. For both users' and
|
||||
authors' sake, the GPL requires that modified versions be marked as
|
||||
changed, so that their problems will not be attributed erroneously to
|
||||
authors of previous versions.
|
||||
|
||||
Some devices are designed to deny users access to install or run
|
||||
modified versions of the software inside them, although the manufacturer
|
||||
can do so. This is fundamentally incompatible with the aim of
|
||||
protecting users' freedom to change the software. The systematic
|
||||
pattern of such abuse occurs in the area of products for individuals to
|
||||
use, which is precisely where it is most unacceptable. Therefore, we
|
||||
have designed this version of the GPL to prohibit the practice for those
|
||||
products. If such problems arise substantially in other domains, we
|
||||
stand ready to extend this provision to those domains in future versions
|
||||
of the GPL, as needed to protect the freedom of users.
|
||||
|
||||
Finally, every program is threatened constantly by software patents.
|
||||
States should not allow patents to restrict development and use of
|
||||
software on general-purpose computers, but in those that do, we wish to
|
||||
avoid the special danger that patents applied to a free program could
|
||||
make it effectively proprietary. To prevent this, the GPL assures that
|
||||
patents cannot be used to render the program non-free.
|
||||
|
||||
The precise terms and conditions for copying, distribution and
|
||||
modification follow.
|
||||
|
||||
TERMS AND CONDITIONS
|
||||
|
||||
0. Definitions.
|
||||
|
||||
"This License" refers to version 3 of the GNU General Public License.
|
||||
|
||||
"Copyright" also means copyright-like laws that apply to other kinds of
|
||||
works, such as semiconductor masks.
|
||||
|
||||
"The Program" refers to any copyrightable work licensed under this
|
||||
License. Each licensee is addressed as "you". "Licensees" and
|
||||
"recipients" may be individuals or organizations.
|
||||
|
||||
To "modify" a work means to copy from or adapt all or part of the work
|
||||
in a fashion requiring copyright permission, other than the making of an
|
||||
exact copy. The resulting work is called a "modified version" of the
|
||||
earlier work or a work "based on" the earlier work.
|
||||
|
||||
A "covered work" means either the unmodified Program or a work based
|
||||
on the Program.
|
||||
|
||||
To "propagate" a work means to do anything with it that, without
|
||||
permission, would make you directly or secondarily liable for
|
||||
infringement under applicable copyright law, except executing it on a
|
||||
computer or modifying a private copy. Propagation includes copying,
|
||||
distribution (with or without modification), making available to the
|
||||
public, and in some countries other activities as well.
|
||||
|
||||
To "convey" a work means any kind of propagation that enables other
|
||||
parties to make or receive copies. Mere interaction with a user through
|
||||
a computer network, with no transfer of a copy, is not conveying.
|
||||
|
||||
An interactive user interface displays "Appropriate Legal Notices"
|
||||
to the extent that it includes a convenient and prominently visible
|
||||
feature that (1) displays an appropriate copyright notice, and (2)
|
||||
tells the user that there is no warranty for the work (except to the
|
||||
extent that warranties are provided), that licensees may convey the
|
||||
work under this License, and how to view a copy of this License. If
|
||||
the interface presents a list of user commands or options, such as a
|
||||
menu, a prominent item in the list meets this criterion.
|
||||
|
||||
1. Source Code.
|
||||
|
||||
The "source code" for a work means the preferred form of the work
|
||||
for making modifications to it. "Object code" means any non-source
|
||||
form of a work.
|
||||
|
||||
A "Standard Interface" means an interface that either is an official
|
||||
standard defined by a recognized standards body, or, in the case of
|
||||
interfaces specified for a particular programming language, one that
|
||||
is widely used among developers working in that language.
|
||||
|
||||
The "System Libraries" of an executable work include anything, other
|
||||
than the work as a whole, that (a) is included in the normal form of
|
||||
packaging a Major Component, but which is not part of that Major
|
||||
Component, and (b) serves only to enable use of the work with that
|
||||
Major Component, or to implement a Standard Interface for which an
|
||||
implementation is available to the public in source code form. A
|
||||
"Major Component", in this context, means a major essential component
|
||||
(kernel, window system, and so on) of the specific operating system
|
||||
(if any) on which the executable work runs, or a compiler used to
|
||||
produce the work, or an object code interpreter used to run it.
|
||||
|
||||
The "Corresponding Source" for a work in object code form means all
|
||||
the source code needed to generate, install, and (for an executable
|
||||
work) run the object code and to modify the work, including scripts to
|
||||
control those activities. However, it does not include the work's
|
||||
System Libraries, or general-purpose tools or generally available free
|
||||
programs which are used unmodified in performing those activities but
|
||||
which are not part of the work. For example, Corresponding Source
|
||||
includes interface definition files associated with source files for
|
||||
the work, and the source code for shared libraries and dynamically
|
||||
linked subprograms that the work is specifically designed to require,
|
||||
such as by intimate data communication or control flow between those
|
||||
subprograms and other parts of the work.
|
||||
|
||||
The Corresponding Source need not include anything that users
|
||||
can regenerate automatically from other parts of the Corresponding
|
||||
Source.
|
||||
|
||||
The Corresponding Source for a work in source code form is that
|
||||
same work.
|
||||
|
||||
2. Basic Permissions.
|
||||
|
||||
All rights granted under this License are granted for the term of
|
||||
copyright on the Program, and are irrevocable provided the stated
|
||||
conditions are met. This License explicitly affirms your unlimited
|
||||
permission to run the unmodified Program. The output from running a
|
||||
covered work is covered by this License only if the output, given its
|
||||
content, constitutes a covered work. This License acknowledges your
|
||||
rights of fair use or other equivalent, as provided by copyright law.
|
||||
|
||||
You may make, run and propagate covered works that you do not
|
||||
convey, without conditions so long as your license otherwise remains
|
||||
in force. You may convey covered works to others for the sole purpose
|
||||
of having them make modifications exclusively for you, or provide you
|
||||
with facilities for running those works, provided that you comply with
|
||||
the terms of this License in conveying all material for which you do
|
||||
not control copyright. Those thus making or running the covered works
|
||||
for you must do so exclusively on your behalf, under your direction
|
||||
and control, on terms that prohibit them from making any copies of
|
||||
your copyrighted material outside their relationship with you.
|
||||
|
||||
Conveying under any other circumstances is permitted solely under
|
||||
the conditions stated below. Sublicensing is not allowed; section 10
|
||||
makes it unnecessary.
|
||||
|
||||
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
|
||||
|
||||
No covered work shall be deemed part of an effective technological
|
||||
measure under any applicable law fulfilling obligations under article
|
||||
11 of the WIPO copyright treaty adopted on 20 December 1996, or
|
||||
similar laws prohibiting or restricting circumvention of such
|
||||
measures.
|
||||
|
||||
When you convey a covered work, you waive any legal power to forbid
|
||||
circumvention of technological measures to the extent such circumvention
|
||||
is effected by exercising rights under this License with respect to
|
||||
the covered work, and you disclaim any intention to limit operation or
|
||||
modification of the work as a means of enforcing, against the work's
|
||||
users, your or third parties' legal rights to forbid circumvention of
|
||||
technological measures.
|
||||
|
||||
4. Conveying Verbatim Copies.
|
||||
|
||||
You may convey verbatim copies of the Program's source code as you
|
||||
receive it, in any medium, provided that you conspicuously and
|
||||
appropriately publish on each copy an appropriate copyright notice;
|
||||
keep intact all notices stating that this License and any
|
||||
non-permissive terms added in accord with section 7 apply to the code;
|
||||
keep intact all notices of the absence of any warranty; and give all
|
||||
recipients a copy of this License along with the Program.
|
||||
|
||||
You may charge any price or no price for each copy that you convey,
|
||||
and you may offer support or warranty protection for a fee.
|
||||
|
||||
5. Conveying Modified Source Versions.
|
||||
|
||||
You may convey a work based on the Program, or the modifications to
|
||||
produce it from the Program, in the form of source code under the
|
||||
terms of section 4, provided that you also meet all of these conditions:
|
||||
|
||||
a) The work must carry prominent notices stating that you modified
|
||||
it, and giving a relevant date.
|
||||
|
||||
b) The work must carry prominent notices stating that it is
|
||||
released under this License and any conditions added under section
|
||||
7. This requirement modifies the requirement in section 4 to
|
||||
"keep intact all notices".
|
||||
|
||||
c) You must license the entire work, as a whole, under this
|
||||
License to anyone who comes into possession of a copy. This
|
||||
License will therefore apply, along with any applicable section 7
|
||||
additional terms, to the whole of the work, and all its parts,
|
||||
regardless of how they are packaged. This License gives no
|
||||
permission to license the work in any other way, but it does not
|
||||
invalidate such permission if you have separately received it.
|
||||
|
||||
d) If the work has interactive user interfaces, each must display
|
||||
Appropriate Legal Notices; however, if the Program has interactive
|
||||
interfaces that do not display Appropriate Legal Notices, your
|
||||
work need not make them do so.
|
||||
|
||||
A compilation of a covered work with other separate and independent
|
||||
works, which are not by their nature extensions of the covered work,
|
||||
and which are not combined with it such as to form a larger program,
|
||||
in or on a volume of a storage or distribution medium, is called an
|
||||
"aggregate" if the compilation and its resulting copyright are not
|
||||
used to limit the access or legal rights of the compilation's users
|
||||
beyond what the individual works permit. Inclusion of a covered work
|
||||
in an aggregate does not cause this License to apply to the other
|
||||
parts of the aggregate.
|
||||
|
||||
6. Conveying Non-Source Forms.
|
||||
|
||||
You may convey a covered work in object code form under the terms
|
||||
of sections 4 and 5, provided that you also convey the
|
||||
machine-readable Corresponding Source under the terms of this License,
|
||||
in one of these ways:
|
||||
|
||||
a) Convey the object code in, or embodied in, a physical product
|
||||
(including a physical distribution medium), accompanied by the
|
||||
Corresponding Source fixed on a durable physical medium
|
||||
customarily used for software interchange.
|
||||
|
||||
b) Convey the object code in, or embodied in, a physical product
|
||||
(including a physical distribution medium), accompanied by a
|
||||
written offer, valid for at least three years and valid for as
|
||||
long as you offer spare parts or customer support for that product
|
||||
model, to give anyone who possesses the object code either (1) a
|
||||
copy of the Corresponding Source for all the software in the
|
||||
product that is covered by this License, on a durable physical
|
||||
medium customarily used for software interchange, for a price no
|
||||
more than your reasonable cost of physically performing this
|
||||
conveying of source, or (2) access to copy the
|
||||
Corresponding Source from a network server at no charge.
|
||||
|
||||
c) Convey individual copies of the object code with a copy of the
|
||||
written offer to provide the Corresponding Source. This
|
||||
alternative is allowed only occasionally and noncommercially, and
|
||||
only if you received the object code with such an offer, in accord
|
||||
with subsection 6b.
|
||||
|
||||
d) Convey the object code by offering access from a designated
|
||||
place (gratis or for a charge), and offer equivalent access to the
|
||||
Corresponding Source in the same way through the same place at no
|
||||
further charge. You need not require recipients to copy the
|
||||
Corresponding Source along with the object code. If the place to
|
||||
copy the object code is a network server, the Corresponding Source
|
||||
may be on a different server (operated by you or a third party)
|
||||
that supports equivalent copying facilities, provided you maintain
|
||||
clear directions next to the object code saying where to find the
|
||||
Corresponding Source. Regardless of what server hosts the
|
||||
Corresponding Source, you remain obligated to ensure that it is
|
||||
available for as long as needed to satisfy these requirements.
|
||||
|
||||
e) Convey the object code using peer-to-peer transmission, provided
|
||||
you inform other peers where the object code and Corresponding
|
||||
Source of the work are being offered to the general public at no
|
||||
charge under subsection 6d.
|
||||
|
||||
A separable portion of the object code, whose source code is excluded
|
||||
from the Corresponding Source as a System Library, need not be
|
||||
included in conveying the object code work.
|
||||
|
||||
A "User Product" is either (1) a "consumer product", which means any
|
||||
tangible personal property which is normally used for personal, family,
|
||||
or household purposes, or (2) anything designed or sold for incorporation
|
||||
into a dwelling. In determining whether a product is a consumer product,
|
||||
doubtful cases shall be resolved in favor of coverage. For a particular
|
||||
product received by a particular user, "normally used" refers to a
|
||||
typical or common use of that class of product, regardless of the status
|
||||
of the particular user or of the way in which the particular user
|
||||
actually uses, or expects or is expected to use, the product. A product
|
||||
is a consumer product regardless of whether the product has substantial
|
||||
commercial, industrial or non-consumer uses, unless such uses represent
|
||||
the only significant mode of use of the product.
|
||||
|
||||
"Installation Information" for a User Product means any methods,
|
||||
procedures, authorization keys, or other information required to install
|
||||
and execute modified versions of a covered work in that User Product from
|
||||
a modified version of its Corresponding Source. The information must
|
||||
suffice to ensure that the continued functioning of the modified object
|
||||
code is in no case prevented or interfered with solely because
|
||||
modification has been made.
|
||||
|
||||
If you convey an object code work under this section in, or with, or
|
||||
specifically for use in, a User Product, and the conveying occurs as
|
||||
part of a transaction in which the right of possession and use of the
|
||||
User Product is transferred to the recipient in perpetuity or for a
|
||||
fixed term (regardless of how the transaction is characterized), the
|
||||
Corresponding Source conveyed under this section must be accompanied
|
||||
by the Installation Information. But this requirement does not apply
|
||||
if neither you nor any third party retains the ability to install
|
||||
modified object code on the User Product (for example, the work has
|
||||
been installed in ROM).
|
||||
|
||||
The requirement to provide Installation Information does not include a
|
||||
requirement to continue to provide support service, warranty, or updates
|
||||
for a work that has been modified or installed by the recipient, or for
|
||||
the User Product in which it has been modified or installed. Access to a
|
||||
network may be denied when the modification itself materially and
|
||||
adversely affects the operation of the network or violates the rules and
|
||||
protocols for communication across the network.
|
||||
|
||||
Corresponding Source conveyed, and Installation Information provided,
|
||||
in accord with this section must be in a format that is publicly
|
||||
documented (and with an implementation available to the public in
|
||||
source code form), and must require no special password or key for
|
||||
unpacking, reading or copying.
|
||||
|
||||
7. Additional Terms.
|
||||
|
||||
"Additional permissions" are terms that supplement the terms of this
|
||||
License by making exceptions from one or more of its conditions.
|
||||
Additional permissions that are applicable to the entire Program shall
|
||||
be treated as though they were included in this License, to the extent
|
||||
that they are valid under applicable law. If additional permissions
|
||||
apply only to part of the Program, that part may be used separately
|
||||
under those permissions, but the entire Program remains governed by
|
||||
this License without regard to the additional permissions.
|
||||
|
||||
When you convey a copy of a covered work, you may at your option
|
||||
remove any additional permissions from that copy, or from any part of
|
||||
it. (Additional permissions may be written to require their own
|
||||
removal in certain cases when you modify the work.) You may place
|
||||
additional permissions on material, added by you to a covered work,
|
||||
for which you have or can give appropriate copyright permission.
|
||||
|
||||
Notwithstanding any other provision of this License, for material you
|
||||
add to a covered work, you may (if authorized by the copyright holders of
|
||||
that material) supplement the terms of this License with terms:
|
||||
|
||||
a) Disclaiming warranty or limiting liability differently from the
|
||||
terms of sections 15 and 16 of this License; or
|
||||
|
||||
b) Requiring preservation of specified reasonable legal notices or
|
||||
author attributions in that material or in the Appropriate Legal
|
||||
Notices displayed by works containing it; or
|
||||
|
||||
c) Prohibiting misrepresentation of the origin of that material, or
|
||||
requiring that modified versions of such material be marked in
|
||||
reasonable ways as different from the original version; or
|
||||
|
||||
d) Limiting the use for publicity purposes of names of licensors or
|
||||
authors of the material; or
|
||||
|
||||
e) Declining to grant rights under trademark law for use of some
|
||||
trade names, trademarks, or service marks; or
|
||||
|
||||
f) Requiring indemnification of licensors and authors of that
|
||||
material by anyone who conveys the material (or modified versions of
|
||||
it) with contractual assumptions of liability to the recipient, for
|
||||
any liability that these contractual assumptions directly impose on
|
||||
those licensors and authors.
|
||||
|
||||
All other non-permissive additional terms are considered "further
|
||||
restrictions" within the meaning of section 10. If the Program as you
|
||||
received it, or any part of it, contains a notice stating that it is
|
||||
governed by this License along with a term that is a further
|
||||
restriction, you may remove that term. If a license document contains
|
||||
a further restriction but permits relicensing or conveying under this
|
||||
License, you may add to a covered work material governed by the terms
|
||||
of that license document, provided that the further restriction does
|
||||
not survive such relicensing or conveying.
|
||||
|
||||
If you add terms to a covered work in accord with this section, you
|
||||
must place, in the relevant source files, a statement of the
|
||||
additional terms that apply to those files, or a notice indicating
|
||||
where to find the applicable terms.
|
||||
|
||||
Additional terms, permissive or non-permissive, may be stated in the
|
||||
form of a separately written license, or stated as exceptions;
|
||||
the above requirements apply either way.
|
||||
|
||||
8. Termination.
|
||||
|
||||
You may not propagate or modify a covered work except as expressly
|
||||
provided under this License. Any attempt otherwise to propagate or
|
||||
modify it is void, and will automatically terminate your rights under
|
||||
this License (including any patent licenses granted under the third
|
||||
paragraph of section 11).
|
||||
|
||||
However, if you cease all violation of this License, then your
|
||||
license from a particular copyright holder is reinstated (a)
|
||||
provisionally, unless and until the copyright holder explicitly and
|
||||
finally terminates your license, and (b) permanently, if the copyright
|
||||
holder fails to notify you of the violation by some reasonable means
|
||||
prior to 60 days after the cessation.
|
||||
|
||||
Moreover, your license from a particular copyright holder is
|
||||
reinstated permanently if the copyright holder notifies you of the
|
||||
violation by some reasonable means, this is the first time you have
|
||||
received notice of violation of this License (for any work) from that
|
||||
copyright holder, and you cure the violation prior to 30 days after
|
||||
your receipt of the notice.
|
||||
|
||||
Termination of your rights under this section does not terminate the
|
||||
licenses of parties who have received copies or rights from you under
|
||||
this License. If your rights have been terminated and not permanently
|
||||
reinstated, you do not qualify to receive new licenses for the same
|
||||
material under section 10.
|
||||
|
||||
9. Acceptance Not Required for Having Copies.
|
||||
|
||||
You are not required to accept this License in order to receive or
|
||||
run a copy of the Program. Ancillary propagation of a covered work
|
||||
occurring solely as a consequence of using peer-to-peer transmission
|
||||
to receive a copy likewise does not require acceptance. However,
|
||||
nothing other than this License grants you permission to propagate or
|
||||
modify any covered work. These actions infringe copyright if you do
|
||||
not accept this License. Therefore, by modifying or propagating a
|
||||
covered work, you indicate your acceptance of this License to do so.
|
||||
|
||||
10. Automatic Licensing of Downstream Recipients.
|
||||
|
||||
Each time you convey a covered work, the recipient automatically
|
||||
receives a license from the original licensors, to run, modify and
|
||||
propagate that work, subject to this License. You are not responsible
|
||||
for enforcing compliance by third parties with this License.
|
||||
|
||||
An "entity transaction" is a transaction transferring control of an
|
||||
organization, or substantially all assets of one, or subdividing an
|
||||
organization, or merging organizations. If propagation of a covered
|
||||
work results from an entity transaction, each party to that
|
||||
transaction who receives a copy of the work also receives whatever
|
||||
licenses to the work the party's predecessor in interest had or could
|
||||
give under the previous paragraph, plus a right to possession of the
|
||||
Corresponding Source of the work from the predecessor in interest, if
|
||||
the predecessor has it or can get it with reasonable efforts.
|
||||
|
||||
You may not impose any further restrictions on the exercise of the
|
||||
rights granted or affirmed under this License. For example, you may
|
||||
not impose a license fee, royalty, or other charge for exercise of
|
||||
rights granted under this License, and you may not initiate litigation
|
||||
(including a cross-claim or counterclaim in a lawsuit) alleging that
|
||||
any patent claim is infringed by making, using, selling, offering for
|
||||
sale, or importing the Program or any portion of it.
|
||||
|
||||
11. Patents.
|
||||
|
||||
A "contributor" is a copyright holder who authorizes use under this
|
||||
License of the Program or a work on which the Program is based. The
|
||||
work thus licensed is called the contributor's "contributor version".
|
||||
|
||||
A contributor's "essential patent claims" are all patent claims
|
||||
owned or controlled by the contributor, whether already acquired or
|
||||
hereafter acquired, that would be infringed by some manner, permitted
|
||||
by this License, of making, using, or selling its contributor version,
|
||||
but do not include claims that would be infringed only as a
|
||||
consequence of further modification of the contributor version. For
|
||||
purposes of this definition, "control" includes the right to grant
|
||||
patent sublicenses in a manner consistent with the requirements of
|
||||
this License.
|
||||
|
||||
Each contributor grants you a non-exclusive, worldwide, royalty-free
|
||||
patent license under the contributor's essential patent claims, to
|
||||
make, use, sell, offer for sale, import and otherwise run, modify and
|
||||
propagate the contents of its contributor version.
|
||||
|
||||
In the following three paragraphs, a "patent license" is any express
|
||||
agreement or commitment, however denominated, not to enforce a patent
|
||||
(such as an express permission to practice a patent or covenant not to
|
||||
sue for patent infringement). To "grant" such a patent license to a
|
||||
party means to make such an agreement or commitment not to enforce a
|
||||
patent against the party.
|
||||
|
||||
If you convey a covered work, knowingly relying on a patent license,
|
||||
and the Corresponding Source of the work is not available for anyone
|
||||
to copy, free of charge and under the terms of this License, through a
|
||||
publicly available network server or other readily accessible means,
|
||||
then you must either (1) cause the Corresponding Source to be so
|
||||
available, or (2) arrange to deprive yourself of the benefit of the
|
||||
patent license for this particular work, or (3) arrange, in a manner
|
||||
consistent with the requirements of this License, to extend the patent
|
||||
license to downstream recipients. "Knowingly relying" means you have
|
||||
actual knowledge that, but for the patent license, your conveying the
|
||||
covered work in a country, or your recipient's use of the covered work
|
||||
in a country, would infringe one or more identifiable patents in that
|
||||
country that you have reason to believe are valid.
|
||||
|
||||
If, pursuant to or in connection with a single transaction or
|
||||
arrangement, you convey, or propagate by procuring conveyance of, a
|
||||
covered work, and grant a patent license to some of the parties
|
||||
receiving the covered work authorizing them to use, propagate, modify
|
||||
or convey a specific copy of the covered work, then the patent license
|
||||
you grant is automatically extended to all recipients of the covered
|
||||
work and works based on it.
|
||||
|
||||
A patent license is "discriminatory" if it does not include within
|
||||
the scope of its coverage, prohibits the exercise of, or is
|
||||
conditioned on the non-exercise of one or more of the rights that are
|
||||
specifically granted under this License. You may not convey a covered
|
||||
work if you are a party to an arrangement with a third party that is
|
||||
in the business of distributing software, under which you make payment
|
||||
to the third party based on the extent of your activity of conveying
|
||||
the work, and under which the third party grants, to any of the
|
||||
parties who would receive the covered work from you, a discriminatory
|
||||
patent license (a) in connection with copies of the covered work
|
||||
conveyed by you (or copies made from those copies), or (b) primarily
|
||||
for and in connection with specific products or compilations that
|
||||
contain the covered work, unless you entered into that arrangement,
|
||||
or that patent license was granted, prior to 28 March 2007.
|
||||
|
||||
Nothing in this License shall be construed as excluding or limiting
|
||||
any implied license or other defenses to infringement that may
|
||||
otherwise be available to you under applicable patent law.
|
||||
|
||||
12. No Surrender of Others' Freedom.
|
||||
|
||||
If conditions are imposed on you (whether by court order, agreement or
|
||||
otherwise) that contradict the conditions of this License, they do not
|
||||
excuse you from the conditions of this License. If you cannot convey a
|
||||
covered work so as to satisfy simultaneously your obligations under this
|
||||
License and any other pertinent obligations, then as a consequence you may
|
||||
not convey it at all. For example, if you agree to terms that obligate you
|
||||
to collect a royalty for further conveying from those to whom you convey
|
||||
the Program, the only way you could satisfy both those terms and this
|
||||
License would be to refrain entirely from conveying the Program.
|
||||
|
||||
13. Use with the GNU Affero General Public License.
|
||||
|
||||
Notwithstanding any other provision of this License, you have
|
||||
permission to link or combine any covered work with a work licensed
|
||||
under version 3 of the GNU Affero General Public License into a single
|
||||
combined work, and to convey the resulting work. The terms of this
|
||||
License will continue to apply to the part which is the covered work,
|
||||
but the special requirements of the GNU Affero General Public License,
|
||||
section 13, concerning interaction through a network will apply to the
|
||||
combination as such.
|
||||
|
||||
14. Revised Versions of this License.
|
||||
|
||||
The Free Software Foundation may publish revised and/or new versions of
|
||||
the GNU General Public License from time to time. Such new versions will
|
||||
be similar in spirit to the present version, but may differ in detail to
|
||||
address new problems or concerns.
|
||||
|
||||
Each version is given a distinguishing version number. If the
|
||||
Program specifies that a certain numbered version of the GNU General
|
||||
Public License "or any later version" applies to it, you have the
|
||||
option of following the terms and conditions either of that numbered
|
||||
version or of any later version published by the Free Software
|
||||
Foundation. If the Program does not specify a version number of the
|
||||
GNU General Public License, you may choose any version ever published
|
||||
by the Free Software Foundation.
|
||||
|
||||
If the Program specifies that a proxy can decide which future
|
||||
versions of the GNU General Public License can be used, that proxy's
|
||||
public statement of acceptance of a version permanently authorizes you
|
||||
to choose that version for the Program.
|
||||
|
||||
Later license versions may give you additional or different
|
||||
permissions. However, no additional obligations are imposed on any
|
||||
author or copyright holder as a result of your choosing to follow a
|
||||
later version.
|
||||
|
||||
15. Disclaimer of Warranty.
|
||||
|
||||
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
|
||||
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
|
||||
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
|
||||
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
|
||||
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
|
||||
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
|
||||
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
|
||||
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
|
||||
|
||||
16. Limitation of Liability.
|
||||
|
||||
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
|
||||
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
|
||||
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
|
||||
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
|
||||
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
|
||||
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
|
||||
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
|
||||
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
|
||||
SUCH DAMAGES.
|
||||
|
||||
17. Interpretation of Sections 15 and 16.
|
||||
|
||||
If the disclaimer of warranty and limitation of liability provided
|
||||
above cannot be given local legal effect according to their terms,
|
||||
reviewing courts shall apply local law that most closely approximates
|
||||
an absolute waiver of all civil liability in connection with the
|
||||
Program, unless a warranty or assumption of liability accompanies a
|
||||
copy of the Program in return for a fee.
|
||||
|
||||
END OF TERMS AND CONDITIONS
|
||||
|
||||
How to Apply These Terms to Your New Programs
|
||||
|
||||
If you develop a new program, and you want it to be of the greatest
|
||||
possible use to the public, the best way to achieve this is to make it
|
||||
free software which everyone can redistribute and change under these terms.
|
||||
|
||||
To do so, attach the following notices to the program. It is safest
|
||||
to attach them to the start of each source file to most effectively
|
||||
state the exclusion of warranty; and each file should have at least
|
||||
the "copyright" line and a pointer to where the full notice is found.
|
||||
|
||||
<one line to give the program's name and a brief idea of what it does.>
|
||||
Copyright (C) <year> <name of author>
|
||||
|
||||
This program is free software: you can redistribute it and/or modify
|
||||
it under the terms of the GNU General Public License as published by
|
||||
the Free Software Foundation, either version 3 of the License, or
|
||||
(at your option) any later version.
|
||||
|
||||
This program is distributed in the hope that it will be useful,
|
||||
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
||||
GNU General Public License for more details.
|
||||
|
||||
You should have received a copy of the GNU General Public License
|
||||
along with this program. If not, see <https://www.gnu.org/licenses/>.
|
||||
|
||||
Also add information on how to contact you by electronic and paper mail.
|
||||
|
||||
If the program does terminal interaction, make it output a short
|
||||
notice like this when it starts in an interactive mode:
|
||||
|
||||
<program> Copyright (C) <year> <name of author>
|
||||
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
|
||||
This is free software, and you are welcome to redistribute it
|
||||
under certain conditions; type `show c' for details.
|
||||
|
||||
The hypothetical commands `show w' and `show c' should show the appropriate
|
||||
parts of the General Public License. Of course, your program's commands
|
||||
might be different; for a GUI interface, you would use an "about box".
|
||||
|
||||
You should also get your employer (if you work as a programmer) or school,
|
||||
if any, to sign a "copyright disclaimer" for the program, if necessary.
|
||||
For more information on this, and how to apply and follow the GNU GPL, see
|
||||
<https://www.gnu.org/licenses/>.
|
||||
|
||||
The GNU General Public License does not permit incorporating your program
|
||||
into proprietary programs. If your program is a subroutine library, you
|
||||
may consider it more useful to permit linking proprietary applications with
|
||||
the library. If this is what you want to do, use the GNU Lesser General
|
||||
Public License instead of this License. But first, please read
|
||||
<https://www.gnu.org/licenses/why-not-lgpl.html>.
|
||||
61
README.md
61
README.md
|
|
@ -1,57 +1,16 @@
|
|||
# SelfPrivacy App
|
||||
# selfprivacy
|
||||
|
||||
SelfPrivacy — is a platform on your cloud hosting, that allows to deploy your own private services and control them using mobile application.
|
||||
selfprivacy.org
|
||||
|
||||
To use this application, you'll be required to create accounts of different service providers. Please reffer to this manual: https://selfprivacy.org/docs/getting-started/
|
||||
## Getting Started
|
||||
|
||||
Application will do the following things for you:
|
||||
This project is a starting point for a Flutter application.
|
||||
|
||||
1. Create your personal server
|
||||
2. Setup NixOS
|
||||
3. Bring all services to the ready-to-use state. Services include:
|
||||
A few resources to get you started if this is your first Flutter project:
|
||||
|
||||
* E-mail, ready to use with DeltaChat
|
||||
* NextCloud - your personal cloud storage
|
||||
* Bitwarden — secure and private password manager
|
||||
* Pleroma — your private fediverse space for blogging
|
||||
* Jitsi — awesome Zoom alternative
|
||||
* Gitea — your own Git server
|
||||
* OpenConnect — Personal VPN server
|
||||
- [Lab: Write your first Flutter app](https://flutter.dev/docs/get-started/codelab)
|
||||
- [Cookbook: Useful Flutter samples](https://flutter.dev/docs/cookbook)
|
||||
|
||||
**Project is currently in open beta state**. Feel free to try it. It would be much appreciated if you would provide us with some feedback.
|
||||
|
||||
## Building
|
||||
|
||||
Supported platforms are Android, Linux, and Windows. We are looking forward to support iOS and macOS builds.
|
||||
|
||||
For Linux builds, make sure you have these packages installed:
|
||||
|Arch-based|Debian-based|
|
||||
|----------|------------|
|
||||
|pacman -S ninja xdg-user-dirs gnome-keyring unzip xz-utils zip|apt install ninja-build xdg-user-dirs gnome-keyring unzip xz-utils zip|
|
||||
|
||||
Install [Flutter](https://docs.flutter.dev/get-started/install/linux) and [Android SDK tools](https://developer.android.com/studio/command-line/sdkmanager), then try your setup:
|
||||
|
||||
```
|
||||
flutter pub get
|
||||
|
||||
# Build .APK for Android
|
||||
flutter build --flavor production apk
|
||||
# Build AAB bundle for Google Play
|
||||
flutter build --flavor production aab
|
||||
# Build Linux binaries
|
||||
flutter build linux
|
||||
# Build Windows binaries
|
||||
flutter build windows
|
||||
|
||||
# Package AppImage
|
||||
appimage-builder --recipe appimage.yml
|
||||
# Package Flatpak
|
||||
flatpak-builder --force-clean --repo=flatpak-repo flatpak-build flatpak.yml
|
||||
flatpak build-bundle flatpak-repo org.selfprivacy.app.flatpak org.selfprivacy.app
|
||||
```
|
||||
|
||||
## Translations
|
||||
|
||||
[](http://weblate.selfprivacy.org/engage/selfprivacy/)
|
||||
|
||||
Translations are stored in `assets/translations/*.json` and can be edited on <https://weblate.selfprivacy.org/projects/selfprivacy/selfprivacy-app/>.
|
||||
For help getting started with Flutter, view our
|
||||
[online documentation](https://flutter.dev/docs), which offers tutorials,
|
||||
samples, guidance on mobile development, and a full API reference.
|
||||
|
|
|
|||
|
|
@ -1,76 +0,0 @@
|
|||
# This file configures the analyzer, which statically analyzes Dart code to
|
||||
# check for errors, warnings, and lints.
|
||||
#
|
||||
# The issues identified by the analyzer are surfaced in the UI of Dart-enabled
|
||||
# IDEs (https://dart.dev/tools#ides-and-editors). The analyzer can also be
|
||||
# invoked from the command line by running `flutter analyze`.
|
||||
|
||||
# The following line activates a set of recommended lints for Flutter apps,
|
||||
# packages, and plugins designed to encourage good coding practices.
|
||||
include: package:flutter_lints/flutter.yaml
|
||||
|
||||
analyzer:
|
||||
exclude:
|
||||
- lib/generated_plugin_registrant.dart
|
||||
- lib/**.g.dart
|
||||
- lib/**.graphql.dart
|
||||
|
||||
linter:
|
||||
# The lint rules applied to this project can be customized in the
|
||||
# section below to disable rules from the `package:flutter_lints/flutter.yaml`
|
||||
# included above or to enable additional rules. A list of all available lints
|
||||
# and their documentation is published at
|
||||
# https://dart-lang.github.io/linter/lints/index.html.
|
||||
#
|
||||
# Instead of disabling a lint rule for the entire project in the
|
||||
# section below, it can also be suppressed for a single line of code
|
||||
# or a specific dart file by using the `// ignore: name_of_lint` and
|
||||
# `// ignore_for_file: name_of_lint` syntax on the line or in the file
|
||||
# producing the lint.
|
||||
rules:
|
||||
avoid_print: false # Uncomment to disable the `avoid_print` rule
|
||||
always_declare_return_types: true
|
||||
always_put_control_body_on_new_line: true
|
||||
always_put_required_named_parameters_first: true
|
||||
always_use_package_imports: true
|
||||
avoid_escaping_inner_quotes: true
|
||||
avoid_setters_without_getters: true
|
||||
collection_methods_unrelated_type: true
|
||||
combinators_ordering: true
|
||||
directives_ordering: true
|
||||
eol_at_end_of_file: true
|
||||
no_adjacent_strings_in_list: true
|
||||
prefer_constructors_over_static_methods: true
|
||||
prefer_expression_function_bodies: true
|
||||
prefer_final_in_for_each: true
|
||||
prefer_final_locals: true
|
||||
prefer_final_parameters: true
|
||||
prefer_foreach: true
|
||||
prefer_if_elements_to_conditional_expressions: true
|
||||
prefer_mixin: true
|
||||
prefer_null_aware_method_calls: true
|
||||
prefer_single_quotes: true
|
||||
require_trailing_commas: true
|
||||
sized_box_shrink_expand: true
|
||||
sort_constructors_first: true
|
||||
unawaited_futures: true
|
||||
unnecessary_await_in_return: true
|
||||
unnecessary_null_aware_operator_on_extension_on_nullable: true
|
||||
unnecessary_null_checks: true
|
||||
unnecessary_parenthesis: true
|
||||
unnecessary_statements: true
|
||||
unnecessary_to_list_in_spreads: true
|
||||
unreachable_from_main: true
|
||||
use_enums: true
|
||||
use_if_null_to_convert_nulls_to_bools: true
|
||||
use_is_even_rather_than_modulo: true
|
||||
use_late_for_private_fields_and_variables: true
|
||||
use_named_constants: true
|
||||
use_setters_to_change_properties: true
|
||||
use_string_buffers: true
|
||||
use_string_in_part_of_directives: true
|
||||
use_super_parameters: true
|
||||
use_to_and_as_if_applicable: true
|
||||
|
||||
# Additional information about this file can be found at
|
||||
# https://dart.dev/guides/language/analysis-options
|
||||
|
|
@ -26,65 +26,30 @@ apply plugin: 'kotlin-android'
|
|||
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"
|
||||
|
||||
android {
|
||||
namespace 'org.selfprivacy.app'
|
||||
|
||||
compileSdkVersion flutter.compileSdkVersion
|
||||
ndkVersion flutter.ndkVersion
|
||||
compileSdkVersion 29
|
||||
|
||||
sourceSets {
|
||||
main.java.srcDirs += 'src/main/kotlin'
|
||||
}
|
||||
|
||||
compileOptions {
|
||||
sourceCompatibility JavaVersion.VERSION_1_8
|
||||
targetCompatibility JavaVersion.VERSION_1_8
|
||||
}
|
||||
|
||||
kotlinOptions {
|
||||
jvmTarget = '1.8'
|
||||
}
|
||||
|
||||
lintOptions {
|
||||
disable 'InvalidPackage'
|
||||
}
|
||||
|
||||
defaultConfig {
|
||||
// TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
|
||||
applicationId "org.selfprivacy.app"
|
||||
minSdkVersion 21
|
||||
targetSdkVersion 34
|
||||
compileSdkVersion 34
|
||||
applicationId "pro.kherel.selfprivacy"
|
||||
minSdkVersion 18
|
||||
targetSdkVersion 29
|
||||
versionCode flutterVersionCode.toInteger()
|
||||
versionName flutterVersionName
|
||||
}
|
||||
|
||||
flavorDimensions "default"
|
||||
productFlavors {
|
||||
fdroid {
|
||||
applicationId "pro.kherel.selfprivacy"
|
||||
}
|
||||
production {
|
||||
applicationIdSuffix ""
|
||||
}
|
||||
nightly {
|
||||
applicationIdSuffix ".nightly"
|
||||
versionCode project.getVersionCode()
|
||||
versionName "nightly-" + project.getVersionCode()
|
||||
}
|
||||
}
|
||||
|
||||
flavorDimensions "default"
|
||||
productFlavors {
|
||||
fdroid {
|
||||
applicationId "pro.kherel.selfprivacy"
|
||||
}
|
||||
production {
|
||||
applicationIdSuffix ""
|
||||
}
|
||||
nightly {
|
||||
applicationIdSuffix ".nightly"
|
||||
versionCode project.getVersionCode()
|
||||
versionName "nightly-" + project.getVersionCode()
|
||||
buildTypes {
|
||||
release {
|
||||
// TODO: Add your own signing config for the release build.
|
||||
// Signing with the debug keys for now, so `flutter run --release` works.
|
||||
signingConfig signingConfigs.debug
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
|
||||
package="org.selfprivacy.app">
|
||||
package="pro.kherel.selfprivacy">
|
||||
<!-- Flutter needs it to communicate with the running application
|
||||
to allow setting breakpoints, to provide hot reload, etc.
|
||||
-->
|
||||
|
|
|
|||
|
|
@ -1,20 +1,20 @@
|
|||
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
|
||||
package="org.selfprivacy.app">
|
||||
package="pro.kherel.selfprivacy">
|
||||
<uses-permission android:name="android.permission.INTERNET" />
|
||||
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
|
||||
<!-- io.flutter.app.FlutterApplication is an android.app.Application that
|
||||
calls FlutterMain.startInitialization(this); in its onCreate method.
|
||||
In most cases you can leave this as-is, but you if you want to provide
|
||||
additional functionality it is fine to subclass or reimplement
|
||||
FlutterApplication and put your custom class here. -->
|
||||
<application
|
||||
android:name="${applicationName}"
|
||||
android:name="io.flutter.app.FlutterApplication"
|
||||
android:label="SelfPrivacy"
|
||||
android:icon="@mipmap/launcher_icon">
|
||||
<activity
|
||||
android:name=".MainActivity"
|
||||
android:launchMode="singleTop"
|
||||
android:theme="@style/LaunchTheme"
|
||||
android:exported="true"
|
||||
android:configChanges="orientation|keyboardHidden|keyboard|screenSize|smallestScreenSize|locale|layoutDirection|fontScale|screenLayout|density|uiMode"
|
||||
android:hardwareAccelerated="true"
|
||||
android:windowSoftInputMode="adjustResize"
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
package org.selfprivacy.app
|
||||
package pro.kherel.selfprivacy
|
||||
|
||||
import io.flutter.embedding.android.FlutterActivity
|
||||
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<!-- Modify this file to customize your launch splash screen -->
|
||||
<layer-list xmlns:android="http://schemas.android.com/apk/res/android">
|
||||
<item android:drawable="?android:colorBackground" />
|
||||
|
||||
<!-- You can insert your own image assets here -->
|
||||
<!-- <item>
|
||||
<bitmap
|
||||
android:gravity="center"
|
||||
android:src="@mipmap/launch_image" />
|
||||
</item> -->
|
||||
</layer-list>
|
||||
|
|
@ -1,18 +0,0 @@
|
|||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<resources>
|
||||
<!-- Theme applied to the Android Window while the process is starting when the OS's Dark Mode setting is on -->
|
||||
<style name="LaunchTheme" parent="@android:style/Theme.Black.NoTitleBar">
|
||||
<!-- Show a splash screen on the activity. Automatically removed when
|
||||
Flutter draws its first frame -->
|
||||
<item name="android:windowBackground">@drawable/launch_background</item>
|
||||
</style>
|
||||
<!-- Theme applied to the Android Window as soon as the process has started.
|
||||
This theme determines the color of the Android Window while your
|
||||
Flutter UI initializes, as well as behind your Flutter UI while its
|
||||
running.
|
||||
|
||||
This Theme is only used starting with V2 of Flutter's Android embedding. -->
|
||||
<style name="NormalTheme" parent="@android:style/Theme.Black.NoTitleBar">
|
||||
<item name="android:windowBackground">?android:colorBackground</item>
|
||||
</style>
|
||||
</resources>
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
|
||||
xmlns:tools="http://schemas.android.com/tools"
|
||||
package="org.selfprivacy.app">
|
||||
<application
|
||||
tools:replace="android:label"
|
||||
android:label="SelfPrivacy (Nightly)">
|
||||
</application>
|
||||
</manifest>
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 544 B |
Binary file not shown.
|
Before Width: | Height: | Size: 2.0 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 442 B |
Binary file not shown.
|
Before Width: | Height: | Size: 1.5 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 721 B |
Binary file not shown.
|
Before Width: | Height: | Size: 2.6 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 1.0 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.6 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 1.4 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.7 KiB |
|
|
@ -1,5 +1,5 @@
|
|||
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
|
||||
package="org.selfprivacy.app">
|
||||
package="pro.kherel.selfprivacy">
|
||||
<!-- Flutter needs it to communicate with the running application
|
||||
to allow setting breakpoints, to provide hot reload, etc.
|
||||
-->
|
||||
|
|
|
|||
|
|
@ -1,25 +1,12 @@
|
|||
buildscript {
|
||||
ext.kotlin_version = '1.9.21'
|
||||
ext.getVersionCode = { ->
|
||||
try {
|
||||
def stdout = new ByteArrayOutputStream()
|
||||
exec {
|
||||
commandLine 'git', 'rev-list', '--first-parent', '--count', 'HEAD'
|
||||
standardOutput = stdout
|
||||
}
|
||||
return Integer.parseInt(stdout.toString().trim())
|
||||
}
|
||||
catch (ignored) {
|
||||
return -1
|
||||
}
|
||||
}
|
||||
ext.kotlin_version = '1.3.50'
|
||||
repositories {
|
||||
google()
|
||||
jcenter()
|
||||
}
|
||||
|
||||
dependencies {
|
||||
classpath 'com.android.tools.build:gradle:7.1.2'
|
||||
classpath 'com.android.tools.build:gradle:3.5.0'
|
||||
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
|
||||
}
|
||||
}
|
||||
|
|
@ -39,6 +26,6 @@ subprojects {
|
|||
project.evaluationDependsOn(':app')
|
||||
}
|
||||
|
||||
tasks.register("clean", Delete) {
|
||||
task clean(type: Delete) {
|
||||
delete rootProject.buildDir
|
||||
}
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
org.gradle.jvmargs=-Xmx1536M
|
||||
android.useAndroidX=true
|
||||
android.enableJetifier=true
|
||||
android.bundle.enableUncompressedNativeLibs=false
|
||||
android.enableR8=true
|
||||
|
|
|
|||
|
|
@ -3,4 +3,4 @@ distributionBase=GRADLE_USER_HOME
|
|||
distributionPath=wrapper/dists
|
||||
zipStoreBase=GRADLE_USER_HOME
|
||||
zipStorePath=wrapper/dists
|
||||
distributionUrl=https\://services.gradle.org/distributions/gradle-7.6-all.zip
|
||||
distributionUrl=https\://services.gradle.org/distributions/gradle-5.6.2-all.zip
|
||||
|
|
|
|||
54
appimage.yml
54
appimage.yml
|
|
@ -1,54 +0,0 @@
|
|||
# appimage-builder recipe see https://appimage-builder.readthedocs.io for details
|
||||
version: 1
|
||||
script:
|
||||
- rm -rf AppDir || true
|
||||
- cp -r build/linux/x64/release/bundle AppDir
|
||||
- install -Dm644 assets/images/icon/logo.svg AppDir/usr/share/icons/hicolor/scalable/apps/org.selfprivacy.app.svg
|
||||
AppDir:
|
||||
path: AppDir
|
||||
app_info:
|
||||
id: org.selfprivacy.app
|
||||
name: SelfPrivacy
|
||||
icon: org.selfprivacy.app
|
||||
version: 0.11.0
|
||||
exec: selfprivacy
|
||||
exec_args: $@
|
||||
apt:
|
||||
arch:
|
||||
- amd64
|
||||
allow_unauthenticated: true
|
||||
sources:
|
||||
- sourceline: deb http://archive.ubuntu.com/ubuntu/ jammy main restricted
|
||||
- sourceline: deb http://archive.ubuntu.com/ubuntu/ jammy-updates main restricted
|
||||
- sourceline: deb http://archive.ubuntu.com/ubuntu/ jammy universe
|
||||
- sourceline: deb http://archive.ubuntu.com/ubuntu/ jammy-updates universe
|
||||
- sourceline: deb http://archive.ubuntu.com/ubuntu/ jammy multiverse
|
||||
- sourceline: deb http://archive.ubuntu.com/ubuntu/ jammy-updates multiverse
|
||||
- sourceline: deb http://archive.ubuntu.com/ubuntu/ jammy-backports main restricted universe multiverse
|
||||
- sourceline: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted
|
||||
- sourceline: deb http://security.ubuntu.com/ubuntu/ jammy-security universe
|
||||
- sourceline: deb http://security.ubuntu.com/ubuntu/ jammy-security multiverse
|
||||
include:
|
||||
- libjsoncpp-dev
|
||||
- libsecret-1-0
|
||||
- xdg-desktop-portal
|
||||
test:
|
||||
fedora-30:
|
||||
image: appimagecrafters/tests-env:fedora-30
|
||||
command: ./AppRun
|
||||
debian-stable:
|
||||
image: appimagecrafters/tests-env:debian-stable
|
||||
command: ./AppRun
|
||||
archlinux-latest:
|
||||
image: appimagecrafters/tests-env:archlinux-latest
|
||||
command: ./AppRun
|
||||
centos-7:
|
||||
image: appimagecrafters/tests-env:centos-7
|
||||
command: ./AppRun
|
||||
ubuntu-xenial:
|
||||
image: appimagecrafters/tests-env:ubuntu-xenial
|
||||
command: ./AppRun
|
||||
AppImage:
|
||||
arch: x86_64
|
||||
update-information: guess
|
||||
comp: xz
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 2.1 MiB |
Binary file not shown.
|
Before Width: | Height: | Size: 2.6 MiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.3 MiB |
|
|
@ -1,9 +0,0 @@
|
|||
<svg width="186" height="186" viewBox="0 0 186 186" fill="none" xmlns="http://www.w3.org/2000/svg">
|
||||
<path d="M181.85 0H179.81C180.898 0 181.782 0.882482 181.782 1.96861V180.23C181.782 181.316 180.898 182.199 179.81 182.199H14.7574C13.6692 182.199 12.7852 181.316 12.7852 180.23V181.859C12.7852 184.167 14.6893 186 16.9336 186H181.85C184.162 186 185.998 184.167 185.998 181.859V4.14088C186.066 1.83285 184.162 0 181.85 0Z" fill="#EFCD29"/>
|
||||
<path d="M87.0484 106.577C87.1164 106.577 87.1164 106.645 87.1164 106.645L81.1999 131.287H105.478L99.5617 106.645C99.5617 106.577 99.5617 106.577 99.6297 106.577C105.138 104.133 109.015 98.6347 109.015 92.2537C109.015 80.9172 96.9774 72.4318 84.9402 78.8129C82.832 79.9669 80.9958 81.7318 79.9077 83.8362C74.7392 93.4756 79.2277 103.183 87.0484 106.577Z" fill="#FFDD00"/>
|
||||
<path d="M87.0484 106.577C87.1164 106.577 87.1164 106.645 87.1164 106.645L81.1999 131.287H105.478L99.5617 106.645C99.5617 106.577 99.5617 106.577 99.6297 106.577C105.138 104.133 109.015 98.6347 109.015 92.2537C109.015 80.9172 96.9774 72.4318 84.9402 78.8129C82.832 79.9669 80.9958 81.7318 79.9077 83.8362C74.7392 93.4756 79.2277 103.183 87.0484 106.577Z" fill="#FFDD00"/>
|
||||
<path d="M14.7574 182.199H179.81C180.898 182.199 181.782 181.316 181.782 180.23V1.96861C181.782 0.882482 180.898 0 179.81 0H17.0016H14.8254C13.7372 0 12.8532 0.882482 12.8532 1.96861V4.14088V46.3642H95.2092L125.336 82.4102L127.444 84.9898V148.257H12.7852V160.612V180.23C12.7852 181.316 13.6692 182.199 14.7574 182.199Z" fill="#FFDD00"/>
|
||||
<path d="M14.7574 182.199H179.81C180.898 182.199 181.782 181.316 181.782 180.23V1.96861C181.782 0.882482 180.898 0 179.81 0H17.0016H14.8254C13.7372 0 12.8532 0.882482 12.8532 1.96861V4.14088V46.3642H95.2092L125.336 82.4102L127.444 84.9898V148.257H12.7852V160.612V180.23C12.7852 181.316 13.6692 182.199 14.7574 182.199Z" fill="#FFDD00"/>
|
||||
<path d="M125.336 145.677V82.4102L95.2093 46.3643H12.7853H0V145.677H125.336ZM79.9078 83.9037C81.0639 81.7993 82.8321 80.0343 84.9403 78.8803C96.9095 72.4993 109.015 80.9847 109.015 92.3212C109.015 98.7022 105.138 104.201 99.6298 106.645C99.5618 106.645 99.5618 106.712 99.5618 106.712L105.478 131.354H81.2L87.1165 106.712C87.1165 106.645 87.1165 106.645 87.0485 106.645C79.2278 103.182 74.7393 93.4752 79.9078 83.9037Z" fill="#404548"/>
|
||||
<path d="M127.444 148.257V84.9902L125.336 82.4785V145.678H0L12.7853 160.68V148.257H127.444Z" fill="#333638"/>
|
||||
</svg>
|
||||
|
Before Width: | Height: | Size: 2.4 KiB |
|
|
@ -1 +0,0 @@
|
|||
<svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 209.51 94.74"><defs><style>.cls-1{fill:#fff;}</style></defs><path class="cls-1" d="M143.05,93.42l1.07-3.71c1.27-4.41.8-8.48-1.34-11.48-2-2.76-5.26-4.38-9.25-4.57L58,72.7a1.47,1.47,0,0,1-1.35-2,2,2,0,0,1,1.75-1.34l76.26-1c9-.41,18.84-7.75,22.27-16.71l4.34-11.36a2.68,2.68,0,0,0,.18-1,3.31,3.31,0,0,0-.06-.54,49.67,49.67,0,0,0-95.49-5.14,22.35,22.35,0,0,0-35,23.42A31.73,31.73,0,0,0,.34,93.45a1.47,1.47,0,0,0,1.45,1.27l139.49,0h0A1.83,1.83,0,0,0,143.05,93.42Z"/><path class="cls-1" d="M168.22,41.15q-1,0-2.1.06a.88.88,0,0,0-.32.07,1.17,1.17,0,0,0-.76.8l-3,10.26c-1.28,4.41-.81,8.48,1.34,11.48a11.65,11.65,0,0,0,9.24,4.57l16.11,1a1.44,1.44,0,0,1,1.14.62,1.5,1.5,0,0,1,.17,1.37,2,2,0,0,1-1.75,1.34l-16.73,1c-9.09.42-18.88,7.75-22.31,16.7l-1.21,3.16a.9.9,0,0,0,.79,1.22h57.63A1.55,1.55,0,0,0,208,93.63a41.34,41.34,0,0,0-39.76-52.48Z"/></svg>
|
||||
|
Before Width: | Height: | Size: 923 B |
|
|
@ -1,89 +0,0 @@
|
|||
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
|
||||
<!-- Created with Inkscape (http://www.inkscape.org/) -->
|
||||
|
||||
<svg
|
||||
xmlns:dc="http://purl.org/dc/elements/1.1/"
|
||||
xmlns:cc="http://creativecommons.org/ns#"
|
||||
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
|
||||
xmlns:svg="http://www.w3.org/2000/svg"
|
||||
xmlns="http://www.w3.org/2000/svg"
|
||||
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
|
||||
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
|
||||
width="7.4053912mm"
|
||||
height="7.5173831mm"
|
||||
viewBox="0 0 7.4053913 7.5173831"
|
||||
version="1.1"
|
||||
id="svg1262"
|
||||
sodipodi:docname="logo.notext.svg"
|
||||
inkscape:version="0.92.4 (5da689c313, 2019-01-14)">
|
||||
<defs
|
||||
id="defs1256" />
|
||||
<sodipodi:namedview
|
||||
id="base"
|
||||
pagecolor="#ffffff"
|
||||
bordercolor="#666666"
|
||||
borderopacity="1.0"
|
||||
inkscape:pageopacity="0.0"
|
||||
inkscape:pageshadow="2"
|
||||
inkscape:zoom="5.6"
|
||||
inkscape:cx="101.86078"
|
||||
inkscape:cy="8.9271745"
|
||||
inkscape:document-units="mm"
|
||||
inkscape:current-layer="g3885"
|
||||
showgrid="false"
|
||||
fit-margin-top="0"
|
||||
fit-margin-left="0"
|
||||
fit-margin-right="0"
|
||||
fit-margin-bottom="0"
|
||||
inkscape:window-width="2560"
|
||||
inkscape:window-height="1365"
|
||||
inkscape:window-x="0"
|
||||
inkscape:window-y="38"
|
||||
inkscape:window-maximized="1" />
|
||||
<metadata
|
||||
id="metadata1259">
|
||||
<rdf:RDF>
|
||||
<cc:Work
|
||||
rdf:about="">
|
||||
<dc:format>image/svg+xml</dc:format>
|
||||
<dc:type
|
||||
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
|
||||
<dc:title></dc:title>
|
||||
</cc:Work>
|
||||
</rdf:RDF>
|
||||
</metadata>
|
||||
<g
|
||||
inkscape:label="Layer 1"
|
||||
inkscape:groupmode="layer"
|
||||
id="layer1"
|
||||
transform="translate(-254.94057,-266.78298)">
|
||||
<g
|
||||
id="g3885"
|
||||
transform="matrix(0.26519825,0,0,0.26519825,228.89366,215.69135)"
|
||||
style="fill:#000000">
|
||||
<g
|
||||
style="fill:#000000;stroke:#ffffff;stroke-opacity:1"
|
||||
id="layer1-9"
|
||||
transform="matrix(0.22901929,0,0,0.22901929,26.296508,84.906304)"
|
||||
inkscape:export-filename="/home/nils/git/desec-stack/webapp/src/assets/logo.png"
|
||||
inkscape:export-xdpi="567.52002"
|
||||
inkscape:export-ydpi="567.52002">
|
||||
<g
|
||||
style="fill:#000000;stroke:#ffffff;stroke-opacity:1"
|
||||
transform="translate(-194.13584,150.8067)"
|
||||
id="g3933">
|
||||
<path
|
||||
inkscape:connector-curvature="0"
|
||||
d="m 509.13584,366.2239 c 8.87906,-33.13708 42.93987,-52.8021 76.07695,-43.92304 21.43594,5.74374 38.17931,22.48711 43.92305,43.92304 0,0 -6.09923,-6.07815 -10,-6.07815 -3.90077,0 -10,6.07815 -10,6.07815 0,0 -6.09923,-6.07815 -10,-6.07815 -3.90077,0 -10,6.07815 -10,6.07815 0,0 -6.09923,-6.07815 -10,-6.07815 -3.90077,0 -10,6.07815 -10,6.07815 0,0 -6.09923,-6.07815 -10,-6.07815 -3.90077,0 -10,6.07815 -10,6.07815 0,0 -6.09923,-6.07815 -10,-6.07815 -3.90077,0 -10,6.07815 -10,6.07815 0,0 -6.09923,-6.07815 -10,-6.07815 -3.90077,0 -10,6.07815 -10,6.07815 z"
|
||||
id="path2985-6-3"
|
||||
style="color:#000000;display:inline;overflow:visible;visibility:visible;fill:#000000;fill-opacity:1;stroke:#ffffff;stroke-width:0.99999994;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker:none;enable-background:accumulate" />
|
||||
<path
|
||||
inkscape:connector-curvature="0"
|
||||
d="m 567.42674,364.89583 v 61.87321 c 0,9.34738 5.48085,16.17306 12.23879,16.17306 6.75795,0 12.23635,-6.83606 12.23635,-16.18344 0,0 -1.07806,-1.02674 -1.75904,-1.03964 -0.64261,-0.0122 -1.69589,0.91753 -1.69589,0.91753 0,6.70817 -3.93157,13.01592 -8.78142,13.01592 -4.84984,0 -8.78142,-6.30775 -8.78142,-13.01592 l -7.6e-4,-61.74072 z"
|
||||
id="path3775-7-4-6"
|
||||
style="color:#000000;display:inline;overflow:visible;visibility:visible;fill:#000000;fill-opacity:1;stroke:#ffffff;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:117.14173126;stroke-opacity:1;marker:none;enable-background:accumulate" />
|
||||
</g>
|
||||
</g>
|
||||
</g>
|
||||
</g>
|
||||
</svg>
|
||||
|
Before Width: | Height: | Size: 4.0 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 36 KiB |
|
|
@ -1,6 +0,0 @@
|
|||
<svg width="24" height="25" viewBox="0 0 24 25" fill="none" xmlns="http://www.w3.org/2000/svg">
|
||||
<path d="M12.0013 24.0128V19.3592C16.927 19.3592 20.7505 14.4743 18.8591 9.2901C18.1652 7.37152 16.6276 5.83395 14.709 5.14C9.52482 3.26224 4.63995 7.07217 4.63995 11.9979H0C0 4.14669 7.59264 -1.97641 15.8248 0.595295C19.417 1.72467 22.2881 4.58211 23.4038 8.17433C25.9755 16.4201 19.8661 24.0128 12.0013 24.0128Z" fill="white"/>
|
||||
<path d="M12.0149 19.3729H7.38855V14.7466H12.0149V19.3729Z" fill="white"/>
|
||||
<path d="M7.38861 22.9376H3.82361V19.3726H7.38861V22.9376Z" fill="white"/>
|
||||
<path d="M3.82354 19.373H0.843628V16.3931H3.82354V19.373Z" fill="white"/>
|
||||
</svg>
|
||||
|
Before Width: | Height: | Size: 657 B |
|
|
@ -1,10 +0,0 @@
|
|||
<svg width="24" height="23" viewBox="0 0 24 23" fill="none" xmlns="http://www.w3.org/2000/svg">
|
||||
<g clip-path="url(#clip0_51804_9018)">
|
||||
<path d="M22.5704 0H19.3252C18.5948 0 18.2817 0.302609 18.2817 1.04348V9.25565H5.35304V1.04348C5.35304 0.313043 5.05044 0 4.30957 0H1.04348C0.302609 0 0 0.302609 0 1.04348V22.1739C0 22.9148 0.302609 23.2174 1.04348 23.2174H4.30957C5.04 23.2174 5.35304 22.9252 5.35304 22.1739V13.8261H18.2922V22.1739C18.2922 22.9043 18.5948 23.2174 19.3357 23.2174H22.5809C23.3113 23.2174 23.6243 22.9148 23.6243 22.1739V1.04348C23.6035 0.333913 23.3009 0 22.5704 0Z" fill="white"/>
|
||||
</g>
|
||||
<defs>
|
||||
<clipPath id="clip0_51804_9018">
|
||||
<rect width="24" height="22.9565" fill="white"/>
|
||||
</clipPath>
|
||||
</defs>
|
||||
</svg>
|
||||
|
Before Width: | Height: | Size: 722 B |
Binary file not shown.
|
Before Width: | Height: | Size: 22 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 11 KiB |
|
|
@ -0,0 +1,12 @@
|
|||
### About us
|
||||
|
||||
More and more corporations want to control our data.
|
||||
We want to have full control of our **data** on our own.
|
||||
|
||||
### Our mission
|
||||
|
||||
Digital independence and privacy, available to everyone
|
||||
|
||||
### Target
|
||||
|
||||
Develop the program, which will allow everyone to deploy their private services for themselves and their neighbours.
|
||||
|
|
@ -0,0 +1,12 @@
|
|||
### О проекте
|
||||
|
||||
Всё больше организаций хотят владеть нашими данными
|
||||
Проект позволяет только Вам в полной мере распоряжаться собственными **данными** на своём сервере.
|
||||
|
||||
### Миссия проекта
|
||||
|
||||
Цифровая независимость и приватность доступная каждому.
|
||||
|
||||
### Цель
|
||||
|
||||
Развивать программу, которая позволит каждому создавать приватные сервисы для себя и своих близких.
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
### Як атрымаць Backblaze API Token
|
||||
1. Перайдзіце па спасылцы https://secure.backblaze.com/user_signin.htm і аўтарызуйцеся
|
||||
2. У левай частцы інтэрфейсу абярыце **App Keys** y **B2 Cloud Storage** падкатэгорыі.
|
||||
3. Націсніце на сінюю кнопку **Generate New Master Application Key**.
|
||||
4. Пацвердзіце стварэнне ва ўсплываючым акне.
|
||||
5. Схавайце _keyID_ і _applicationKey_ у бяспечным месце. Напрыклад, у мэнеджэры пароляў.
|
||||
|
||||
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
### Jak získat Backblaze API Token
|
||||
1. Navštivte následující odkaz a autorizujte se: https://secure.backblaze.com/user_signin.htm
|
||||
2. V levé části rozhraní vyberte položku **App Keys** v podkategorii **B2 Cloud Storage**.
|
||||
3. Klikněte na modré tlačítko **Generate New Master Application Key** (Vygenerovat nový hlavní aplikační klíč**).
|
||||
4. V zobrazeném vyskakovacím okně potvrďte vygenerování.
|
||||
5. Save _keyID_ and _applicationKey_ in the safe place.. Například ve správci hesel.
|
||||
|
||||
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
### So erhalten Sie das Backblaze-API-Token
|
||||
1. Besuchen Sie den folgenden Link und melden Sie sich an: https://secure.backblaze.com/user_signin.htm
|
||||
2. Wählen Sie auf der linken Seite der Benutzeroberfläche **App Keys** in der Unterkategorie **B2 Cloud Storage** aus.
|
||||
3. Klicken Sie auf die blaue Schaltfläche **Generate New Master Application Key**.
|
||||
4. Bestätigen Sie im erscheinenden Popup-Fenster die Generierung.
|
||||
5. Speichern Sie _keyID_ und _applicationKey_ an einem sicheren Ort. Zum Beispiel im Passwort-Manager.
|
||||
|
||||
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
### How to get Backblaze API Token
|
||||
1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm
|
||||
2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory.
|
||||
3. Click on the blue **Generate New Master Application Key** button.
|
||||
4. In the appeared pop-up window confirm the generation.
|
||||
5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager.
|
||||
|
||||
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
### How to get Backblaze API Token
|
||||
1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm
|
||||
2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory.
|
||||
3. Click on the blue **Generate New Master Application Key** button.
|
||||
4. In the appeared pop-up window confirm the generation.
|
||||
5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager.
|
||||
|
||||
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
### How to get Backblaze API Token
|
||||
1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm
|
||||
2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory.
|
||||
3. Click on the blue **Generate New Master Application Key** button.
|
||||
4. In the appeared pop-up window confirm the generation.
|
||||
5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager.
|
||||
|
||||
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
### How to get Backblaze API Token
|
||||
1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm
|
||||
2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory.
|
||||
3. Click on the blue **Generate New Master Application Key** button.
|
||||
4. In the appeared pop-up window confirm the generation.
|
||||
5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager.
|
||||
|
||||
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
### How to get Backblaze API Token
|
||||
1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm
|
||||
2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory.
|
||||
3. Click on the blue **Generate New Master Application Key** button.
|
||||
4. In the appeared pop-up window confirm the generation.
|
||||
5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager.
|
||||
|
||||
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
### How to get Backblaze API Token
|
||||
1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm
|
||||
2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory.
|
||||
3. Click on the blue **Generate New Master Application Key** button.
|
||||
4. In the appeared pop-up window confirm the generation.
|
||||
5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager.
|
||||
|
||||
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
### How to get Backblaze API Token
|
||||
1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm
|
||||
2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory.
|
||||
3. Click on the blue **Generate New Master Application Key** button.
|
||||
4. In the appeared pop-up window confirm the generation.
|
||||
5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager.
|
||||
|
||||
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
### Jak otrzymać Backblaze API Token
|
||||
1. Odwiedź poniższy link i autoryzuj: https://secure.backblaze.com/user_signin.htm
|
||||
2. Po lewej stronie wybierz **App Keys** w podkategorіі **B2 Cloud Storage**.
|
||||
3. Naciśnij **Generate New Master Application Key**.
|
||||
4. W wyświetlonym oknie podręcznym potwierdź generację.
|
||||
5. Zapisz _keyID_ i _applicationKey_ w bezpiecznym miejscu. Na przykład w menedżerze haseł.
|
||||
|
||||
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
### Как получить Backblaze API Token
|
||||
1. Переходим по ссылке https://secure.backblaze.com/user_signin.htm и авторизуемся.
|
||||
2. В левой части интерфейса выбираем **App Keys** в подкатегории **"Account"**.
|
||||
3. Нажимаем на синюю кнопку **Generate New Master Application Key**.
|
||||
4. Во всплывающем окне подтверждаем генерацию.
|
||||
5. Сохраняем _keyID_ и _applicationKey_ в надёжном месте. Например в менеджере паролей.
|
||||
|
||||
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
### Ako získať token API spoločnosti Backblaze
|
||||
1. Navštívte nasledujúci odkaz a autorizujte sa: https://secure.backblaze.com/user_signin.htm
|
||||
2. Na ľavej strane rozhrania vyberte položku **App Keys** v podkategórii **B2 Cloud Storage** podkategória.
|
||||
3. Kliknite na modré tlačidlo **Generate New Master Application Key**.
|
||||
4. V zobrazenom pop-up okne potvrďte generovanie.
|
||||
5. Uložte _keyID_ and _applicationKey_ in bezpečné miesto. Napríklad v správcovi hesiel.
|
||||
|
||||
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
### How to get Backblaze API Token
|
||||
1. Visit the following link and authorize: https://secure.backblaze.com/user_signin.htm
|
||||
2. On the left side of the interface, select **App Keys** in the **B2 Cloud Storage** subcategory.
|
||||
3. Click on the blue **Generate New Master Application Key** button.
|
||||
4. In the appeared pop-up window confirm the generation.
|
||||
5. Save _keyID_ and _applicationKey_ in the safe place. For example, in the password manager.
|
||||
|
||||
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
## Як отримати Backblaze API токен
|
||||
1. Перейдіть за посиланням і авторизуйте: https://secure.backblaze.com/user_signin.htm
|
||||
2. У лівій частині інтерфейсу виберіть **App Keys** у підкатегорії **B2 Cloud Storage**.
|
||||
3. Натисніть кнопку синій **Створити новий майстер-ключ програми**.
|
||||
4. У з'явилось спливаюче вікно підтверджують покоління.
|
||||
5. Save _KeyID_ and _applicationKey_ in the safe place. Наприклад, в менеджері паролів.
|
||||
|
||||
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
### Як атрымаць токен Cloudflare API
|
||||
1. Перайдзіце па наступнай спасылцы: https://dash.cloudflare.com/
|
||||
2. У правым куце націсніце на значок профілю (чалавек у крузе). Для мабільнай версіі сайта ў левым верхнім куце націсніце кнопку **Menu** (тры гарызантальныя палоскі), у выпадальным меню націсніце **My Profile**.
|
||||
3. Ёсць чатыры катэгорыі канфігурацыі на выбар: *Communication*, *Authentication*, **API Tokens**, *Session*. Выберыце **API Tokens**.
|
||||
4. Націсніце на кнопку **Create Token**.
|
||||
5. Спусціцеся ўніз і паглядзіце поле **Create Custom Token** і націсніце кнопку **Get Started** справа.
|
||||
6. У полі **Token Name** дайце назву токену.
|
||||
7. Далей у нас налады. У крайнім левым полі абярыце **Zone**. У самым доўгім полі па цэнтры абярыце **DNS**. У крайнім правым полі абярыце **Edit**.
|
||||
8. Далей прама пад гэтым радком націсніце «Дадаць яшчэ». З'явіцца аналагічнае поле.
|
||||
9. У самым левым полі новага радка выберыце аналагічна папярэдняму радку — **Zone**. У цэнтры — крыху іншае. Тут абярыце тое ж, што і злева — **Zone**. У крайнім правым полі абярыце **Read**.
|
||||
10. Далей паглядзіце на **Resources Zone**. Пад гэтым надпісам радок з двума палямі. Злева павінна быць **Include**, а справа павінна быць **Specific Zone**. Пасля таго як вы выберыце канкрэтную зону, справа з'явіцца іншае поле. Выберыце ў ім свой дамен.
|
||||
11. Прагартайце ўніз і націсніце сінюю кнопку **Continue to Summary**.
|
||||
12. Правер, ці ўсё ў цябе правільна. Аналагічны радок павінен прысутнічаць: *Domain — DNS:Edit, Zone:Read*.
|
||||
13. Націсніце на **Create Token**.
|
||||
14. Створаны токен капіюем і захоўваем у надзейным месцы (пажадана ў мэнэджару пароляў).
|
||||
|
||||
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
### Jak získat token API Cloudflare
|
||||
1. Přejděte na následující odkaz: https://dash.cloudflare.com/.
|
||||
2. V pravém rohu klikněte na ikonu profilu (mužík v kruhu). V případě mobilní verze webu klikněte v levém horním rohu na **Menu** (tři vodorovné pruhy), v rozbalovací nabídce klikněte na **My profile**.
|
||||
Na výběr jsou čtyři kategorie nastavení: *Communication*, *Authentication*, **API Tokens**, *Session*. Vyberte možnost **API Tokens**.
|
||||
4. Klikněte na tlačítko **Create Token**.
|
||||
5. Přejděte dolů, zobrazte pole **Create Custom Token** a klikněte na tlačítko **Get Started** vpravo.
|
||||
6. V poli **Token Name** pojmenujte svůj token.
|
||||
7. Dále máme přístupová práva. V poli zcela vlevo vyberte možnost **Zone**. V nejdelším poli uprostřed vyberte položku **DNS**. V pravém krajním poli vyberte možnost **Edit**.
|
||||
8. Poté hned pod tímto řádkem klepněte na tlačítko Přidat další. Zobrazí se podobné pole.
|
||||
9. Na zcela levé straně nového řádku vyberte totéž co u předchozího řádku - **Zone**. Prostřední pole se mírně liší. Zde vyberte totéž co na levém okraji - **Zone**. Na pravém okraji zcela vpravo vyberte možnost **Read**.
|
||||
10. Dále se podívejte na položku **Zone Resources**. Pod ním se nachází řádek se dvěma poli. V levém z nich by mělo být uvedeno **Include** a v pravém **Specific Zone**. Jakmile vyberete možnost Specifická zóna, objeví se vpravo další pole. V něm vyberte svou doménu.
|
||||
11. Přejděte úplně dolů a klikněte na modré tlačítko **Continue to Summary**.
|
||||
12. Zkontrolujte, zda jste vše provedli správně. Měl by se objevit podobný řádek: *Domain - DNS:Edit, Zone:Read*.
|
||||
13. Klepněte na tlačítko **Create Token**.
|
||||
14. Zkopírujte vytvořený token a uložte jej na bezpečné místo (nejlépe do správce hesel).
|
||||
|
||||
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
### Wie man Cloudflare API Token bekommt
|
||||
1. Besuchen Sie den folgenden link: https://dash.cloudflare.com/
|
||||
2. Klicken Sie in der rechten Ecke auf das Profilsymbol (ein Mann in einem Kreis). Bei der mobilen Version der Website klicken Sie in der oberen linken Ecke auf die Schaltfläche **Menu** (drei horizontale Balken), im Dropdown-Menü klicken Sie auf **My Profile**
|
||||
3. Es gibt vier Konfigurationskategorien, aus denen Sie wählen können: *Communication*, *Authentication*, **API Tokens**, *Session*. Wählen Sie **API Tokens**.
|
||||
4. Klicken Sie auf die Schaltfläche **Create Token**.
|
||||
5. Gehen Sie nach unten und sehen Sie das Feld **Create Custom Token** und klicken Sie auf der rechten Seite auf die Schaltfläche **Get Started**.
|
||||
6. Geben Sie in das Feld **Token Name** einen Namen für Ihr Token ein.
|
||||
7. Als nächstes folgen die Berechtigungen. Wählen Sie im Feld ganz links **Zone**. Wählen Sie im längsten Feld in der Mitte **DNS**. Wählen Sie im Feld ganz rechts **Edit**.
|
||||
8. Klicken Sie anschließend direkt unter dieser Zeile auf Add More. Ein ähnliches Feld wird angezeigt.
|
||||
9. Wählen Sie im ganz linken Feld der neuen Zeile, ähnlich wie in der letzten Zeile, **Zone**. In der Mitte - ein wenig anders. Wählen Sie hier dasselbe wie in der linken Zeile - **Zone**. Im Feld ganz rechts wählen Sie **Read**.
|
||||
10. Als nächstes sehen Sie sich **Zone Resources** an. Unter dieser Aufschrift befindet sich eine Zeile mit zwei Feldern. Auf der linken Seite muss **Include** und auf der rechten Seite **Specific Zone** stehen. Sobald Sie Spezifische Zone auswählen, erscheint rechts ein weiteres Feld. Wählen Sie dort Ihre Domain aus.
|
||||
11. Streichen Sie nach unten und drücken Sie die blaue Schaltfläche **Continue to Summary**.
|
||||
12. Überprüfen Sie, ob Sie alles richtig gemacht haben. Eine ähnliche Zeichenfolge muss vorhanden sein: *Domain — DNS:Edit, Zone:Read*.
|
||||
13. Klicken Sie auf **Create Token**.
|
||||
14. Kopieren Sie das erstellte Token und speichern Sie es an einem zuverlässigen Ort (vorzugsweise im Passwort-Manager).
|
||||
|
||||
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
### How to get Cloudflare API Token
|
||||
1. Visit the following link: https://dash.cloudflare.com/
|
||||
2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile**
|
||||
3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**.
|
||||
4. Click on **Create Token** button.
|
||||
5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side.
|
||||
6. In the **Token Name** field, give your token a name.
|
||||
7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**.
|
||||
8. Next, right under this line, click Add More. Similar field will appear.
|
||||
9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**.
|
||||
10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it.
|
||||
11. Flick to the bottom and press the blue **Continue to Summary** button.
|
||||
12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*.
|
||||
13. Click on **Create Token**.
|
||||
14. We copy the created token, and save it in a reliable place (preferably in the password manager).
|
||||
|
||||
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
### How to get Cloudflare API Token
|
||||
1. Visit the following link: https://dash.cloudflare.com/
|
||||
2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile**
|
||||
3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**.
|
||||
4. Click on **Create Token** button.
|
||||
5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side.
|
||||
6. In the **Token Name** field, give your token a name.
|
||||
7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**.
|
||||
8. Next, right under this line, click Add More. Similar field will appear.
|
||||
9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**.
|
||||
10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it.
|
||||
11. Flick to the bottom and press the blue **Continue to Summary** button.
|
||||
12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*.
|
||||
13. Click on **Create Token**.
|
||||
14. We copy the created token, and save it in a reliable place (preferably in the password manager).
|
||||
|
||||
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
### How to get Cloudflare API Token
|
||||
1. Visit the following link: https://dash.cloudflare.com/
|
||||
2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile**
|
||||
3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**.
|
||||
4. Click on **Create Token** button.
|
||||
5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side.
|
||||
6. In the **Token Name** field, give your token a name.
|
||||
7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**.
|
||||
8. Next, right under this line, click Add More. Similar field will appear.
|
||||
9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**.
|
||||
10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it.
|
||||
11. Flick to the bottom and press the blue **Continue to Summary** button.
|
||||
12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*.
|
||||
13. Click on **Create Token**.
|
||||
14. We copy the created token, and save it in a reliable place (preferably in the password manager).
|
||||
|
||||
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
### How to get Cloudflare API Token
|
||||
1. Visit the following link: https://dash.cloudflare.com/
|
||||
2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile**
|
||||
3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**.
|
||||
4. Click on **Create Token** button.
|
||||
5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side.
|
||||
6. In the **Token Name** field, give your token a name.
|
||||
7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**.
|
||||
8. Next, right under this line, click Add More. Similar field will appear.
|
||||
9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**.
|
||||
10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it.
|
||||
11. Flick to the bottom and press the blue **Continue to Summary** button.
|
||||
12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*.
|
||||
13. Click on **Create Token**.
|
||||
14. We copy the created token, and save it in a reliable place (preferably in the password manager).
|
||||
|
||||
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
### How to get Cloudflare API Token
|
||||
1. Visit the following link: https://dash.cloudflare.com/
|
||||
2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile**
|
||||
3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**.
|
||||
4. Click on **Create Token** button.
|
||||
5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side.
|
||||
6. In the **Token Name** field, give your token a name.
|
||||
7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**.
|
||||
8. Next, right under this line, click Add More. Similar field will appear.
|
||||
9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**.
|
||||
10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it.
|
||||
11. Flick to the bottom and press the blue **Continue to Summary** button.
|
||||
12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*.
|
||||
13. Click on **Create Token**.
|
||||
14. We copy the created token, and save it in a reliable place (preferably in the password manager).
|
||||
|
||||
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
### How to get Cloudflare API Token
|
||||
1. Visit the following link: https://dash.cloudflare.com/
|
||||
2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile**
|
||||
3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**.
|
||||
4. Click on **Create Token** button.
|
||||
5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side.
|
||||
6. In the **Token Name** field, give your token a name.
|
||||
7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**.
|
||||
8. Next, right under this line, click Add More. Similar field will appear.
|
||||
9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**.
|
||||
10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it.
|
||||
11. Flick to the bottom and press the blue **Continue to Summary** button.
|
||||
12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*.
|
||||
13. Click on **Create Token**.
|
||||
14. We copy the created token, and save it in a reliable place (preferably in the password manager).
|
||||
|
||||
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
### How to get Cloudflare API Token
|
||||
1. Visit the following link: https://dash.cloudflare.com/
|
||||
2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile**
|
||||
3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**.
|
||||
4. Click on **Create Token** button.
|
||||
5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side.
|
||||
6. In the **Token Name** field, give your token a name.
|
||||
7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**.
|
||||
8. Next, right under this line, click Add More. Similar field will appear.
|
||||
9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**.
|
||||
10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it.
|
||||
11. Flick to the bottom and press the blue **Continue to Summary** button.
|
||||
12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*.
|
||||
13. Click on **Create Token**.
|
||||
14. We copy the created token, and save it in a reliable place (preferably in the password manager).
|
||||
|
||||
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
### Jak uzyskać token API Cloudflare'a
|
||||
1. Przejdź pod następujący link: https://dash.cloudflare.com/.
|
||||
2. W prawym rogu kliknij ikonę profilu (człowiek w kółku). W przypadku wersji mobilnej strony, w lewym górnym rogu kliknij **Menu** (trzy poziome paski), w rozwijanym menu kliknij **My Profile**.
|
||||
Do wyboru są cztery kategorie ustawień: *Communication*, *Authentication*, **API Tokens**, *Session*. Należy wybrać **API Tokens**.
|
||||
4. Kliknij przycisk **Create token**.
|
||||
5. Zjedź na dół, zobacz pole **Create Custom Token** i kliknij przycisk **Get Started** po prawej stronie.
|
||||
6. W polu **Token Name** nadaj nazwę swojemu tokenowi.
|
||||
7. Następnie mamy prawa dostępu. W skrajnie lewym polu wybierz **Zone**. W najdłuższym polu, środkowym, wybierz **DNS**. W skrajnie prawym polu wybierz **Edit**.
|
||||
8. Następnie, tuż pod tym wierszem, kliknij Add more. Pojawi się podobne pole.
|
||||
9. W skrajnie lewej części nowej linii wybierz to samo, co w poprzedniej linii - **Zone**. Środkowe pole jest nieco inne. Tutaj wybierz to samo, co na lewym marginesie - **Zone**. W skrajnie prawym marginesie wybierz **Read**.
|
||||
10. Następnie spójrz na **Strefę zasobów**. Poniżej tego znajduje się linia z dwoma polami. W lewym powinno być **Include**, a w prawym **Specific Zone**. Gdy wybierzesz Specific Zone, po prawej stronie pojawi się kolejne pole. Wybierz w nim swoją domenę.
|
||||
11. Przejdź na sam dół i kliknij niebieski przycisk **Continue to Summary**.
|
||||
12. Sprawdź, czy wszystko zrobiłeś poprawnie. Powinna pojawić się podobna linia: *Domain - DNS:Edit, Zone:Read*.
|
||||
13. Kliknij na **Create Token**.
|
||||
14. Skopiuj utworzony token i zapisz go w bezpiecznym miejscu (najlepiej w menedżerze haseł).
|
||||
|
||||
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
### Как получить токен API Cloudflare
|
||||
1. Перейдите по следующей ссылке: https://dash.cloudflare.com/.
|
||||
2. В правом углу нажмите на значок профиля (человечек в круге). Для мобильной версии сайта: в левом верхнем углу нажмите на кнопку **Menu** (три горизонтальные полоски), в выпадающем меню нажмите на **My Profile**.
|
||||
3. На выбор предлагаются четыре категории настроек: *Communication*, *Authentication*, **API Tokens**, *Session*. Выберите **API Tokens**.
|
||||
4. Нажмите на кнопку **Create token**.
|
||||
5. Спуститесь в самый низ, увидите поле **Create Custom Token** и нажмите кнопку **Get Started** справа.
|
||||
6. В поле **Token Name** дайте имя вашему токену.
|
||||
7. Далее у нас есть права доступа. В крайнем левом поле выберите **Zone**. В самом длинном поле, по центру, выберите **DNS**. В крайнем правом поле выберите **Edit**.
|
||||
8. Далее, прямо под этой строкой, нажмите **Добавить еще**. Появится аналогичное поле.
|
||||
9. В крайнем левом поле новой строки выберите, аналогично предыдущей строке - **Zone**. В центральном - немного иначе. Здесь выберите то же, что и в левом - **Zone**. В крайнем правом поле выберите **Read**.
|
||||
10. Далее посмотрите на **Resources Zone**. Под этой надписью находится строка с двумя полями. В левом должно быть **Include**, а в правом - **Specific Zone**. Как только вы выберете Specific Zone, справа появится еще одно поле. Выберите в нем свой домен.
|
||||
11. Перейдите в самый низ и нажмите синюю кнопку **Continue to Summary**.
|
||||
12. Проверьте, все ли вы сделали правильно. Должна присутствовать аналогичная строка: *Domain - DNS:Edit, Zone:Read*.
|
||||
13. Нажмите на **Create Token**.
|
||||
14. Копируем созданный токен и сохраняем его в надежном месте (желательно в менеджере паролей).
|
||||
|
||||
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
### Ako získať token API Cloudflare
|
||||
1. Navštívte nasledujúce prepojenie: https://dash.cloudflare.com/
|
||||
2. V pravom rohu kliknite na ikonu profilu (muž v kruhu). V prípade mobilnej verzie stránky kliknite v ľavom hornom rohu na tlačidlo **Menu** (tri vodorovné pruhy), v rozbaľovacej ponuke kliknite na **My profile**
|
||||
3. Na výber sú štyri kategórie konfigurácie: *Communication*, *Authentication*, **Toky API**, *Session*. Vyberte **API Tokens**.
|
||||
4. Kliknite na tlačidlo **Create Token**.
|
||||
5. Prejdite na spodnú časť a zobrazte pole **Create Custom Token** a stlačte tlačidlo **Get Started** na pravej strane.
|
||||
6. V poli **Token Name** zadajte svoj token.
|
||||
7. Ďalej tu máme položku Permissions. V ľavom krajnom poli vyberte položku **Zone**. V najdlhšom poli uprostred vyberte položku **DNS**. V krajnom pravom poli vyberte položku **Edit**.
|
||||
8. Ďalej priamo pod týmto riadkom kliknite na položku **Pridať ďalšie**. Zobrazí sa podobné pole.
|
||||
9. V krajnom ľavom poli nového riadku vyberte podobne ako v predchádzajúcom riadku - **Zone**. V strede - trochu inak. Tu vyberte rovnako ako v ľavom poli - **Zone**. V krajnom pravom poli vyberte položku **Read**.
|
||||
10. Ďalej sa pozrite na položku **Zone Resources**. Pod týmto nápisom sa nachádza riadok s dvoma poľami. V ľavom musí byť uvedené **Include** a v pravom **Specific Zone**. Keď vyberiete položku **Špecifická zóna**, vpravo sa objaví ďalšie pole. V ňom vyberte svoju doménu.
|
||||
11. Prejdite na spodnú časť a stlačte modré tlačidlo **Continue to Summary**.
|
||||
12. Skontrolujte, či máte všetko správne. Musí sa vyskytovať podobný reťazec: *Domain — DNS:Edit, Zone:Read*.
|
||||
13. Kliknite na **Create Token**.
|
||||
14. Vytvorený token skopírujeme a uložíme ho na spoľahlivé miesto (najlepšie do správcu hesiel).
|
||||
|
||||
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
### How to get Cloudflare API Token
|
||||
1. Visit the following link: https://dash.cloudflare.com/
|
||||
2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile**
|
||||
3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**.
|
||||
4. Click on **Create Token** button.
|
||||
5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side.
|
||||
6. In the **Token Name** field, give your token a name.
|
||||
7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**.
|
||||
8. Next, right under this line, click Add More. Similar field will appear.
|
||||
9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**.
|
||||
10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it.
|
||||
11. Flick to the bottom and press the blue **Continue to Summary** button.
|
||||
12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*.
|
||||
13. Click on **Create Token**.
|
||||
14. We copy the created token, and save it in a reliable place (preferably in the password manager).
|
||||
|
||||
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
### Як отримати токен Cloudflare API
|
||||
1. Перейдіть за цим посиланням: https://dash.cloudflare.com/
|
||||
2. В правому куті натисніть на іконку профілю (людина в колі). Для мобільної версії сайту, у верхньому лівому кутку натисніть кнопку **Menu** (три горизонтальні смужки), у випадаючому меню натисніть **My profile**
|
||||
3. Є чотири категорії конфігурації на вибір: *Communication*, *Authentication*, **API Tokens**, *Session*. Виберіть **API Tokens**.
|
||||
4. Натисніть кнопку **Create Token**.
|
||||
5. Спустіться вниз і перегляньте поле **Create Custom Token** і натисніть кнопку **Get Started** праворуч.
|
||||
6. У полі **Назва токена** введіть назву токена.
|
||||
7. Далі у нас є Дозволи. У крайньому лівому полі виберіть **Zone**. У найдовшому полі по центру виберіть **DNS**. У крайньому правому полі виберіть **Edit**.
|
||||
8. Далі прямо під цим рядком натисніть «Add more». З'явиться аналогічне поле.
|
||||
9. У крайньому лівому полі нового рядка виберіть, як і в останньому рядку, — **Zone**. У центрі — трохи інше. Тут вибираємо те саме, що й зліва — **Zone**. У крайньому правому полі виберіть **Read**.
|
||||
10. Далі подивіться на **Zone Resources**. Під цим написом — рядок із двома полями. Ліворуч має бути **Include**, а праворуч має бути **Specific Zone**. Після вибору «Specific Zone» праворуч з’явиться ще одне поле. Виберіть у ньому свій домен.
|
||||
11. Прокрутіть униз і натисніть синю кнопку **Continue to Summary**.
|
||||
12. Перевірте, чи все ви зробили правильно. Подібний рядок має бути присутнім: *Domain — DNS:Edit, Zone:Read*.
|
||||
13. Натисніть **Create Token**.
|
||||
14. Копіюємо створений токен і зберігаємо в надійному місці (бажано в менеджері паролів).
|
||||
|
||||
|
||||
|
|
@ -1,9 +0,0 @@
|
|||
### How to get deSEC API Token
|
||||
1. Log in at: https://desec.io/login
|
||||
2. Go to **Domains** page at: https://desec.io/domains
|
||||
3. Go to **Token management** tab.
|
||||
4. Click on the round "plus" button in the upper right corner.
|
||||
5. **"Generate New Token"** dialogue must be displayed. Enter any **Token name** you wish. *Advanced settings* are not required, so do not touch anything there.
|
||||
6. Click on **Save**.
|
||||
7. Make sure you save the token's "**secret value**" as it will only be displayed once.
|
||||
8. Now you can safely **close** the dialogue.
|
||||
|
|
@ -1,9 +0,0 @@
|
|||
### Как получить deSEC API Токен
|
||||
1. Авторизуемся в deSEC: https://desec.io/login
|
||||
2. Переходим на страницу **Domains** по ссылке: https://desec.io/domains
|
||||
3. Переходим на вкладку **Token management**.
|
||||
4. Нажимаем на большую кнопку с плюсом в правом верхнем углу страницы.
|
||||
5. Должен был появиться **"Generate New Token"** диалог. Вводим любое имя токена в **Token name**. *Advanced settings* необязательны, так что ничего там не трогаем.
|
||||
6. Кликаем **Save**.
|
||||
7. Обязательно сохраняем "**secret value**" ключ токена, потому что он отображается исключительно один раз.
|
||||
8. Теперь спокойно закрываем диалог, нажав **close**.
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
### Як атрымаць токен Digital Ocean API
|
||||
1. Перайдзіце па наступнай [link](https://cloud.digitalocean.com/) і падпішыцеся
|
||||
у толькі што створаны ўліковы запіс.
|
||||
2. Увайдзіце ў раней створаны праект. Калі вы яго не стварылі,
|
||||
тады, калі ласка, працягвайце.
|
||||
3. Перайдзіце па спасылцы "API" на панэлі злева.
|
||||
4. Націсніце на кнопку "Generation New Token".
|
||||
5. Увядзіце любую назву токена.
|
||||
6. Усталюйце час заканчэння тэрміну дзеяння на "No Expiry".
|
||||
7. Усталюйце сцяжок "Write (optional)".
|
||||
8. Цяпер націсніце на кнопку "Generate Token".
|
||||
9. Пасля гэтага будзе паказаны токен. Захоўвайце яго ў любым надзейным месцы, пажадана ў менеджэры пароляў.
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
### Jak získat token API Digital Ocean
|
||||
1. Navštivte následující [link](https://cloud.digitalocean.com/) a podepište se.
|
||||
k nově vytvořenému účtu.
|
||||
2. Vstupte do dříve vytvořeného projektu. Pokud jste žádný nevytvořili,
|
||||
pak prosím pokračujte.
|
||||
3. Přejděte na odkaz "API" na levé liště.
|
||||
4. Klikněte na tlačítko "Generate New Token" (Vygenerovat nový token).
|
||||
5. Zadejte libovolný název tokenu.
|
||||
6. Nastavte dobu platnosti na "No expiry".
|
||||
7. Zaškrtněte políčko "Write (optional)".
|
||||
8. Nyní klikněte na tlačítko "Generate Token".
|
||||
9. Poté se zobrazí token. Uložte jej na libovolné spolehlivé místo, nejlépe do správce hesel.
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
### So erhalten Sie das Digital Ocean API-Token
|
||||
1. Besuchen Sie den folgenden [link](https://cloud.digitalocean.com/) und melden Sie sich
|
||||
in das neu erstellte Konto an.
|
||||
2. Gehen Sie in ein zuvor erstelltes Projekt. Wenn Sie noch keine erstellt haben,
|
||||
dann bitte fortfahren.
|
||||
3. Gehen Sie zum Link "API" in der linken Leiste.
|
||||
4. Klicken Sie auf "Generate New Token".
|
||||
5. Geben Sie einen beliebigen Namen für das Token ein.
|
||||
6. Setzen Sie die Ablaufzeit auf "No expiry".
|
||||
7. Aktivieren Sie das Kontrollkästchen "Write (optional)".
|
||||
8. Klicken Sie nun auf die Schaltfläche "Generate Token".
|
||||
9. Danach wird der Token angezeigt. Bewahren Sie es an einem zuverlässigen Ort auf, vorzugsweise in einem Passwort-Manager.
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
### How to get Digital Ocean API Token
|
||||
1. Visit the following [link](https://cloud.digitalocean.com/) and sign
|
||||
into newly created account.
|
||||
2. Enter into previously created project. If you haven't created one,
|
||||
then please proceed.
|
||||
3. Go to the "API" link on the left bar.
|
||||
4. Click on the "Generate New Token".
|
||||
5. Enter any name for the token.
|
||||
6. Put expiration time to "No expiry".
|
||||
7. Check the "Write (optional)" checkbox.
|
||||
8. Now click on the "Generate Token" button.
|
||||
9. After that, the token will be shown. Store it in any reliable place, preferably a password manager.
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
### How to get Digital Ocean API Token
|
||||
1. Visit the following [link](https://cloud.digitalocean.com/) and sign
|
||||
into newly created account.
|
||||
2. Enter into previously created project. If you haven't created one,
|
||||
then please proceed.
|
||||
3. Go to the "API" link on the left bar.
|
||||
4. Click on the "Generate New Token".
|
||||
5. Enter any name for the token.
|
||||
6. Put expiration time to "No expiry".
|
||||
7. Check the "Write (optional)" checkbox.
|
||||
8. Now click on the "Generate Token" button.
|
||||
9. After that, the token will be shown. Store it in any reliable place, preferably a password manager.
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
### How to get Digital Ocean API Token
|
||||
1. Visit the following [link](https://cloud.digitalocean.com/) and sign
|
||||
into newly created account.
|
||||
2. Enter into previously created project. If you haven't created one,
|
||||
then please proceed.
|
||||
3. Go to the "API" link on the left bar.
|
||||
4. Click on the "Generate New Token".
|
||||
5. Enter any name for the token.
|
||||
6. Put expiration time to "No expiry".
|
||||
7. Check the "Write (optional)" checkbox.
|
||||
8. Now click on the "Generate Token" button.
|
||||
9. After that, the token will be shown. Store it in any reliable place, preferably a password manager.
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
### How to get Digital Ocean API Token
|
||||
1. Visit the following [link](https://cloud.digitalocean.com/) and sign
|
||||
into newly created account.
|
||||
2. Enter into previously created project. If you haven't created one,
|
||||
then please proceed.
|
||||
3. Go to the "API" link on the left bar.
|
||||
4. Click on the "Generate New Token".
|
||||
5. Enter any name for the token.
|
||||
6. Put expiration time to "No expiry".
|
||||
7. Check the "Write (optional)" checkbox.
|
||||
8. Now click on the "Generate Token" button.
|
||||
9. After that, the token will be shown. Store it in any reliable place, preferably a password manager.
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
### How to get Digital Ocean API Token
|
||||
1. Visit the following [link](https://cloud.digitalocean.com/) and sign
|
||||
into newly created account.
|
||||
2. Enter into previously created project. If you haven't created one,
|
||||
then please proceed.
|
||||
3. Go to the "API" link on the left bar.
|
||||
4. Click on the "Generate New Token".
|
||||
5. Enter any name for the token.
|
||||
6. Put expiration time to "No expiry".
|
||||
7. Check the "Write (optional)" checkbox.
|
||||
8. Now click on the "Generate Token" button.
|
||||
9. After that, the token will be shown. Store it in any reliable place, preferably a password manager.
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
### How to get Digital Ocean API Token
|
||||
1. Visit the following [link](https://cloud.digitalocean.com/) and sign
|
||||
into newly created account.
|
||||
2. Enter into previously created project. If you haven't created one,
|
||||
then please proceed.
|
||||
3. Go to the "API" link on the left bar.
|
||||
4. Click on the "Generate New Token".
|
||||
5. Enter any name for the token.
|
||||
6. Put expiration time to "No expiry".
|
||||
7. Check the "Write (optional)" checkbox.
|
||||
8. Now click on the "Generate Token" button.
|
||||
9. After that, the token will be shown. Store it in any reliable place, preferably a password manager.
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
### How to get Digital Ocean API Token
|
||||
1. Visit the following [link](https://cloud.digitalocean.com/) and sign
|
||||
into newly created account.
|
||||
2. Enter into previously created project. If you haven't created one,
|
||||
then please proceed.
|
||||
3. Go to the "API" link on the left bar.
|
||||
4. Click on the "Generate New Token".
|
||||
5. Enter any name for the token.
|
||||
6. Put expiration time to "No expiry".
|
||||
7. Check the "Write (optional)" checkbox.
|
||||
8. Now click on the "Generate Token" button.
|
||||
9. After that, the token will be shown. Store it in any reliable place, preferably a password manager.
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
### Jak uzyskać token API Digital Ocean
|
||||
1. Wejdź na stronę [link](https://cloud.digitalocean.com/) i zaloguj się
|
||||
na konto, które właśnie utworzyłeś.
|
||||
2. Zaloguj się do wcześniej utworzonego projektu. Jeśli jeszcze nie utworzyłeś projektu,
|
||||
to przejdź dalej.
|
||||
3. Kliknij na link "API" w lewym panelu.
|
||||
4. Kliknij na przycisk "Generate New Token".
|
||||
5. Wprowadź dowolną nazwę dla tokena.
|
||||
6. Ustaw datę wygaśnięcia na "No expiry".
|
||||
7. Zaznacz pole wyboru "Write (optional)".
|
||||
8. Teraz kliknij przycisk "Generate Token".
|
||||
9. Na ekranie pojawi się wówczas token. Przechowuj go w dowolnym bezpiecznym miejscu, najlepiej w menedżerze haseł.
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
### Как получить API-токен Digital Ocean
|
||||
1. Перейдите по следующей [link](https://cloud.digitalocean.com/) и войдите
|
||||
в только что созданную учетную запись.
|
||||
2. Войдите в ранее созданный проект. Если вы еще не создали проект,
|
||||
тогда приступайте.
|
||||
3. Перейдите по ссылке "API" на левой панели.
|
||||
4. Нажмите на кнопку "Generate New Token".
|
||||
5. Введите любое имя для токена.
|
||||
6. Установите срок действия на "No expiry".
|
||||
7. Установите флажок "Write (optional)".
|
||||
8. Теперь нажмите на кнопку "Generate Token".
|
||||
9. После этого на экране появится токен. Сохраните его в любом надежном месте, лучше всего в менеджере паролей.
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
### Ako získať token API Digital Ocean
|
||||
1. Navštívte nasledujúci [link](https://cloud.digitalocean.com/) a prihláste sa
|
||||
do novo vytvoreného účtu.
|
||||
2. Vstúpte do predtým vytvoreného projektu. Ak ste ho ešte nevytvorili,
|
||||
potom pokračujte ďalej.
|
||||
3. Prejdite na odkaz "API" na ľavej lište.
|
||||
4. Kliknite na tlačidlo "Generate New Token".
|
||||
5. Zadajte ľubovoľný názov tokenu.
|
||||
6. Nastavte čas vypršania platnosti na "No expiry".
|
||||
7. Začiarknite políčko "Write (optional)" zaškrtávacie políčko.
|
||||
8. Teraz kliknite na tlačidlo "Generate Token" tlačidlo.
|
||||
9. Potom sa zobrazí token. Uložte ho na akékoľvek spoľahlivé miesto, najlepšie do správcu hesiel.
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
### How to get Digital Ocean API Token
|
||||
1. Visit the following [link](https://cloud.digitalocean.com/) and sign
|
||||
into newly created account.
|
||||
2. Enter into previously created project. If you haven't created one,
|
||||
then please proceed.
|
||||
3. Go to the "API" link on the left bar.
|
||||
4. Click on the "Generate New Token".
|
||||
5. Enter any name for the token.
|
||||
6. Put expiration time to "No expiry".
|
||||
7. Check the "Write (optional)" checkbox.
|
||||
8. Now click on the "Generate Token" button.
|
||||
9. After that, the token will be shown. Store it in any reliable place, preferably a password manager.
|
||||
|
|
@ -1,11 +0,0 @@
|
|||
### Як отримати токен Digital Ocean API
|
||||
|
||||
1. Перейдіть за цим [посилання](https://cloud.digitalocean.com/) і увійдіть у щойно створений обліковий запис.
|
||||
2. Увійдіть у раніше створений проект. Якщо ви його не створили, тоді, будь ласка, продовжуйте.
|
||||
3. Перейдіть за посиланням «API» на лівій панелі.
|
||||
4. Натисніть «Створити новий токен».
|
||||
5. Введіть будь-яку назву токену.
|
||||
6. Встановіть для терміну дії значення «Без терміну дії».
|
||||
7. Встановіть прапорець «Написати (необов’язково)».
|
||||
8. Тепер натисніть кнопку «Створити токен».
|
||||
9. Після цього буде показано токен. Зберігайте його в будь-якому надійному місці, бажано в менеджері паролів.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
У наступным акне увядзіце токен, атрыманы з кансолі папярэдняй версіі прыкладання.
|
||||
|
||||
Увядзіце яго без слова *Bearer*.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
V dalším okně zadejte token získaný z konzoly předchozí verze aplikace.
|
||||
|
||||
Zadejte ji bez slova *Bearer*.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
Geben Sie im nächsten Fenster das Token ein, das Sie von der Konsole der vorherigen Version der Anwendung erhalten haben.
|
||||
|
||||
Geben Sie es ohne das Wort *Bearer* ein.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
In the next window, enter the token obtained from the console of the previous version of the application.
|
||||
|
||||
Enter it without the word *Bearer*.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
In the next window, enter the token obtained from the console of the previous version of the application.
|
||||
|
||||
Enter it without the word *Bearer*.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
In the next window, enter the token obtained from the console of the previous version of the application.
|
||||
|
||||
Enter it without the word *Bearer*.
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue