Cobbler is a versatile Linux deployment server

Cobbler

Publish Python distributions to TestPyPI PyPI version PyPI - Downloads Documentation Status Gitter chat Codacy Badge codecov

Cobbler is a Linux installation server that allows for rapid setup of network installation environments. It glues together and automates many associated Linux tasks so you do not have to hop between lots of various commands and applications when rolling out new systems, and, in some cases, changing existing ones. It can help with installation, DNS, DHCP, package updates, power management, configuration management orchestration, and much more.

asciicast

Read more at https://cobbler.github.io

To view the man-pages, install the RPM and run man cobbler or run perldoc cobbler.pod from a source checkout.

To build the RPM, run make rpms. Developers, try make webtest to do a local make install that preserves your configuration.

If you want to contribute you may find more information under CONTRIBUTING.md.

The documentation can be found at Readthedocs

Comments
  • The requested URL returned error: 500 Internal Server Error

    The requested URL returned error: 500 Internal Server Error

    The requested URL returned error: 500 Internal Server Error Warning: anaconda: failed to fetch kickstart from https://192.168.60.10/cblr/svc/op/autoinstall/system/nodo1

    Hi, I have a problem with launching a RHEL8 kickstart from a master PC to a node PC, the indicated URL is not visible from the node to be able to be configured by the Cobbler system, in /var/lib/tftpboot/pxelinux.cfg/"file_MAC".

    timeout 1
    prompt 0
    default nodo1
    ontimeout nodo1
    LABEL nodo1
            MENU LABEL nodo1
            kernel /images/RHEL8-x86_64/vmlinuz
            append initrd=/images/RHEL8-x86_64/initrd.img  kssendmac inst.ks=http://192.168.60.10/cblr/svc/op/autoinstall/system/nodo1
            ipappend 2
    

    The inst.ks URL is not accessible and the installation fails at that point.

  • Debian10 automated DEBs build

    Debian10 automated DEBs build

    This will add automated Debian 10 "Buster" DEB package builds to the CI pipeline. Far from perfect due to issues in multiple places, eg. in setup.py; the cobbler.spec; etc. Look at tests/build-and-install-debs.sh and in the Travis buildlogs for where to improve.

  • Remove child reference on parent on collection.remove()

    Remove child reference on parent on collection.remove()

    This PR tries to improve the stacktrace in case we have orphaned children, as well as trying to prevent it in more cases.

    ~~Fixes #2680~~

    Edit: The fixed issue is unrelated to this PR now because it can't be reproduced anymore...

  • Add UEFI support

    Add UEFI support

    This should close #1777 This should close https://github.com/SUSE/spacewalk/issues/14679 This should close #2576

    The acceptance criteria for this is documented in the issue mentioned above. Otherwise this should be straightforward

  • Enable all tests

    Enable all tests

    This PR is aiming to fix all the currently skipped tests.

    TODO-Checklist:

    • [x] Implement the tests which are currently raising a not implemented exception
    • [x] Cut through the tests which are glued together in a specific order.
    • [ ] Implement the cli tests for the import (and implement the mocks)
    • [ ] Implement the server tests for the import (and implement the mocks)
    • [ ] Publish the new repo with the integration tests
    • [ ] Remove the integration test from this repo after the previous point was done
  • Using cobbler for On-Premise Ubuntu Server Repo

    Using cobbler for On-Premise Ubuntu Server Repo

    Version

    Cobbler 2.8.5 source: ?, ? build time: Tue Oct 15 01:59:43 2019

    Question

    I would like Using cobbler for On-Premise Ubuntu Server Repo , ie on-premise server will sync internet repo on a schedule & then it will act as a On-premise repo.

    I have Centos 7 server on which cobbler is installed. Here is the error i am getting

    #######################################

    Commands
    cobbler repo add --mirror=http://mirror.enzu.com/ubuntu/dists/bionic/ --name=bionic-all

    cobbler reposync --only="bionic-all"

    #######################################

    Error is : http://mirror.enzu.com/ubuntu/dists/bionic/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found

    ####################################### Details

    task started: 2020-10-17_202120_reposync task started (id=Reposync, time=Sat Oct 17 20:21:20 2020) hello, reposync run, reposync, run! creating: /var/www/cobbler/repo_mirror/bionic-all/config.repo creating: /var/www/cobbler/repo_mirror/bionic-all/.origin/bionic-all.repo running: /usr/bin/reposync -l -n -d --config=/var/www/cobbler/repo_mirror/bionic-all/.origin/bionic-all.repo --repoid=bionic-all --download_path=/var/www/cobbler/repo_mirror received on stdout: received on stderr: Error setting up repositories: failure: repodata/repomd.xml from bionic-all: [Errno 256] No more mirrors to try. http://mirror.enzu.com/ubuntu/dists/bionic/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found

    Exception occured: <class 'cobbler.cexceptions.CX'> Exception value: 'cobbler reposync failed' Exception Info: File "/usr/lib/python2.7/site-packages/cobbler/utils.py", line 106, in die raise CX(msg)

    Exception occured: <class 'cobbler.cexceptions.CX'> Exception value: 'cobbler reposync failed' Exception Info: File "/usr/lib/python2.7/site-packages/cobbler/action_reposync.py", line 120, in run self.sync(repo) File "/usr/lib/python2.7/site-packages/cobbler/action_reposync.py", line 164, in sync return self.yum_sync(repo) File "/usr/lib/python2.7/site-packages/cobbler/action_reposync.py", line 432, in yum_sync utils.die(self.logger,"cobbler reposync failed") File "/usr/lib/python2.7/site-packages/cobbler/utils.py", line 114, in die raise CX(msg)

    reposync failed, tries left: 0 reposync failed, retry limit reached, skipping running: chown -R root:apache /var/www/cobbler/repo_mirror/bionic-all received on stdout: received on stderr: running: chmod -R 755 /var/www/cobbler/repo_mirror/bionic-all received on stdout: received on stderr: Exception occured: <class 'cobbler.cexceptions.CX'> Exception value: 'overall reposync failed, at least one repo failed to synchronize' Exception Info: File "/usr/lib/python2.7/site-packages/cobbler/utils.py", line 106, in die raise CX(msg)

    Exception occured: <class 'cobbler.cexceptions.CX'> Exception value: 'overall reposync failed, at least one repo failed to synchronize' Exception Info: File "/usr/lib/python2.7/site-packages/cobbler/remote.py", line 82, in run rc = self._run(self) File "/usr/lib/python2.7/site-packages/cobbler/remote.py", line 243, in runner 3), name=name, nofail=nofail, logger=self.logger) File "/usr/lib/python2.7/site-packages/cobbler/api.py", line 804, in reposync return reposync.run(name) File "/usr/lib/python2.7/site-packages/cobbler/action_reposync.py", line 149, in run utils.die(self.logger,"overall reposync failed, at least one repo failed to synchronize") File "/usr/lib/python2.7/site-packages/cobbler/utils.py", line 114, in die raise CX(msg)

    !!! TASK FAILED !!!

    #######################################

    Any suggestion Please

    Thanks

  • Centos 7 and RHEL 7 PXE Installing fail

    Centos 7 and RHEL 7 PXE Installing fail

    When PXEing RHEL 7 from Cobbler 2.6.7 my host would load all the way to dracut, at which point I got the dreaded /dev/root error.

    [   84.985068] dracut Warning: Unable to process initqueue
    dracut Warning: Unable to process initqueue  
    [   84.985892] dracut Warning: /dev/root does not exist
    dracut Warning: /dev/root does not exist
    
    Dropping to debug shell.
    
    dracut:/# _  
    

    Cobbler Tested:

    Name        : cobbler
    Arch        : noarch
    Version     : 2.6.8
      and
    Name        : cobbler
    Arch        : noarch
    Version     : 2.6.7
    

    I have the problem described here and used his solution and this do the work!

    Here is describe the problem and solution: https://blog.vladionescu.com/pxe-installing-rhel-7-from-cobbler-2-6/

    Thanks to Vlad Ionescu for his job and his blog!.

  • cobbler sync extremely slow after upgrade

    cobbler sync extremely slow after upgrade

    Hello Cobbler Group,

    I've recently upgraded one of our cobbler servers from cobbler-2.0.11-2.el5 to cobbler-2.4.0-1.el5.noarch. Our cobbler syncs now take nearly 20 times longer.

    Comparing an older install: 2.0: real 0m8.438s 2.4: real 2m25.440s

    Both systems serve a similar amount of nodes: 2.0: ~1400 2.4: ~1200

    And have identical profiles. The hardware on the upgraded 2.4 system is substantially faster as well.

    I have noticed that the portion of the sync that takes longest is the tftpboot section. It now also generates in two locations:

    generating: /tftpboot/pxelinux.cfg/01-aa-bb-cc-dd-ee-ff generating: /tftpboot/grub/01-AA-BB-CC-DD-EE-FF warning: kernel option length exceeds 255 warning: kernel option length exceeds 255

    Is it possible to remove the /tftpboot/grub generation? Or is there anything that can be done to speed up this process?

    Thanks! -Chris

  • WIP: Multilevel boot menu

    WIP: Multilevel boot menu

    If you have 100+ profiles, then the linear boot menu becomes unusable.

    TODO:

    • if these changes are needed then I will update the documentation, etc.
    • need help testing on hardware

    Changes:

    • added a simple menu object with parent-child relationships # cobbler menu add/edit/remove/copy/find/list/rename/report
    • added menu attribute to profiles and images
    • added code to tftpgen to build layered menus for pxe, ipxe and grub boot loaders
    • added templates for building the beginning and end of the submenu
    • added templates for ipxe boot loader - ipxe*.template
    • ipxe boot menu for systems is available via http://$http_server/cblr/svc/op/ipxe/system/<system_name> similar to gpxe
    • the full ipxe boot menu is available via http://$http_server/cblr/svc/op/ipxe and tftp://ipxe/default.ipxe
    • in distros, profiles, systems and images, changed the boot_loader attribute to boot_loaders to specify a list of boot loaders for these items

    Changes for Windows:

    • metadata for specifying Windows boot files moved from kernel-options to autoinstall-meta and changed their names
    • added templates for windows answer file, startnet.cmd in WinPE image and post-installation script that downloads and runs win.ks
    • sync_post_wingen now prepares boot files not only for profiles, but also for systems
    • sync_post_wingen takes the bootmgr.exe, BCD and winpe.wim files from the /var/www/cobbler/distro_mirror/<distro_name>/Boot directory, patches them and places modified files in $tftpboot_location/images/<distro_name> and http://$http_server/cobbler/images/<distro_name>
    • added support for wimboot in tftpgen in case of gpxe/ipxe boot

    kernel for distro could be:

    • pxeboot.n12 (pxe/ipxe)
    • wimboot (ipxe)

    initrd for distro:

    • boot.sdi

    autoinstall-meta in the profiles/systems:

    • kernel
      • new name for patched pxeboot.n12
      • wimboot if the wimboot has a prefix http://, then all other files will have a prefix http://$http_server/cobbler/images/<distro_name> in the menu
    • bootmgr: new name for patched bootmgr.exe/setupldr.exe
    • bcd: new name for patched BCD
    • winpe: new name for patched winpe.wim
    • answerfile: answer file for windows
    • post_install_script: post-installation script
  • Packaging: Provide native packages for Debian & Ubuntu

    Packaging: Provide native packages for Debian & Ubuntu

    Is your feature request related to a problem?

    Currently we only provide packages for Debian and Ubuntu via Debbuild. This is good for test installations or users how know the OBS already and are familiar with it.

    The Behaviour you'd like

    apt install cobbler

    Alternatives you've considered

    Well the OBS is nice and all but in the end we will probably have more users when providing Distro-Native packages. Also we will have a simpler specfile.

    Additional context

    Current OBS project in my home: https://build.opensuse.org/project/show/home:SchoolGuy:cobbler

  • Debian_10: install from DEB fails

    Debian_10: install from DEB fails

    Describe the bug

    On Debian 10 "Buster", installing .DEB packages from Pharaoh_Atem:/cobbler-dev/Debian_10/all/ gives a non-working Cobbler. Cc @Conan-Kudo

    To Reproduce

    Install all requirements first:

    # apt install tftpd-hpa createrepo rsync xorriso python3-cheetah python3-dns python3-future python3-ldap3 python3-netaddr python3-simplejson python3-tornado python3-django python-django-common python3-tz python3-dnsq 
    
    1. cd /var/cache/apt/archives/
    2. wget https://download.opensuse.org/repositories/home:/Pharaoh_Atem:/cobbler-dev/Debian_10/all/cobbler_3.1.0~git.20191226.1577397150.c46abca1-15debian10.2_all.deb
    3. wget https://download.opensuse.org/repositories/home:/Pharaoh_Atem:/cobbler-dev/Debian_10/all/cobbler-web_3.1.0~git.20191226.1577397150.c46abca1-15debian10.2_all.deb
    4. dpkg -i cobbler_3.1.0~git.20191226.1577397150.c46abca1-15debian10.2_all.deb
    5. dpkg -i cobbler-web_3.1.0~git.20191226.1577397150.c46abca1-15debian10.2_all.deb

    Expected behavior

    A working Cobbler 3.1.0 setup.

    Version

    # cobbler --version
    httpd does not appear to be running and proxying cobbler, or SELinux is in the way. Original traceback:
    Traceback (most recent call last):
      File "/usr/lib/python3/dist-packages/cobbler/cli.py", line 325, in check_setup
        s.ping()
      File "/usr/lib/python3.7/xmlrpc/client.py", line 1112, in __call__
        return self.__send(self.__name, args)
      File "/usr/lib/python3.7/xmlrpc/client.py", line 1452, in __request
        verbose=self.__verbose
      File "/usr/lib/python3.7/xmlrpc/client.py", line 1154, in request
        return self.single_request(host, handler, request_body, verbose)
      File "/usr/lib/python3.7/xmlrpc/client.py", line 1187, in single_request
        dict(resp.getheaders())
    xmlrpc.client.ProtocolError: <ProtocolError for 127.0.0.1:80/cobbler_api: 404 Not Found>
    

    Should have given Cobbler 3.1.0

    Screenshots

    N.A.

    Additional context

    Multiple errors:

    During installation:

    conffile '/etc/cobbler' is not a plain file
    conffile '/var/lib/cobbler' is not a plain file
    

    In file /lib/systemd/system/cobblerd.service:

    ExecStart=/usr/local/bin/cobblerd -F
    

    However file cobblerd is installed in /usr/bin. This seems to be an issue with install_scripts in setup.py (?). Same goes for other files installed in /usr/share, where cobblerd.service points to ExecStartPost=-/usr/bin/touch /usr/local/share/cobbler/web/cobbler.wsgi.

    The postinst has openssl rand -base64 40 | sed 's/\//\\\//g' in the cobbler.spec, but somehow this becomes openssl rand -base64 40 | sed 's/\//\\//g' (lacking a backslash!) in the .DEB-file. This will give an error like this:

    # openssl rand -base64 40 | sed 's/\//\\//g'
    sed: -e expression #1, char 9: unknown option to `s'
    139963333518464:error:02012020:system library:fflush:Broken pipe:../crypto/bio/bss_file.c:316:fflush()
    139963333518464:error:20074002:BIO routines:file_ctrl:system lib:../crypto/bio/bss_file.c:318:
    

    I build Cobbler 3.1.1 locally on Debian Buster with debbuild (debbuild 19.11.0-0ubuntu18.04 and debbuild-macros 0.0.2-0ubuntu18.04). It had the same issues.

  • Combustion support

    Combustion support

    Is your feature request related to a problem?

    openSUSE has a project that is a superset of Ignition, called Combustion. We should support it.

    Provide a detailed description of the proposed feature

    TBD

    Alternatives you've considered

    None

    Additional information

    Further information:

    • Docs: https://en.opensuse.org/Portal:MicroOS/Combustion
    • Repo: https://github.com/openSUSE/combustion
  • Ignition Support

    Ignition Support

    Is your feature request related to a problem?

    Fedora CoreOS and openSUSE MicroOS support Ignition is a new way to auto-install systems.

    Provide a detailed description of the proposed feature

    Enable admins to utilize Ignition. More details to be filled in at a later point.

    Alternatives you've considered

    None.

    Additional information

    • Website & Docs: https://coreos.github.io/ignition/
    • Repo: https://github.com/coreos/ignition
    • openSUSE MicroOS: https://en.opensuse.org/Portal:MicroOS/Ignition
    • It doesn't seem possible to supply the location of the remote configuration file without modifying the base image.
      See: https://docs.fedoraproject.org/en-US/fedora-coreos/remote-ign/
  • Autoinstallation support for FreeBSD

    Autoinstallation support for FreeBSD

    Is your feature request related to a problem?

    Currently our FreeBSD support is limited to manual installations. IIf many systems are installed or the same system very often this is a time consuming task that doesn't need to be performed.

    Provide a detailed description of the proposed feature

    Unattended auto-installation support for FreeBSD.

    Alternatives you've considered

    Leaving as is: Well our strength is auto-installation, so let's use it.

    Additional information

    I found some pointers already:

    • https://forums.freebsd.org/threads/freebsd-and-automated-pxe-setup.81712/
    • https://www.freebsd.org/cgi/man.cgi?query=bsdinstall&sektion=8&manpath=freebsd-release-ports
    • https://docs.freebsd.org/en/articles/remote-install/
    • https://www.freebsd.org/cgi/man.cgi?query=bsdconfig&sektion=8
    • https://docs.freebsd.org/doc/7.4-RELEASE/usr/share/doc/de/books/handbook/using-sysinstall.html
    • https://www.youtube.com/watch?v=7F3UwfNB2JA
  • Fix small regression: allow empty string as value for

    Fix small regression: allow empty string as value for "interface_type"

    Description

    This PR fixes a small regression apparentely introduced during the refactor of NetworkInterface class, which made it to not longer accept empty string as input value for interface_type property.

    In previous versions, an empty string value was explicitely accepted and considered as na internally. Now it raises an exception:

    cobbler.cexceptions.CX: "serializer: error loading collection system: intf_type choices include: ['NetworkInterfaceType.NA', 'NetworkInterfaceType.BOND', 'NetworkInterfaceType.BOND_SLAVE', 'NetworkInterfaceType.BRIDGE', 'NetworkInterfaceType.BRIDGE_SLAVE', 'NetworkInterfaceType.BONDED_BRIDGE_SLAVE', 'NetworkInterfaceType.BMC', 'NetworkInterfaceType.INFINIBAND']. Check /etc/cobbler/modules.conf"
    

    There was no migration implemeted for interface_type value of collections, so I simply keep allowing empty string as input for NetworkInterfaceType.

    Behaviour changes

    Old: Cobbler was not able to start as there was stored collections with interface_type being empty string.

    New: Cobbler is able to process the empty string for interface_type, making it to successfully start.

    Category

    This is related to a:

    • [x] Bugfix
    • [ ] Feature
    • [ ] Packaging
    • [ ] Docs
    • [ ] Code Quality
    • [ ] Refactoring
    • [ ] Miscellaneous

    Tests

    • [x] Unit-Tests were created
    • [ ] System-Tests were created
    • [ ] Code is already covered by Unit-Tests
    • [ ] Code is already covered by System-Tests
    • [ ] No tests required
  • WIP: Use a threadpool to increase performance on writting tftpboot files on cobbler sync

    WIP: Use a threadpool to increase performance on writting tftpboot files on cobbler sync

    NOTE

    This is still WIP - I'm still doing some tests here, will update this PR soon.

    Description

    This PR introduces a thread pool to improve the performance at the time of generating PXE files during cobbler sync.

    Instead generating the files sequentially, we are spreading the generation across different threads which enhace the performance a lot.

    Behaviour changes

    On an environment with around 1500 systems and lot of profiles:

    Old: New:

    Performance increase

    Category

    This is related to a:

    • [ ] Bugfix
    • [x] Feature
    • [ ] Packaging
    • [ ] Docs
    • [ ] Code Quality
    • [ ] Refactoring
    • [ ] Miscellaneous

    Tests

    • [x] Unit-Tests were created
    • [ ] System-Tests were created
    • [ ] Code is already covered by Unit-Tests
    • [ ] Code is already covered by System-Tests
    • [ ] No tests required
  • "Breed" of Salt's RHEL repo not automatically detected, fails at sync (v3.3.3 RPMs compiled on Rocky 8)

    Describe the bug

    When adding a custom repo with cobbler repo add ..., the breed key is left blank and no error is shown. Then, when trying to do cobbler reposync it fails to download.

    Steps to reproduce

    1. Install official dependencies & compile v3.3.3 RPMs on RHEL 8, then install
    2. Add repo with the following command:
        cobbler repo add  \
        --keep-updated=Y  \
        --mirror-locally=Y  \
        --name="trad_salt_latest_rhel8"  \
        --mirror="https://repo.saltproject.io/py3/redhat/8/x86_64/latest"
    
    1. Run cobbler reposync
    2. Download fails

    Expected behavior

    The breed key should be set automatically, or the repo add should be rejected with an error message which indicates to the user that breed must be set manually as well as the allowed values.

    Cobbler version

    v3.3.3

    Operating system

    Compiled & installed on Rocky 8.7

