Complete container management platform

Rancher

Build Status Docker Pulls Go Report Card

Rancher is an open source project that provides a container management platform built for organizations that deploy containers in production. Rancher makes it easy to run Kubernetes everywhere, meet IT requirements, and empower DevOps teams.

Looking for Rancher 1.6.x info? Click here

Latest Release

  • Latest - v2.5.7 - rancher/rancher:latest - Read the full release notes.

  • Stable - v2.5.7 - rancher/rancher:stable - Read the full release notes.

To get automated notifications of our latest release, you can watch the announcements category in our forums, or subscribe to the RSS feed https://forums.rancher.com/c/announcements.rss.

Quick Start

sudo docker run -d --restart=unless-stopped -p 80:80 -p 443:443 --privileged rancher/rancher

Open your browser to https://localhost

Installation

Rancher can be deployed in either a single node or multi-node setup. Please refer to the following for guides on how to get Rancher up and running.

No internet access? Refer to our Air Gap Installation for instructions on how to use your own private registry to install Rancher.

Minimum Requirements

  • Operating Systems
    • Ubuntu 16.04 (64-bit)
    • Red Hat Enterprise Linux 7.5 (64-bit)
    • RancherOS 1.4 (64-bit)
  • Hardware
    • 4 GB of Memory
  • Software
    • Docker v1.12.6, 1.13.1, 17.03.2

Using Rancher

To learn more about using Rancher, please refer to our Rancher Documentation.

Source Code

This repo is a meta-repo used for packaging and contains the majority of rancher codebase. Rancher does include other Rancher projects including:

Rancher also includes other open source libraries and projects, see go.mod for the full list.

Support, Discussion, and Community

If you need any help with Rancher or RancherOS, please join us at either our Rancher forums, #rancher IRC channel or Slack where most of our team hangs out at.

Please submit any Rancher bugs, issues, and feature requests to rancher/rancher.

Please submit any RancherOS bugs, issues, and feature requests to rancher/os.

For security issues, please email [email protected] instead of posting a public issue in GitHub. You may (but are not required to) use the GPG key located on Keybase.

License

Copyright (c) 2014-2020 Rancher Labs, Inc.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Owner
Rancher
Rancher
https://github.com/rancher/rancher http://rancher.com
Comments
  • [BUG]

    [BUG]

    Rancher Server Setup

    • Rancher version: v2.7-head
    • Installation option (Docker install/Helm Chart): Docker standalone
      • If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):
    • Proxy/Cert Details:

    Information about the Cluster None setup yet

    User Information

    • What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)
      • If custom, define the set of permissions: Admin

    Describe the bug

    When running the container, it restarts constantly and says k3s exited with code 0

    To Reproduce

    Create a container using the instructions at the Rancher v2.7 docs under Persistent Data.

    Result

    Expected Result

    The container starts and I can go to the administration webpage to set up a cluster.

    Additional context

    I am running an Ubuntu 22.04 VM with 8GB allocated ram and 12 allocated cores under PVE 7.3-4.

    Container Logs

    2023/01/01 00:48:26 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:48:28 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:48:30 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:48:32 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:48:34 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:48:36 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:48:38 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:48:40 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:48:42 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:48:44 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:48:46 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:48:48 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:48:50 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:48:52 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:48:54 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:48:56 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:48:58 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:49:00 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:49:02 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:49:04 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:49:13 [INFO] Running in single server mode, will not peer connections
