- infrastructure VS cloud-native-platform
- infrastructure VS usernetes
- infrastructure VS cheatsheets
- infrastructure VS alpine-packaging-image
- infrastructure VS gnomock
- infrastructure VS tube-cast
- infrastructure VS wine-container
- infrastructure VS internationalization
- infrastructure VS container_builder
- infrastructure VS nagios-plugins
Infrastructure Alternatives
Similar projects and alternatives to infrastructure
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
sserver
sserver is a simple headless server for hosting blog/static content and selling courses from your private github repository
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
gnomock
Test your code without writing mocks with ephemeral Docker containers 📦 Setup popular services with just a couple lines of code ⏱️ No bash, no yaml, only code 💻
-
container_builder
This project builds containers images using Ansible. The containers are defined as hosts in the Ansible inventory. They are generated using host and group variables, templates and local connection.
-
frontend
The RecipeRadar Frontend is a recipe search and meal planning application (by openculinary)
-
nagios-plugins
450+ AWS, Hadoop, Cloud, Kafka, Docker, Elasticsearch, RabbitMQ, Redis, HBase, Solr, Cassandra, ZooKeeper, HDFS, Yarn, Hive, Presto, Drill, Impala, Consul, Spark, Jenkins, Travis CI, Git, MySQL, Linux, DNS, Whois, SSL Certs, Yum Security Updates, Kubernetes, Cloudera etc...
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
infrastructure reviews and mentions
-
Ask HN: Who needs help with side projects?
I've been developing a recipe search engine and meal planner at https://www.reciperadar.com/ -- all the code is free and open source.
I think the two largest challenges it has at the moment are:
- Developer experience / infrastructure setup: the service is Kubernetes-based, composed primarily of Python+Flask microservices, and although the setup steps are documented[1], they're not yet automated.
- User interface: my lack of user interface design skills are fairly apparent, I think. Having some clear UI goals to work towards would be helpful - there's likely some overlap with product design questions here (what should be the range of functionality that the the app offers?)
Any and all feedback welcome, from discussion comments to pull requests to business model questions/critiques :)
PS: Don't forget to mention one or two of your own side projects if there's anything you're looking for help with, too.
-
Ask HN: Adversarial System Administration?
Hi folks,
I enjoy developing and maintaining the RecipeRadar[1] project's infrastructure in a truly open fashion.
Since the project itself is AGPL-licensed, that means I like to -- ideally -- push infrastructure documentation and changes before the associated administrative commands are run. That means that the code to the system itself is already published and available (in a chronological sense) to anyone using the service over the network at any given point in time.
However, it does introduce a set of strange risks: what if there changes expose security vulnerabilities that are _not yet_ introduced, but will be when the commands are run.
In a typical system administration scenario, generally the 'home team' acts carefully and is primarily only aware of their own actions - aside from monitoring for any externally-initiated or unexpected system behaviour during maintenance.
If a mistake is made, sometimes they'll backtrack and clean up, but for some kinds of system change, it's hard to know whether an exposed vulnerability was exploited, because the exposure window may have been very brief.
I have a sense that the best overall solution to this kind of problem (in this kind of open environment) would be an 'adversarial' system administration approach; perhaps involving some kind of mirroring.
Two (or more) systems would walk through the same series of administration steps, each with one (or more) red teams attempting to exploit the process -- already armed with the knowledge of the steps to be applied in advance.
Does that make sense to anybody, and/or can anyone provide thoughts or reading material about research into this kind of area?
[1] - https://www.reciperadar.com/
[2] - https://github.com/openculinary/infrastructure/
Stats
openculinary/infrastructure is an open source project licensed under GNU Affero General Public License v3.0 which is an OSI approved license.
The primary programming language of infrastructure is Shell.