Saravanan666/pypi-org huggingface dataset:
Package: hoss-client
Python Client LibraryThe Hoss client library provides Python bindings for interacting with a Hoss server and the data stored within it.Installing the Client Library from pypiCreate a virtualenv using Python 3.6 or laterRunpip install -U hoss-clientInstalling the Client Library from sourceCreate a virtualenv using Python 3.6 or laterClone this repoRunpip3 install .to install thehoss-clientlibraryGetting StartedOnce you have access to a Hoss server, you must create a personal access token to interact with the API.
Log in and navigate to the "personal access token" page using the drop down menu in the top
right corner. Then create a new personal access token.Set theHOSS_PATenvironmental variable to this token before using the client library (e.g.export HOSS_PAT=hp_mytoken).The client library will automatically (via theAuthServiceclass) handle getting a JWT as needed and check of the JWT has expired (and get a new JWT when that happens).Then you can connect to the server and get started:import hoss
import os
server = hoss.connect('https://hoss.my-domain.com')CLI InterfaceThe Hoss client library also provides a CLI when installed. Runhoss -hin your virtualenv to see available commandsThe primary function currently provided by the CLI is an upload tool. This tool currently is optimized to upload a directory of medium to large files.
The the directory that you provide will be created in the specified dataset and all files that do not match the optional skip regex will be uploaded.
Files that already exist in the destination will not be uploaded again. Remember, you must set theHOSS_PATenv var before running the tool.hoss upload <dataset name> <absolute path to the upload dir>You can optionally write metadata key-value pairs using the -m flag (i.e -m subject_id=123). Multiple -m optional args are supported.You can optionally filter out files to upload using a regex string with the --skip arg.You can specify the endpoint (defaults to localhost) using the --endpoint arg.ExamplesThere are examples available in theclient/examplesdirectory. In particular, theclient/examples/notebooksdirectory contains useful example Jupyter notebooks.DevelopmentTestingThis library is effectively tested via the Hossintegration test suite. These tests should be run or updated
as needed before accepting PRs.DocsDocs are automatically built and published via GitHub actions to Read The Docs.To edit and view locally:Set up a virtualenv using the dependencies indocs/requirements.txt.Install thehoss-clientdependencies using something likepip install .Use Makefile to render your changescd docs
make htmlThen opendocs/build/html/index.htmlin your browser.ReleaseTo cut a new release, increment the library version inhoss/version.py. Then tagmainusing the same version.
GitHub Actions will automatically update the "stable" docs and push a release to pypi.
Package: hostbutter
TODO: permit functionality when context=default; e.g., when run from manager leader.PYTHONPATH=src python -m hostbutter swarm setup -i /path/to/inventory.ymlhostbutterCode Repohttps://codeberg.org/Fresh2dev/hostbutterMirror Repohttps://www.Fresh2.dev/code/r/hostbutterFundinghttps://www.Fresh2.dev/fundinghostbutter is <>. I created hostbutter to <>. This is valuable because <_>.hostbutter is similar to/inspired by <>, <>, <>. The distinguishing feature of hostbutter its ability to <>.To learn more,read the docsand find examples in the page ofrecipes.If this project delivers value to you, I ask that youprovide feedback, code contributions, and/orfunding.See my other projects @https://www.Fresh2.dev/projects.
Package: hostcheck
UsageA good tool for checking host, has 24+ servers from different countries to check. Using check-host.netSave as file#save ping server data (ex. www.google.com)>>>fromhostcheckimport*>>>host.ping("www.google.com")savedas:check-host.json>>>#save http server data (ex. www.google.com)>>>fromhostcheckimport*>>>host.http("www.google.com")savedas:check-host.json>>>#save tcp server data (ex. 3.125.102.39:13352)>>>fromhostcheckimport*>>>host.tcp("3.125.102.39:13352")savedas:check-host.json>>>#save dns server data (ex. 1.1.1.1)>>>fromhostcheckimport*>>>host.dns("1.1.1.1")savedas:check-host.json>>>Preview data#view ping server data (ex. www.google.com)>>>fromhostcheckimport*>>>host.ping("www.google.com",True)#view http server data (ex. www.google.com)>>>fromhostcheckimport*>>>host.http("www.google.com",True)#view tcp server data (ex. 3.125.102.39:13352)>>>fromhostcheckimport*>>>host.tcp("3.125.102.39:13352",True)howtoviewserverdatavideo:https://youtu.be/DlUiGR1HfTUall results are automatically saved to the check-host file in json format.  You can read it using the json module.Installationpip install hostcheckMaybe will be in new versionsdns checker
Package: host-checker
HostCheckerSimple CLI tool to check who is hosting a websiteInstallInstall using pip:pip install hostcheckerUsageGet who is hosting a website:$py-mhostcheckerwww.google.comwww.google.com                           Google LLC                               1.33sGet the hosting service of all your bookmarks(support only for chrome):$py-mhostcheckerwww.pcgamer.com                          Amazon.com, Inc.                         0.68swww.hackerrank.com                       Akamai Technologies, Inc.                0.83stranslate.google.it                      Google LLC                               0.65swww.opengl-tutorial.org                  Fastly                                   2.72sbitbucket.org                            Amazon.com, Inc.                         0.72smosquitto.org                            Bitfolk Ltd                              1.22swww.haskell.org                          PACKET                                   0.86sGet useful stats for the most popular hosting service:$py-mhostchecker--statsMicrosoft Corporation                    09 04.1%Akamai Technologies, Inc.                15 06.8%Google LLC                               20 09.1%Amazon.com, Inc.                         24 10.9%Cloudflare, Inc.                         24 10.9%Fastly                                   28 12.7%LicenseYou can reed ithere
Package: hostchk
hostchk is a python 3 CLI tool for checking the HTTP
status codes and server response headers of URLs.As arguments to the script a file of URLs seperated by lines is required . As well as the name of the file in which to save the output.Note by default the output is saved in the same directory as the input.
arguments. Furthermore, the protocol either https or http can be passed using the -proto option to
process the URLs and check their statuses.Installationhostchk is  available on the python repository, PyPI and can be installed using pip as follows:$ pip install hostchkHostchk requires 3rd party packages to run without which it will not run.It can be cloned from GitHub as:$ git clone https://github.com/brigxt0/hostchk.git
$ cd hostchk
$ pip3 install -r requirements.txtUsageIf you installed your hostchk via pip you can run it from any directory ashostchk [-h] -in INFILE -out OUTPFILE