pyinfra automates infrastructure super fast at massive scale. It can be used for ad-hoc command execution, service deployment, configuration management and more.
pyinfra automates infrastructure super fast at massive scale. It can be used for ad-hoc command execution, service deployment, configuration management and more.

pyinfra automates/provisions/manages/deploys infrastructure super fast at massive scale. It can be used for ad-hoc command execution, service deployme

Nov 27, 2022
Simple, Pythonic remote execution and deployment.

Welcome to Fabric! Fabric is a high level Python (2.7, 3.4+) library designed to execute shell commands remotely over SSH, yielding useful Python obje

Dec 5, 2022
Get Response Of Container Deployment Kube with python

get-response-of-container-deployment-kube 概要 get-response-of-container-deployment-kube は、例えばエッジコンピューティング環境のコンテナデプロイメントシステムにおいて、デプロイ元の端末がデプロイ先のコンテナデプロイ

Nov 5, 2021
CTF infrastructure deployment automation tool.

CTF infrastructure deployment automation tool. Focus on the challenges. Mirrored from

Apr 12, 2022
Glances an Eye on your system. A top/htop alternative for GNU/Linux, BSD, Mac OS and Windows operating systems.
Glances an Eye on your system. A top/htop alternative for GNU/Linux, BSD, Mac OS and Windows operating systems.