2023/01/01 00:49:18 [INFO] Applying CRD features.management.cattle.io
2023/01/01 00:50:08 [ERROR] unable to update feature harvester in initialize features: Put "https://127.0.0.1:6444/apis/management.cattle.io/v3/features/harvester": unexpected EOF
2023/01/01 00:50:08 [FATAL] k3s exited with: exit status 1
INFO: Running k3s server --cluster-init --cluster-reset
2023/01/01 00:51:05 [INFO] Rancher version v2.7.0 (ce9a7aea4) is starting
2023/01/01 00:51:05 [INFO] Rancher arguments {ACMEDomains:[] AddLocal:true Embedded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:false Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit.log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Features: ClusterRegistry:}
2023/01/01 00:51:05 [INFO] Listening on /tmp/log.sock
2023/01/01 00:51:05 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:51:07 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:51:09 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:51:11 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:51:13 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:51:15 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:51:17 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:51:19 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:51:21 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:51:23 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:51:25 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:51:27 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:51:29 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:51:31 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:51:38 [INFO] Running in single server mode, will not peer connections
2023/01/01 00:51:38 [INFO] Applying CRD features.management.cattle.io
2023/01/01 00:51:40 [INFO] Applying CRD navlinks.ui.cattle.io
2023/01/01 00:51:50 [INFO] Applying CRD clusters.management.cattle.io
2023/01/01 00:51:51 [INFO] Applying CRD apiservices.management.cattle.io
2023/01/01 00:51:52 [INFO] Applying CRD clusterregistrationtokens.management.cattle.io
2023/01/01 00:51:54 [INFO] Applying CRD settings.management.cattle.io
2023/01/01 00:51:54 [INFO] Applying CRD preferences.management.cattle.io
2023/01/01 00:51:54 [INFO] Applying CRD features.management.cattle.io
2023/01/01 00:51:59 [INFO] Applying CRD clusterrepos.catalog.cattle.io
2023/01/01 00:52:00 [INFO] Applying CRD operations.catalog.cattle.io
2023/01/01 00:52:00 [INFO] Applying CRD apps.catalog.cattle.io
2023/01/01 00:52:00 [INFO] Applying CRD fleetworkspaces.management.cattle.io
2023/01/01 00:52:00 [INFO] Applying CRD managedcharts.management.cattle.io
2023/01/01 00:52:00 [INFO] Applying CRD clusters.provisioning.cattle.io
2023/01/01 00:52:01 [INFO] Applying CRD clusters.provisioning.cattle.io
2023/01/01 00:52:01 [INFO] Applying CRD rkeclusters.rke.cattle.io
2023/01/01 00:52:01 [INFO] Applying CRD rkecontrolplanes.rke.cattle.io
2023/01/01 00:52:01 [INFO] Applying CRD rkebootstraps.rke.cattle.io
2023/01/01 00:52:01 [INFO] Applying CRD rkebootstraptemplates.rke.cattle.io
2023/01/01 00:52:01 [INFO] Applying CRD rkecontrolplanes.rke.cattle.io
2023/01/01 00:52:01 [INFO] Applying CRD custommachines.rke.cattle.io
2023/01/01 00:52:01 [INFO] Applying CRD etcdsnapshots.rke.cattle.io
2023/01/01 00:52:01 [INFO] Applying CRD clusters.cluster.x-k8s.io
2023/01/01 00:52:01 [INFO] Applying CRD machinedeployments.cluster.x-k8s.io
2023/01/01 00:52:01 [INFO] Applying CRD machinehealthchecks.cluster.x-k8s.io
2023/01/01 00:52:01 [INFO] Applying CRD machines.cluster.x-k8s.io
2023/01/01 00:52:01 [INFO] Applying CRD machinesets.cluster.x-k8s.io
2023/01/01 00:52:40 [FATAL] k3s exited with: exit status 1
INFO: Running k3s server --cluster-init --cluster-reset
2023/01/01 00:56:46 [INFO] Rancher version v2.7.0 (ce9a7aea4) is starting
2023/01/01 00:56:46 [INFO] Rancher arguments {ACMEDomains:[] AddLocal:true Embedded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:false Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit.log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Features: ClusterRegistry:}
2023/01/01 00:56:46 [INFO] Listening on /tmp/log.sock
2023/01/01 00:56:48 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:56:50 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:56:52 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:56:54 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:56:56 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:56:58 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:57:02 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:57:04 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:57:06 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:57:08 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:57:10 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:57:12 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:57:14 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:57:16 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:57:18 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:57:20 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:57:22 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:57:24 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:57:26 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:57:28 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:57:30 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:57:32 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:57:34 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
2023/01/01 00:57:36 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.1:6444: connect: connection refused
  • How to modify the default configuration of nginx-proxy in rabcher？

    How to modify the default configuration of nginx-proxy in rabcher？

    In the K8S cluster managed by the rancher, nginx-proxy is used on the worker node for highly available components to access the apiserver。However, the number of processes enabled by nginx-proxy on the worker node is the number of machine cores by default, and the number of my machine cores is 128. This way, too many processes are enabled. However, nginx-proxy is automatically managed by the rancher. How to change the default configuration of nginx proxy's worker processes？

    | Useful | Info | | :-- | :-- | |Versions|Rancher v2.5.12 UI: v2.5.12 |

  • [BUG] Agent cant connect IPv6 only cluster

    [BUG] Agent cant connect IPv6 only cluster

    Rancher Server Setup

    • Rancher version: v2.7.0
    • Installation option (Docker install/Helm Chart): Helm chart
      • If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE2
    • Proxy/Cert Details: Nginx / Cert Manager (Lets Encrypt)

    Information about the Cluster

    • Kubernetes version: v1.24.9+rke2r1 (IPv6 only)
    • Cluster Type (Local/Downstream): Downstream
      • If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): Imported

    User Information

    • What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom) Admin

    Describe the bug The agent keeps failing to connect with "RTNETLINK answers: Network is unreachable" and is stuck on "Connecting to proxy". When I add the CATTLE_FEATURES env to the rancher agent deployment on the downstream cluster it unstuck the connecting to proxy, and set the cluster to active but I'm unable to manage it though rancher getting "lost connection to cluster: failed to find Session for client stv-cluster-c-m-gwftl7hm"

    Also for information the current setup is a clean install, and the previous setup using IPv4 had no issue. To Reproduce Setup two rke2 cluster with IPv6 only node Install rancher on the first one Join the second cluster using kubectl apply

    Result

    Screenshots image

    I also found an error on fleet image

    Hope to get help Thanks in advance

  • INSTALLATION FAILED: chart requires kubeVersion: < 1.25.0-0 which is incompatible with Kubernetes v1.26.0

    INSTALLATION FAILED: chart requires kubeVersion: < 1.25.0-0 which is incompatible with Kubernetes v1.26.0

    Good day! Try to install Rancher Added the Helm Chart Repository rancher-latest I get an error Error: INSTALLATION FAILED: chart requires kubeVersion: < 1.25.0-0 which is incompatible with Kubernetes v1.26.0 Can you please tell me if there is a date when support will be implemented or is there a way to install to ignore versioning?

  • Add useragent to handlers

    Add useragent to handlers

    Some handlers have been configured to use clients with useragents that are named to reference the handlers that use them.

    Issue:

    https://github.com/rancher/rancher/issues/38775

    Problem

    We would like to use the new useragent functionality in a small way that only mainly only affects team1 before rolling it out to more parts of rancher.

    Solution

    Add useragent to some select handlers.

    Testing

    Engineering Testing

    Manual Testing

    Automated Testing

    QA Testing Considerations

    Regressions Considerations

