stp-ip

We went the direction of DNS based redirects using a set of TXT records to get portability and delegation of subpaths with txtdirect.org (FOSS based on Caddy) Currently working on a new iteration and feedback is always appreciated.

Various active channels (Slack, Telegram, Meetups etc.) and participants, but more details in the article ;)

Second the notion of a post mortem, but I assume due to their focus on security they value security by obscurity as an additional factor.

Their downtime and non usable site was so bad already that downtime is almost as inconvenient as the working site was before. Now at least they are fixing it. They held back the update for months due to testing. They have to take the jump and after x hours of downtime the damage is done, so fixing it once and for all instead of rolling back might actually be the better solution.

You have to differentiate between the social media person and the actual engineers.

They first outgrew git, then outgrew perforce and implemented a custom server on top of their usual storage/database stack.

For current user volumes. Due to them filing for IPO it seems right to assume that they want to multiply their user count quite a bit.

There are some companies using k8s not just for the ability to move, but as a hybrid starting ground. One bandwith intense workload is running with GKE for all state/databases, but uses a bare-metal k8s cluster for compute and bandwidth intensive stuff. They actually use federation and the bare-metal cluster basically looks for a local database doesn't find one and gets routed to the next available global cluster, which is GKE.

Due to the cache and read dependend nature of the database queries the latency impact is worth it.

Gitlab reversed their decision to go with bare-metal. They still plan to ditch Azure and the most likely candidate (already testing to move their CI infra) for the move is GCP/GCE and GKE from Google.

Sidenote: We are running coredns.io in production as authoritative internal DNS and as hidden master with NOTIFY to a secondary DNS provider (currently DNSmadeEasy).

The DNS records for the internal records are done using the kubernetes middleware (basically serving the service records). The external records are pulled in from a git repository hosting our zones as bind files. If need be zones are split into subzones per team/project. Same permission system as our code via MRs using Gitlab.

Our recommendation is build on open standards (BIND, AXFR) and use services on top of these.

I agree that using an external mail provider is usually a good idea. It mostly is your fallback communication channel and is usually easy to switch (doing replication to an offsite mail storage needs to be done to make switching easy/possible/fast). MX records \o/

Keep your friends close but your enemies closer.

Joking aside. Most likely to get a foot in the door on competition and on git related features written in Go, which might supplement or replace parts of the infrastructure within Gitlab. They already use Go for the CI runner part and as a smart, Gitlab aware proxy.

No plugin for only caching headers, but you can do that easily using the headers plugin or headers_downstream within the proxy plugin.

As an example:

      header / Cache-Control "no-cache, max-age=86400"

      header /images/ Cache-Control "max-age=86400"

      header /css/ Cache-Control "max-age=604800"

      header /fonts/ Cache-Control "max-age=604800"

      header /icons/ Cache-Control "max-age=604800"

If you want to add the header only to static assets that can be done, but is a bit harder.

Control can be taken and views/visions can be different. That's the great thing about open source. The community or even other participants can fork and continue their own vision. Projects shouldn't make a habit out of it so.

They were 90% of the top contributors. The company had a lot more sales people. The devs don't control decisions of the company. Only the code and that's why I assume there was this fork.

There doesn't seem to be VC money involved with nextcloud. Spreed.com/me is funding the transition and stock will focus on being owned by employees it seems.

9 of the top 10 contributors in addition to the project founder and the lead security engineer are pushing this effort. Good foundation to fork and support users.

Let's hope this brings the transparency, openness and community awareness owncloud/nextcloud always needed.

Seems like 9 of the top 10 contributors in addition to the project founder and the lead security engineer are pushing this effort. Good foundation to fork and support users.

Let's hope this brings the transparency, openness and community awareness owncloud/nextcloud always needed.

Not to mention the awesome team at GitLab and the Core Team from the community. Awesome progress and quite transparent and with an amazingly open approach. Buffer with a product one wants to work on.

As far as the information goes. Musk is selling his stock to buy his stock options and cover the resulting taxes. The documents stated, that even after he sold part of his stake for 0.6B he would have more shares than before.

Any plans to make the browser cache aware of cross domain resources? Basically a hash based cache, where as long as the hash is valid it can be used from a hash based caching pool. This could be integrated with SRI to reduce unnecessary network load without compromising user privacy. Will not provide complete privacy, but might reduce exposure to 3rd party CDNs.

If something like this is implemented, providing frequently used resources via a plugin, privacy aware CDN or even a custom CDN similar to https://addons.mozilla.org/en-US/firefox/addon/decentraleyes... would be possible.

Can't wait to check it out.

Compared to the last version of online document editing in ownCLoud... this might actually be usable.

An up to date demo is available at https://demo.owncloud.org.

And even if they didn't notice it right away. It takes a lot of effort to race an unconfirmed transaction and let the coins get respend (double the actual withdraw in your address). Especially when mtgox let's you verify your account with your official documentation. Additionally with the fees generated just today they would cover 500 Bitcoins in losses just from one day revenue.

And even if you do not yet violate their TOS, they do change them to their liking and kick you out anyway. Relying on Amazon as a partner is not really something I can recommend.

Amazon actively shutsdown projects, which automaticly replace affiliate links. Most still running projects are just too small to be noticed yet.

They closed down all charity and affiliate related projects and replaced them with smile to make it cheaper. aflattr.com + socialvest.com

Thanks

In my opinion it still lacks more automatic deploy mechanisms. Ansible has some great ideas, but I guess the time to write your deploy scripts is needed. I'm still hoping for a salt package like system. (https://github.com/saltstack-formulas) Where you only use your top.sls and perhaps some custom pillar data, to define how packages interact or where packages are needed. Define wordpress running on 2 appservers + 1 database node + 1 loadbalancer with ssl termination and export db and pipe it through gpg via this pillar key. etc. pp

njpatel I would love to get my hands on your python code on the reactor stuff. Still haven't found a real world example for updating loadbalancers or dns.