|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Take Home||362||7 years ago||5||bsd-3-clause||Elm|
|A take-home application server written in Elm and only Elm|
|Fdroidserver||283||3 months ago||agpl-3.0||Python|
|F-Droid server and build tools.|
|Sampctl||219||19 days ago||40||gpl-3.0||Go|
|The Swiss Army Knife of SA:MP - vital tools for any server owner or library maintainer.|
|Ego||189||3 years ago||July 01, 2017||mit||Go|
|Ego is a full-stack web framework written in Go, lightweight and efficient front-end component solutions, based on gin. The front-end is compiled, does not affect the back-end.|
|How To Setup Webpack 2||109||6 years ago||mit|
|🔧 ⚙ Tutorial to setup webpack 2 from scratch.|
|Lightning fast, zero configuration, web application development server|
|Bitcoin wallet that stores Bitcoin in your browser.|
|Build_tools||67||5 days ago||22||agpl-3.0||Python|
|Used to build ONLYOFFICE DocumentServer-related products|
|Conjob||10||a day ago||22||mit||Java|
|Simple web interface to run containers as jobs or serverless functions|
|Run||9||1||1||4 years ago||11||September 04, 2019||other||Go|
|:running: Runs an Aero project and restarts on code, template or style changes.|
F-Droid is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device.
The F-Droid server tools provide various scripts and tools that are used to maintain the main F-Droid application repository. You can use these same tools to create your own additional or alternative repository for publishing, or to assist in creating, testing and submitting metadata to the main repository.
For documentation, please see https://f-droid.org/docs, or you can find the source for the documentation in fdroid/fdroid-website.
There are many ways to install fdroidserver, they are documented on the website: https://f-droid.org/docs/Installing_the_Server_and_Repo_Tools
All sorts of other documentation lives there as well.
There are many components to all the tests for the components in this git repository. The most commonly used parts of well tested, while some parts still lack tests. This test suite has built over time a bit haphazardly, so it is not as clean, organized, or complete as it could be. We welcome contributions. Before rearchitecting any parts of it, be sure to contact us to discuss the changes beforehand.
The test suite for all of the
fdroid commands is in the tests/
subdir. .gitlab-ci.yml and .travis.yml run this test suite on
fdroidcommands, which can be run separately, e.g.
These tests are also run on various distributions through GitLab CI. This is
only enabled for
[email protected]/fdroidserver because it takes longer to
complete than the regular CI tests. Most of the time you won't need to worry
about them, but sometimes it might make sense to also run them for your merge
request. In that case you need to remove these lines from
and push this to a new branch of your fork.
Alternatively run them
gitlab-runner exec docker ubuntu_lts
The tests for the whole build server setup are entirely separate because they require at least 200 GB of disk space, and 8 GB of RAM. These test scripts are in the root of the project, all starting with jenkins- since they are run on https://jenkins.debian.net.
The API documentation based on the docstrings gets automatically
published here on every commit
It can be built locally via
pip install -e .[docs] cd docs sphinx-apidoc -o ./source ../fdroidserver -M -e sphinx-autogen -o generated source/*.rst make html
To additionally lint the code call
pydocstyle fdroidserver --count
When writing docstrings you should follow the numpy style guide.
Everything can be translated. See Translation and Localization for more info.