[-proto PROTOCOL]



options:

  -h, --help       show this help message and exit

  -in INFILE       The input file name

  -out OUTPFILE    The output file name

  -proto PROTOCOL  The protocol to scan withIf you cloned your hostchk directly from Github you can run it as follows$ cd hostchk
$ python -m  hostchk [-h] -in INFILE -out OUTPFILE
[-proto PROTOCOL]ExamplesRun the script installed via pip from a directory containing an arbitrary file of urls named hosts.txt while saving to an output file named status.txt with protocol as https.$ hostchk -in files -out statusRun the script installed via pip from an arbitrary directory which does not contain the input filename named input.txt with protocol set to http.$ hostchk -in /path/to/input.txt -out /path/to/output. txt -proto http://Run the script cloned from Github as a module inside the hostchk directory for an input.txt in the downloads folder.$ cd hostchk
$ python -m hostchk -in ~/storage/downloads/input.txt -out ~/storage/downloads/output.txtEnd
Package: hostconf
The goal of this package is to be a replacement for GNU autoconf support
for a package which needs to “inspect” the local host system to see if
it needs some special local configurations to make it work.The idea is to replace the ‘configure’ script generated by an assortment
of autoconf tools (… along with all of the dependencies ofsed,gawk,make, … which generally must be the GNU versions) with a
pure Python implementation. Ideally, it is basically an extension of the
functionality in distutils, and relies heavily on that infrastructure.Hostconf now only relies on the necessary items indistutilswhich
would be used to build the extensions anyway (cc,c++,ld, …)Have a look at the README in the source repo.
Package: hostedpi
Python interface to theMythic Beasts Hosted PiAPI, developed by thepiwheelsteam (Ben NuttallandDave Jones).This module provides a Pythonic interface to the API, as well as a command line
interface.The authors of this library are not affiliated with Mythic Beasts, but we use
their Pi cloud to power the piwheels project.Documentation of the API itself can be found athttps://www.mythic-beasts.com/support/api/raspberry-piUsageView the information about a Pi from the command line:$hostedpishowmypiName: mypi
Provision status: live
Model: Raspberry Pi 3B
Disk size: 10GB
Power: on
IPv6 address: 2a00:1098:8:5b::1
IPv6 network: 2a00:1098:8:5b00::/56
Initialised keys: yes
SSH keys: 4
IPv4 SSH port: 5091
Location: MER
URLs:
  http://www.mypi.hostedpi.com
  https://www.mypi.hostedpi.com