Glances - An eye on your system Summary Glances is a cross-platform monitoring tool which aims to present a large amount of monitoring information thr

Dec 5, 2022
Linux, Jenkins, AWS, SRE, Prometheus, Docker, Python, Ansible, Git, Kubernetes, Terraform, OpenStack, SQL, NoSQL, Azure, GCP, DNS, Elastic, Network, Virtualization. DevOps Interview Questions
Linux, Jenkins, AWS, SRE, Prometheus, Docker, Python, Ansible, Git, Kubernetes, Terraform, OpenStack, SQL, NoSQL, Azure, GCP, DNS, Elastic, Network, Virtualization. DevOps Interview Questions

Linux, Jenkins, AWS, SRE, Prometheus, Docker, Python, Ansible, Git, Kubernetes, Terraform, OpenStack, SQL, NoSQL, Azure, GCP, DNS, Elastic, Network, Virtualization. DevOps Interview Questions

Dec 3, 2022
SSH tunnels to remote server.

Author: Pahaz Repo: https://github.com/pahaz/sshtunnel/ Inspired by https://github.com/jmagnusson/bgtunnel, which doesn't work on Windows. See also: h

Nov 30, 2022
gunicorn 'Green Unicorn' is a WSGI HTTP Server for UNIX, fast clients and sleepy applications.