Related tags
Miscellaneous docker kubernetes containers rancher orchestration cattle
Generate random, pronounceable, sometimes even memorable, "superhero like" codenames - just like Docker does with container names.

Codename an RFC1178 implementation to generate pronounceable, sometimes even memorable, "superheroe like" codenames, consisting of a random combinatio

Dec 11, 2022
Monitoring Go application inside docker container by InfluxDB, Telegraf, Grafana
 Monitoring Go application inside docker container by InfluxDB, Telegraf, Grafana

REST API for TreatField app Docker compose for TIG and Golang simple app: https://github.com/tochytskyi/treatfield-api/blob/main/docker-compose.yml Gr

Nov 6, 2021
Generic-list-go - Go container/list but with generics

generic-list-go Go container/list but with generics. The code is based on contai

Dec 7, 2022
literature management for bio programmers
 literature management for bio programmers

literature management for bio programmers

Oct 24, 2022
An unified key management system to make life easier.
 An unified key management system to make life easier.

Safebox An unified key management system to make life easier. The main goal of safebox is to make key backup easier with single main key to derive the

Nov 15, 2022
Transaction management tool for taxable investments

Market Lot Robot Transaction management tool for taxable investments. How it works Run the web socket server with the following command: go run . Visi

Oct 19, 2021
Small proof of concept project to try temporal.io with Dispatch Incident Management from Netflix.
 Small proof of concept project to try temporal.io with Dispatch Incident Management from Netflix.

temporal-dispatch-poc Small POC project to try out the Temporal workflow engine together with Netflix's Dispatch Incident Management System. Supported

Nov 12, 2021
🕕Todo management through emails
 🕕Todo management through emails

??Todo management through emails

Nov 15, 2021
Product Lifecycle Management (PLM) in Git

Product Lifecycle Management (PLM) in Git. This repo contains a set of best practices and an application that is used to manage information needed to

Dec 21, 2022
Golang-module-references - A reference for how to setup a Golang project with modules - Task Management + Math Examples

Golang Module Project The purpose of this project is to act as a reference for setting up future Golang projects using modules. This project has a mat

Jan 2, 2022
Go-turing-i2c-cmdline - Controlling the i2c management bus of the turing pi with i2c works fine

go-turing-i2c-cmdline What is it? Controlling the i2c management bus of the turi

Jan 24, 2022
This Go based project of Aadhyarupam Innovators demonstrate the code examples for building microservices, integration with cloud services (Google Cloud Firestore), application configuration management (Viper) etc.

This Go based project of Aadhyarupam Innovators demonstrate the code examples for building microservices, integration with cloud services (Google Cloud Firestore), application configuration management (Viper) etc.

Dec 22, 2022
go.mod file is the root of dependency management in Go

go.mod file is the root of dependency management in Go. All the modules which are needed or to be used in the project are maintained in go.mod file. I

Feb 9, 2022
Supply chain management indie game... IN SPACE!
 Supply chain management indie game... IN SPACE!

Ship shape Supply chain management indie game ... IN SPACE! Current state is preliminary - there's a six-level tutorial, about an hour's worth of game

Nov 3, 2022
cross-platform, normalized battery information library

battery Cross-platform, normalized battery information library. Gives access to a system independent, typed battery state, capacity, charge and voltag

Dec 22, 2022
Cross-platform file system notifications for Go.

File system notifications for Go fsnotify utilizes golang.org/x/sys rather than syscall from the standard library. Ensure you have the latest version

Dec 30, 2022
An example client implementation written in GO to access the CyberVox platform API

About This is an example client implementation written in GO to access the CyberVox platform API.

Nov 7, 2022
golang script for bypass AV and work only in windows platform
 golang script for bypass AV and work only in windows platform

antivirus bypass protection requirements golang installed usage 1 - create your payload go run create.go <ip> <port> <secret> <any url>

Nov 9, 2022
Neko is a cross-platform open-source animated cursor-chasing cat. This is the reimplementation write in Go.

Neko Neko is a cat that chases the mouse cursor across the screen, an app written in the late 1980s and ported for many platforms. This code is a re-i

Nov 21, 2022