SSH commands:
  ssh -p 5091 root@ssh.mypi.hostedpi.com  #IPv4
  ssh root@[2a00:1098:8:5b::1]  #IPv6Provision a new Pi and view its SSH command (using Python):>>>fromhostedpiimportPiCloud>>>api_id='8t29hvcux5g9vud8'>>>secret='QNwsvxZY8SxT3OiLt:Vmz-D1mWQuoZ'>>>cloud=PiCloud(api_id,secret,ssh_key_path='/home/ben/.ssh/id_rsa.pub')>>>pi=cloud.create_pi('mypi')>>>print(pi.ssh_command)ssh -p 5123 root@ssh.mypi.hostedpi.comSee thegetting startedpage for information on how to authenticate, and
see thecommand line interfacepage for information on using the command line
interface.DocumentationDocumentation for this module can be found athttps://hostedpi.readthedocs.io/Documentation of the API itself can be found athttps://www.mythic-beasts.com/support/api/raspberry-piContributingSource code can be found on GitHub athttps://github.com/piwheels/hostedpiCode and documentation contributions welcomeThe issue tracker can be found athttps://github.com/piwheels/hostedpi/issuesFor issues with the API itself, please contact Mythic Beasts supporthttps://www.mythic-beasts.com/support
Package: hostfinder
Host finderFind host in local subnet listening on specified portInstallationMake sure you are using python3.10+pipinstallhostfinderUsageCommand linehostfinder--port8080In Python moduleimporthostfinder# find first host listening to a porthost=hostfinder.find_host(port=8080)# find all hosts listening to a porthosts=hostfinder.find_hosts(port=8080)
Package: hosting-benchmark
hosting-benchmarkA full web-hosting benchmark suiteInstallationInstall using pip:pipinstallhosting-benchmarkUsageThe benchmark consists of two components:Aserver, which is a set of PHP scripts that run the benchmarkAclient, which is a cli (command line interface) tool used to run the
benchmark and collect/present the data.In order to run the benchmark, you need to install the server app. This is
fairly straightforward:Create a MySQL database on your web hosting, note down the credentialsRunhosting-benchmark archiveto prepare a ZIP archive with the server.
You will be asked to provide your database credentialsUpload and extract the zip package to your web hosting http root directoryRun the benchmark using:hosting-benchmark--hostname=https://example.com/--count=10--sleep=5allTo learn what the--countand--sleepflags do, please invokehosting-benchmark --help.DevelopmentPrecommit HooksThis project supportspre-commit. To use it please install it in thepip install pre-commitand then runpre-commit installand you are ready to go.blackwill be executed before commit and files will be formatted correctly.
Package: hostlists
hostlistsPython module to generate lists of hosts from various sources that is extensible
via plugins.Componentshostlists has 2 components:hostlists - This module handles hostlist expansionhostlists_plugins - This module contains plugins that allow hostlists to get lists of hosts from various backend systems.Dependenciesdnspython (BSD License) - This python module is used for the dns plugins to perform host expansion based on dns.UsageThe hostlists module provides a python module to do host expansion within python
programs.  It also provides a command line utility to allow usage from the
command line.Command Line ExamplesExpand a list of hosts from round robin dns using the dns plugin$hostlistsdns:www.google.com
pb-in-f99.1e100.net,pb-in-f[103-106].1e100.net,pb-in-f147.1e100.netMultiple hosts, ranges and plugins can be passed for a single hostlists$hostlistsdns:www.google.com,poodle[10-20,23].dog.com
pb-in-f99.1e100.net,pb-in-f[103-106].1e100.net,pb-in-f147.1e100.net,poodle[10-20].dog.com,poodle23.dog.com
Package: host-manager
host-managerManagement of /etc/hosts file to add and remove mappingsUsage:host-manager [add|del] hostname [ip]ExamplesThe following maps host kubeflow.development.com to ip 192.168.0.1:> host-manager add kubeflow.development.com 192.168.0.1The following removes the mapping of host kubeflow.development.com> host-manager del kubeflow.development.com
Package: hostmydocs-client
This library provide a python client forHostMyDocsdocumentation hosting systemExampleimporthostmydocs# 1. Create client object connect to your HostMyDocs instancehmd_client=hostmydocs.Client(hostmydocs.ServerConfig(address="my-hostmydocs-instance.com",api_login="my_login",api_password="my_password"))# 2. Upload your documentationmy_documentation=hostmydocs.Documentation(name="myDocName",version="1.2.3.4",language="myLanguage",zip_archive_path="path/to/my/doc/archive.zip")hmd_client.upload_documentation(my_documentation)# 3. List all documentations on your serverfordocinhmd_client.get_all_documentations():print(doc.name)
Package: hostnamegen
hostnamegenAboutThis little tool generates random host names that make sense. It is a complementary library fornamechanger.InstallationEasiest way is by pulling from PyPI:pip3 install hostnamegenUsageRandom host name with defaults$ hostnamegen
HOLZAPFEL-W3WS1QTen random names using Japanese locale and selected classes$ hostnamegen -lja_JP -n10 -d";" -cFirstNameDesktop,CompanyDesktop
GONG-ZE-DIAN-QI-YOU-XIAN-HUI-SHE-Y88FW4;HE-TONG-HUI-SHE-JIN-TENG-YIN-XING-1SW7YY;Liang-jie;Zhi-shu;Ying-shu;Yi;ZHONG-DAO-YIN-SHUA-ZHU-SHI-HUI-SHE-641IAN;YOU-XIAN-HUI-SHE-TIAN-BIAN-KUANG-YE-3AAQ5Q;QI-TENG-GASUZHU-SHI-HUI-SHE-1SH0DN;Yang-yiList available classes$ hostnamegen -cl
CompanyDesktop, FirstNameDesktop, WindowsDefaultList available locale$ hostnamegen -ll
ar_EG, bg_BG, bs_BA, cs_CZ, de_DE, el_GR, en_US, es_ES, et_EE, fa_IR, fi_FI, fr_FR, hi_IN, hr_HR, hu_HU, it_IT, ja_JP, ko_KR, lt_LT, lv_LV, nl_NL, pl_PL, pt_BR, ro_RO, ru_RU, sl_SI, sv_SE, tr_TR, uk_UA, zh_CNLegalLicense: BSD-3-Clause (http://opensource.org/licenses/BSD-3-Clause)ContactIn case you feel the need to get in touch:tasooshi@pm.meGPG
Package: hostname-resolver
hostname_resolverA bulk hostname resolver, designed to get info on a large number of internal hostnames against
internal TLDs.Given a list of hostnames, finds their FQDN using an inbuilt list of top level domains.
Designed for environments where user needs full names of internal servers, but has only
hostnames.In addition, provides limited formatting and reporting functionality (simple text or csv)Installationpip installUsageimporthostname_resolverresolver=hostname_resolver.HostnameResolver()resolver.run()or:python ./hostname_resolver/__init__.pyOn default runs, hostname_resolver will prompt you for hostnames (recommend copy/pasting a column)
h_r strips any duplicates and attempts to resolve hostnames as is or iterates each against its known
TLDs. As it resolves it displays what was given, how it resolved the hostname, and the found IP.
Once a full list is run, h_r then prompts you to run a new list, add to the previous list, build a
report (text file or csv), or quitFeaturesAdhoc functionality, most functionality modules are loaded only as needed to reduce startup timeversatility, hostnames to check can be passed through run, stdin, or the file can be called
directly with hostnames in as command line arguments (single items, passable arrays, or path names
to files containing hostnames)Modularity. It's all horizontal as heck
Package: hostopen
SynopsisWhen connected to a vagrant machine via ssh, this allows the user to open files and directories on the host machine without tunnelling.This functionality is restricted to only files/directories in synced folders.Requirementspython3vagrantSetupInstallationYou can installhostopenwithpippip3 install hostopenThis will give the commands:hostopenandhostopen-serverVagrantfile configurationThe virtual machine needs access to thesynced_foldersfile for this program to work. This file is located in the.vagrantdirectory in the same root as the Vagrantfile.Add a similiar line to the Vagrantfile:config.vm.synced_folder ".vagrant/machines/default/virtualbox", "/.vagrant_info"This assumes the machine is named ‘default’ and you are using ‘virtualbox’. Change where appropriate.SSHvagrant ssh -- -R 12355:localhost:12355The arbitrarily chosen default port of 12355 can be changed.Usage ExamplesYou can usehostopen--helpandhostopen-server--helpfor usage information.Clienthostopen file.py directoryWill make the server openfile.pyanddirectoryif they are inside of a synced folder.Serverhostopen-server sublFilepaths received will be opened with sublime.sublcan be substitued for a different program.LicenseCopyright (c) Jake Treacher. All rights reserved.Licensed under theMITLicense.
Package: hostout.centos
.. contents::Installing**********hostout.centos is a plugin for collective.hostout_. Hostout is a zc.buildoutrecipe.It's based on hostout.ubuntu_ plugin by Dylan Jay.First you need a working buildout_. Google buildout + your fav app framework to findout how to build it.We'll use a really simple one and add a hostout to our buildout and we extendhostout by adding the centos plugin using the "extends"option.>>> write('buildout.cfg',... """... [buildout]... parts = helloworld host...... [helloworld]... recipe = zc.recipe.egg:scripts... eggs = zc.recipe.egg... initialization = import sys...   main=lambda: sys.stdout.write('all your hosts are below to us!!!')... entry-points = helloworld=__main__:main...... [host]... recipe = collective.hostout... host = 127.0.0.1:10022... extends = hostout.centos...... """)>>> print system('bin/buildout -N')Installing helloworld.Generated script '/sample-buildout/bin/helloworld'.Installing host.Generated script '/sample-buildout/bin/hostout'.During deployment hostout will check for a working buildout on the remotehost and if not found will execute a CentOS bootstrap installingnative packages>>> print system('bin/hostout host deploy')Hostout: Running command 'predeploy' from '/.../collective/hostout/supervisor/fabfile.py'Logging into the following hosts as :127.0.0.1[127.0.0.1] sudo: /var/lib/plone/host1/bin/supervisorctl shutdown || echo 'Failed to shutdown'...Hostout: Running command 'postdeploy' from '/.../collective/hostout/supervisor/fabfile.py'...[127.0.0.1] sudo: /var/lib/plone/host1/bin/supervisord...[127.0.0.1] sudo: /var/lib/plone/host1/bin/supervisorctl status...Hostout: Running command 'postdeploy' from '.../collective.hostout/collective/hostout/fabfile.py'...Credits*******Nejc Zupan ( nejc dot zupan at niteoweb dot com ).. _buildout: http://pypi.python.org/pypi/zc.buildout.. _recipe: http://pypi.python.org/pypi/zc.buildout#recipes.. _fabric: http://fabfile.org.. _collective.hostout: http://pypi.python.org/pypi/collective.hostout.. _hostout.ubuntu: http://pypi.python.org/pypi/hostout.ubuntu.. _hostout: http://pypi.python.org/pypi/collective.hostout.. _supervisor: http://pypi.python.org/pypi/collective.recipe.supervisorRelease History***************0.1 (2010-06-21)----------------- Initial release.[zupo]
Package: hostout.cloud
hostout.cloud let's you build whole new application clusters in a matter of minutes.Building on the power of collective.hostout_, buildout_ and fabric_ just few lines of configurationand a single command is all thats needed to deploy apache, squid, mysql, zope, plone, django...Installing hostout.cloud************************Add the collective.hostout part to your development buildout. Using the extendsoption we add hostout.cloud to handle creating a host and hostout.ubuntuto bootstrap that host ready for deployment.>>> write('buildout.cfg',... """... [buildout]... parts = host1 helloworld...... [helloworld]... recipe = zc.recipe.egg:scripts... eggs = zc.recipe.egg... initialization = import sys...   main=lambda: sys.stdout.write('all your hosts are below to us!!!')... entry-points = helloworld=__main__:main...... [host1]... recipe = collective.hostout... extends = hostout.cloud hostout.ubuntu... hostsize - 256... hostos = Ubuntu 9.10... hosttype = rackspacecloud... key = myaccount... secret = myapikey... """... )>>> print system('bin/buildout -N')Installing host1.Generated script '/sample-buildout/bin/hostout'.Now with a single command everything is done for us>>> print system('bin/hostout host1 deploy')Our local environment>>> print system('bin/helloworld')all your hosts are below to us!!!is now deployed to the cloud>>> print system('bin/hostout host1 run bin/helloworld')all your hosts are below to us!!!Change your local code and just run deploy again>>> print system('bin/hostout host1 deploy')Reboot your server>>> print system('bin/hostout host1 reboot')and destroy it when you're done>>> print system('bin/hostout host1 destroy')Supported Cloud providers*************************hostout.cloud uses libcloud_. See the libcloud_ site for the supported serviers and optionsfor each.Currently rackspace cloud is the only provider tested
Package: hostout.ubuntu
ContentsInstallingCreditsRelease History1.0a2 (2010-05-28)1.0a1 (2010-02-13)Installinghostout.ubuntu is a plugin forcollective.hostout. Hostout is a zc.buildout
recipe.First you need a workingbuildout. Google buildout + your fav app framework to findout how to build it.
We’ll use a really simple one and add a hostout to our buildout and we extend
hostout by adding the ubuntu plugin using the “extends”
option.>>> write('buildout.cfg',
... """
... [buildout]
... parts = helloworld host
...
... [helloworld]
... recipe = zc.recipe.egg:scripts
... eggs = zc.recipe.egg
... initialization = import sys
...   main=lambda: sys.stdout.write('all your hosts are below to us!!!')
... entry-points = helloworld=__main__:main
...
... [host]
... recipe = collective.hostout
... host = 127.0.0.1:10022
... extends = hostout.ubuntu
...
... """)>>> print system('bin/buildout -N')
Installing helloworld.
Generated script '/sample-buildout/bin/helloworld'.
Installing host.
Generated script '/sample-buildout/bin/hostout'.During deployment hostout will check for a working buildout on the remote
host and if not found will execute an ubuntu bootstrap installing
native packages>>> print system('bin/hostout host deploy')
    Hostout: Running command 'predeploy' from '/.../collective/hostout/supervisor/fabfile.py'
    Logging into the following hosts as :
        127.0.0.1
    [127.0.0.1] sudo: /var/lib/plone/host1/bin/supervisorctl shutdown || echo 'Failed to shutdown'
    ...
    Hostout: Running command 'postdeploy' from '/.../collective/hostout/supervisor/fabfile.py'
    ...
    [127.0.0.1] sudo: /var/lib/plone/host1/bin/supervisord
    ...
    [127.0.0.1] sudo: /var/lib/plone/host1/bin/supervisorctl status
    ...
    Hostout: Running command 'postdeploy' from '.../collective.hostout/collective/hostout/fabfile.py'
    ...CreditsDylan Jay ( software at pretaweb dot com )Release History1.0a3 (2010-06-03)
- fabfile entrypoint1.0a2 (2010-05-28)Moved setaccess and setowners into collective.hostout1.0a1 (2010-02-13)Moved out of collective.hostoutupgraded it to fabric 1.0 and python 2.6