Gunicorn Gunicorn 'Green Unicorn' is a Python WSGI HTTP Server for UNIX. It's a pre-fork worker model ported from Ruby's Unicorn project. The Gunicorn

Dec 5, 2022
A lobby boy will create a VPS server when you need one, and destroy it after using it.

Lobbyboy What is a lobby boy? A lobby boy is completely invisible, yet always in sight. A lobby boy remembers what people hate. A lobby boy anticipate

Oct 16, 2022
Some automation scripts to setup a deployable development database server (with docker).

Postgres-Docker Database Initializer This is a simple automation script that will create a Docker Postgres database with a custom username, password,

Nov 11, 2021
Simple ssh overlay for easy, remote server management written in Python GTK with paramiko
Simple ssh overlay for easy, remote server management written in Python GTK with paramiko

Simple "ssh" overlay for easy, remote server management written in Python GTK with paramiko

May 1, 2022
📦 Powerful Package manager which updates plugins & server software for minecraft servers
📦 Powerful Package manager which updates plugins & server software for minecraft servers

pluGET A powerful package manager which updates Plugins and Server Software for minecraft servers. Screenshots check all to check installed plugins fo

Nov 22, 2022
This Docker container is build to run on a server an provide an easy to use interface for every student to vote for their councilors
This Docker container is build to run on a server an provide an easy to use interface for every student to vote for their councilors

