You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not too long between updates this time, but I’ve got a few neat pieces of news to share.
33
33
First and foremost, you may recall that I said we’d gotten a domain name (opensourcecorp.org) in a previous post. For some time now, it’s really just had some redirect rules to point folks to the GitHub Org, and to the GitHub Pages site for blog posts.
34
-
But now, it’s a real-ass website! You might even be reading this post on it right now!
34
+
But now, it’s a real-ass website! You might even be reading this post on it right now!<ahref="https://www.opensourcecorp.org/blog/posts/2022-06-05-progress-report/">(more)</a>
Not a ton of changes in this update, I’ve had a lot of things come up these past few months that have prioritized my attention (a few conference talks to prepare for, dog & personal health issues, house repairs, work-work, etc). But some impactful updates nonetheless!
43
-
All OSC infrastructure repos have now been consolidated into a single monorepo, osc-infra. This implies that you should expect old links to the individual infra repos to be broken.
43
+
All OSC infrastructure repos have now been consolidated into a single monorepo, osc-infra. This implies that you should expect old links to the individual infra repos to be broken.<ahref="https://www.opensourcecorp.org/blog/posts/2022-05-15-progress-report/">(more)</a>
More radio silence as ever more work has been done across OSC. As you’ll see from the list below though, this is a really big set of changes/new stuff!
51
-
The conflation of infrastructure repos with application repos has grown to be a potential source of confusion for readers. As such, OSC should shortly be moving from a mono-org source, to orgs separated by identifier (opensourcecorp-infra, opensourcecorp-apps, etc). This should make it more clear what type of repo you’re looking at when you’re browsing a certain org.
51
+
The conflation of infrastructure repos with application repos has grown to be a potential source of confusion for readers. As such, OSC should shortly be moving from a mono-org source, to orgs separated by identifier (opensourcecorp-infra, opensourcecorp-apps, etc). This should make it more clear what type of repo you’re looking at when you’re browsing a certain org.<ahref="https://www.opensourcecorp.org/blog/posts/2022-02-27-progress-report/">(more)</a>
Over the holiday season, I’ve had about a week of dedicated time to do a lot of net-new work for OSC, as well as to go back and do some much-needed cleanup & consolidation across several of the core codebases.
60
-
First & foremost, we’ve now got a working OCI image registry! gnar needs one for custom images, so it turned into a priority pretty quick. The registry is called photobook, which is our implementation of the Harbor registry software.
60
+
First & foremost, we’ve now got a working OCI image registry! gnar needs one for custom images, so it turned into a priority pretty quick. The registry is called photobook, which is our implementation of the Harbor registry software.<ahref="https://www.opensourcecorp.org/blog/posts/2022-01-02-progress-report/">(more)</a>
61
61
<br/><br/>
62
62
</li>
63
63
64
64
<li>
65
65
<h4><ahref="https://www.opensourcecorp.org/blog/posts/2021-12-11-local-bootstrapper-available/">OSC local bootstrapper available</a></h4>
66
66
<p><em>Ryan J. Price, 2021-12-11</em></p>
67
67
OpenSourceCorp (OSC) development continues to chug along. Below are some of the updates we’ve been hard at work on, when time presents itself.
68
-
One of the net-new things we’ve worked on recently is the introduction of a (working) service-discovery implementation via HashiCorp Consul (named “faro”, which means “lighthouse” in a few Latin-root languages). Updates to aether allow for each platform/app to easily register themselves with the Consul cluster, and be discoverable via clean domain names and not IP addresses anymore, with two foundational exceptions that still need known IPs at their first launch (faro itself, and aether).
68
+
One of the net-new things we’ve worked on recently is the introduction of a (working) service-discovery implementation via HashiCorp Consul (named “faro”, which means “lighthouse” in a few Latin-root languages). Updates to aether allow for each platform/app to easily register themselves with the Consul cluster, and be discoverable via clean domain names and not IP addresses anymore, with two foundational exceptions that still need known IPs at their first launch (faro itself, and aether).<ahref="https://www.opensourcecorp.org/blog/posts/2021-12-11-local-bootstrapper-available/">(more)</a>
69
69
<br/><br/>
70
70
</li>
71
71
72
72
<li>
73
73
<h4><ahref="https://www.opensourcecorp.org/blog/posts/2021-10-04-deployment-update/">OSC updates: hosting decision & live services!</a></h4>
74
74
<p><em>Ryan J. Price, 2021-10-04</em></p>
75
75
OpenSourceCorp (OSC) development has slowed down in recent months as Ryan (founder & maintainer) has gotten caught up in work-work. However, with renewed motivation (looming conference talk at SaltConf21, presenting on OSC!), we’re back at it again!
76
-
One of the chief goals of OSC has been to have its services live on an as-unmanaged-as-possible platform, in the service of helping to teach the community all about the core functionality of computing, storage, networking, and security.
76
+
One of the chief goals of OSC has been to have its services live on an as-unmanaged-as-possible platform, in the service of helping to teach the community all about the core functionality of computing, storage, networking, and security.<ahref="https://www.opensourcecorp.org/blog/posts/2021-10-04-deployment-update/">(more)</a>
OpenSourceCorp’s home repo has a new architecture diagram up! This diagram provides a high-level layout of the architecural flows for the current & future core OpenSourceCorp platforms. It’s pretty rough at the time of this posting, but I’m not exactly a designer :)
84
-
If you peruse the various repos across OSC, you’ll notice that most are still empty placeholders, not-yet-functional, or still need some serious work – but many have continued to receive updates to their codebases (still just me over here!
84
+
If you peruse the various repos across OSC, you’ll notice that most are still empty placeholders, not-yet-functional, or still need some serious work – but many have continued to receive updates to their codebases (still just me over here!<ahref="https://www.opensourcecorp.org/blog/posts/2021-07-25-new-arch-diagram/">(more)</a>
Today, I’m very excited to finally announce the public launch of OpenSourceCorp – the free and open-source enterprise. This is something I’ve been working towards for a few months now, and while it’s been public the entire time, it’s finally in a spot worth sharing with the rest of the world.
92
-
My contributions to the open-source community all started with an ndJSON logging framework for R that I wrote at work, to solve a very specific set of challenges I was having.
92
+
My contributions to the open-source community all started with an ndJSON logging framework for R that I wrote at work, to solve a very specific set of challenges I was having.<ahref="https://www.opensourcecorp.org/blog/posts/2021-07-05-announcing-opensourcecorp/">(more)</a>
0 commit comments