This Docker container is build to run on a server and provide an easy to use interface for every student to vote for their councilors.

Nov 23, 2022
The deployment framework aims to provide a simple, lightweight, fast integrated, pipelined deployment framework that ensures reliability, high concurrency and scalability of services.

savior是一个能够进行快速集成算法模块并支持高性能部署的轻量开发框架。能够帮助将团队进行快速想法验证(PoC),避免重复的去github上找模型然后复现模型;能够帮助团队将功能进行流程拆解,很方便的提高分布式执行效率;能够有效减少代码冗余,减少不必要负担。

Sep 16, 2022
A light-weight, versatile XYZ tile server, built with Flask and Rasterio :earth_africa:
A light-weight, versatile XYZ tile server, built with Flask and Rasterio :earth_africa:

Terracotta is a pure Python tile server that runs as a WSGI app on a dedicated webserver or as a serverless app on AWS Lambda. It is built on a modern

Nov 27, 2022
Awesome multilingual OCR toolkits based on PaddlePaddle (practical ultra lightweight OCR system, provide data annotation and synthesis tools, support training and deployment among server, mobile, embedded and IoT devices)
Awesome multilingual OCR toolkits based on PaddlePaddle (practical ultra lightweight OCR system, provide data annotation and synthesis tools, support training and deployment among server, mobile, embedded and IoT devices)

English | 简体中文 Introduction PaddleOCR aims to create multilingual, awesome, leading, and practical OCR tools that help users train better models and a

Nov 27, 2022
A simple python package that perform SQL Server Source Control and Auto Deployment.

deploydb Deploy your database objects automatically when the git branch is updated. Production-ready! ⚙️ Easy-to-use ?? Customizable ?? Installation I

Aug 9, 2022
Automation for grabbing keys from a Linux host. Useful during red team exercises to quickly help assess what access to a Linux host can lead to.

keygrabber Automation for grabbing keys from a Linux host. This can be helpful during red team exercises when you gain access to a Linux host and want

Sep 27, 2022
LSO, also known as Linux Swap Operator, is a software with both GUI and terminal versions that you can manage the Swap area for Linux operating systems.
LSO, also known as Linux Swap Operator, is a software with both GUI and terminal versions that you can manage the Swap area for Linux operating systems.

LSO - Linux Swap Operator Türkçe - LSO Nedir? LSO, diğer adıyla Linux Swap Operator Linux işletim sistemleri için Swap alanını yönetebileceğiniz hem G

Feb 9, 2022
List of Linux Tools I put on almost every linux / Debian host

Linux-Tools List of Linux Tools I put on almost every Linux / Debian host Installed: geany --> GUI editor/ notepad++ like chkservice --> TUI Linux ser

Nov 5, 2022