Compare commits
4 Commits
renovate/m
...
google-dri
Author | SHA1 | Date | |
---|---|---|---|
daea06eae8 | |||
34328a1dea | |||
1060130197
|
|||
6d389047cb
|
@ -1,4 +1,4 @@
|
||||
FROM ruby:3.0.2-alpine3.12
|
||||
FROM ruby:2.7.3-alpine
|
||||
|
||||
EXPOSE 4000
|
||||
|
||||
|
@ -24,7 +24,7 @@ services:
|
||||
labels:
|
||||
- "traefik.enable=true"
|
||||
- "traefik.http.services.jekyll.loadbalancer.server.port=4000"
|
||||
- "traefik.http.routers.jekyll.rule=Host(`autonomic.zone`) || Host(`www.autonomic.zone`)"
|
||||
- "traefik.http.routers.jekyll.rule=Host(`autonomic.zone`)"
|
||||
- "traefik.http.routers.jekyll.entrypoints=web-secure"
|
||||
- "traefik.http.routers.jekyll.tls.certresolver=production"
|
||||
- "traefik.http.routers.jekyll.tls.options=default@file"
|
||||
|
@ -1 +1 @@
|
||||
docker-compose==1.29.2
|
||||
docker-compose==1.29.1
|
||||
|
25
src/_posts/2021-02-11-google-drive.md
Normal file
@ -0,0 +1,25 @@
|
||||
---
|
||||
layout: post
|
||||
title: Escaping the Google silo
|
||||
description: Opening up your Google Drive and Docs files using open source software
|
||||
image:
|
||||
category: technology
|
||||
date: 2021-02-11
|
||||
---
|
||||
|
||||
At Autonomic we always promote using [libre software](https://en.wikipedia.org/wiki/Free_software) whereever possible but we understand that many clients have committed to using [propietary software](https://en.wikipedia.org/wiki/Proprietary_software) either due to legacy decision or because the non-libre solutions are simply more effective and mature.
|
||||
|
||||
The Google Workspace set of tools including Google Drive and Google Docs is one such solution. Once your organisation has deployed and is using these Google services, it's extremly difficult to migrate away. Google Docs files are not easy to extract from their propietary format and users are strongly encouragaged to only interact with the documents via the Google Workspace web apps.
|
||||
|
||||
This is problematic for organisations that want to approach their data storage with a stratergy that suits them, rather than the Google™️ mandated workflow.
|
||||
There are also [so many criticims](https://en.wikipedia.org/wiki/Criticism_of_Google) that could be made of Google in so many areas (as a [worker's co-operative of privacy advocates](/our-founding-principles), we're of course very biased).
|
||||
|
||||
There is also the question of [Google outages](https://en.wikipedia.org/wiki/2020_Google_services_outages) which happened multiple times in 2020. Of course, service outages can and do happen at any scale but it is interesting to note that they are even fairly regular occurance at many of the largest technology companies. When it comes to critical services, offering reduncancy and decentralisation is very difficult to do at the monolithic scale of the tech ginats.
|
||||
|
||||
We have been working on a solution for a client to try and make it easier for organisatons to in the short term keep non-Google hosted copies of their data and in the long term, be in a better position to migrate away from Google Workspace all together. Luckily, there is an extensive [Drive](https://developers.google.com/drive/) and [Docs API](https://developers.google.com/docs/api/) which is well documentated and relativley stable.
|
||||
|
||||
Our system is designed to pull all of your data out of the Google [walled garden](https://en.wikipedia.org/wiki/Closed_platform) and directly into your control. We host a server for you which runs our code to extract all of your files from Google Drive and covert all of your Google Docs into open document formats (.odt .docx etc.). The files are then made available to your organisation as standard filesystem on your own [Nextcloud](https://nextcloud.com/) instance and then you can do what you want with them. You'll also be able to draw up a support contract with us that suits your needs for both maintaining the server and supporting your users.
|
||||
|
||||
We intend to release the source code for our system under a libre license as soon whens we feel it's ready but it still needs some cleaning up and documentation which takes time. When it's released, you'll be able to find on our [Gitea instance](https://git.autonomic.zone/autonomic-cooperative).
|
||||
|
||||
If you're interested in hosting this solution for your organsation, feel free to [get in touch](mailto:helo@autonomic.zone).
|
@ -1,10 +0,0 @@
|
||||
---
|
||||
layout: post
|
||||
title: New Co-op Cloud blog, socials and updates
|
||||
description: Co-op Cloud project blog, socials and monthly updates
|
||||
image: ccblog.png
|
||||
category: coop, co-op, cloud, docker, swarm, libre-software, hosting,
|
||||
date: 2021-07-07
|
||||
---
|
||||
|
||||
The Co-op Cloud is starting to come into its own and we've decided to move our posts over to a dedicated [new and shiny blog](https://coopcloud.tech/blog/). We are working on opening up shared ownership of the project and want to create digital spaces where Autonomic is not implicitly having some sort of gate keeping role. We'll be writing regularly about our progress over there. We've also made new [Twitter](https://twitter.com/Coop_Cloud) and [Mastodon](https://social.coop/@coopcloud) which can you can follow along. That's all for now!
|
@ -1,63 +0,0 @@
|
||||
---
|
||||
layout: post
|
||||
title: Come join the good ship Autonomic!
|
||||
description: Hi do you want to work with the coolest anarchist tech workers co-operative?
|
||||
image: robertmccall.jpg
|
||||
category: decision making, democracy, meta
|
||||
date: 2021-11-25
|
||||
---
|
||||
|
||||
|
||||
## Background
|
||||
|
||||
Autonomic is a worker-owned co-operative of queer comrade hackers dedicated to using technology to empower people making a positive difference in the world. Since 2017, we’ve been successfully delivering projects in a range of sectors including renewable energy, labour organising, independent media, feminist research, migrant solidarity activism, sustainable fashion, and arms trade abolition.
|
||||
|
||||
We are currently 12 worker-owners, located on four continents worldwide. We are a Co-operative Society, registered in the UK with the Financial Conduct Authority. Legally, we are a freelance consortium, which means that we operate as a group of self-employed contractors, and are responsible for our own individual income tax.
|
||||
|
||||
Autonomic aspires to follow the [7 co-operative principles as defined by the International Co-operative Alliance](https://www.ica.coop/en/cooperatives/cooperative-identity).
|
||||
|
||||
We're currently looking to build capacity in the co-op in key areas to help take us to the next level.
|
||||
|
||||
## Pay
|
||||
|
||||
We are currently paid £16 per hour for all work.
|
||||
|
||||
Everyone in the co-op will always be paid the same rate, which we decide on collectively and adjust according to how well we're doing.
|
||||
|
||||
## What we're looking for:
|
||||
|
||||
We are looking for folks who have expertise in the following areas:
|
||||
|
||||
### Required
|
||||
- Care, communicatiton and compassion. Trust. Comradeship. Each according to their need.
|
||||
- Available for around 10-20 hours per week **between 8am UTC and 3pm UTC**
|
||||
|
||||
### Skill areas
|
||||
|
||||
We are in need of people who have experience or interest in at least 2 of these areas:
|
||||
|
||||
- Project management: progress tracking and planning, budgeting and estimates.
|
||||
- Client communications / relations / meeting, conflict resolution.
|
||||
- Infrastrucure skills: Debian, Ansible, Git, Docker, Docker Swarm in the context of [Co-op Cloud](https://coopcloud.tech).
|
||||
- Wordpress development (front end and back end): PHP, CSS, Composer, Docker.
|
||||
- Finance administration: invoicing, tax, forecasting,
|
||||
|
||||
### Bonus/Nice to Have
|
||||
|
||||
- Wordpress plug-in development
|
||||
- Drupal development
|
||||
- New business development
|
||||
|
||||
## Process
|
||||
|
||||
People of color, women, genderqueer, non-binary and trans folks, neurodiverse and queer folks strongly encouraged to apply.
|
||||
|
||||
Email helo@autonomic.zone with your CV (doesn't have to be fancy, just a list of work) and a little bit about yourself and what you're looking for work wise.
|
||||
|
||||
If we think you might be suitable for these roles, you'll be invited for a few chats with members of the co-op who will show you more about the kinds of work we do and be able to answer any questions you have.
|
||||
|
||||
If we want to take you on, we'll then have a vote amongst our members and you can start working for us right away as a "potential member". After 100 hours of work you can be invited to join the co-op as a full member.
|
||||
|
||||
<hr>
|
||||
|
||||
_image by Robert McCall_
|
@ -1,14 +0,0 @@
|
||||
---
|
||||
layout: post
|
||||
title: The Co-op Cloud Federation Proposal
|
||||
description:
|
||||
image: ccforest.jpg
|
||||
category: coop cloud, decision making, democracy
|
||||
date: 2022-04-14
|
||||
---
|
||||
|
||||
Following on in [the tradition](https://autonomic.zone/blog/new-coop-cloud-blog-and-socials/) of making [short blog posts](https://autonomic.zone/blog/co-op-cloud/) about [Co-op Cloud](https://coopcloud.tech) on this blog, here comes another one!
|
||||
|
||||
We're delighted to announce that we have finally published the Co-op Cloud federation proposal. It's a document which aims to formalise the organisation of the project, focusing on a democratic process. It's open for comments, feedback, critique & amendments.
|
||||
|
||||
Autonomic has had a central role in the organising of this project until now, but we'd like to step back and open up space for others. The proposal is part of formalising that and we're excited to see who will step in! You can find out more on the [Co-op Cloud blog](https://coopcloud.tech/blog/federation-proposal/) or jump straight to [the proposal](https://pad.autonomic.zone/s/MLafJE2jC).
|
@ -1,36 +0,0 @@
|
||||
---
|
||||
layout: post
|
||||
title: Publishing our Ansible roles
|
||||
description:
|
||||
image: infra.jpg
|
||||
category: ansible, automation, infrastructure
|
||||
date: 2022-05-30
|
||||
---
|
||||
|
||||
We're delighted to announce that we're publishing our Ansible roles
|
||||
into the open under [`git.autonomic.zone/autonomic-cooperative/...`](https://git.autonomic.zone/explore/repos?q=ansible&topic=1) at long last 🥳
|
||||
|
||||
They've always been licensed as libre software but due to the way we managed
|
||||
our internal infrastructure configurations, they were embedded in a private
|
||||
repository.
|
||||
|
||||
The roles are currently lacking documentation and written for very specific
|
||||
Autonomic needs but they might be handy as a learning resource or a base to
|
||||
fork from. We'd happily accept contributions to generalise them.
|
||||
|
||||
In particular, we've been relying on and running
|
||||
[`autonomic.new-hetzner`](https://git.autonomic.zone/autonomic-cooperative/autonomic.new-hetzner)
|
||||
for years, so it is battle tested. The role bootstraps a Hetzner VPS from
|
||||
scratch and provisions it with a hardened SSH configuration, firewalls, user
|
||||
accounts and some basic packages and a shiny MOTD.
|
||||
|
||||
All roles are CI tested on every commit with [Molecule](https://molecule.readthedocs.io/en/latest/) so things don't break.
|
||||
|
||||
[Expanding re-use with shared infrastructure](https://community.coops.tech/t/cotech-gathering-ansible-and-shared-infrastructure-session/1107)
|
||||
is someting we've always been working on at Autonomic. We have an ongoing
|
||||
critique of Ansible and the pros/cons of when it is a good choice to use. This
|
||||
ultimately lead us to start projects like [Co-op
|
||||
Cloud](https://coopcloud.tech/). However, we still think Ansible is pretty good
|
||||
at handling more complicated server provisioning needs.
|
||||
|
||||
Happy Infra Hacking.
|
@ -1,45 +0,0 @@
|
||||
---
|
||||
layout: post
|
||||
title: Wireless Battle of the Mesh - Building Community Networks for Fun and Non-Profit
|
||||
description: Autonomic members are aiming to attend. Here is our public endorsement!
|
||||
image: bmesh.png
|
||||
category: community, wireless, event
|
||||
date: 2022-07-11
|
||||
---
|
||||
|
||||
Autonomic Co-op supports this year's "Wireless Battle of the Mesh - Building
|
||||
Community Networks for Fun and Non-Profit".
|
||||
|
||||
The event aims to bring together people from across the globe who are
|
||||
interested in community networks, including wireless mesh network technologies,
|
||||
fiber infrastructure, Do-It-Yourself Internet Access Providers, and more
|
||||
generally how to create and maintain a thriving community of people involved in
|
||||
building their own networks.
|
||||
|
||||
We envision 4 days of expert presentations, practical workshops, hacking
|
||||
sessions, and fruitful discussions: whether you are a mesh networking
|
||||
enthusiast, community networking activist, protocol developer, or have an
|
||||
interest in networking in general, come and join the event!
|
||||
|
||||
The Battlemesh is free of charge and open for all.
|
||||
|
||||
This year, the event will take place from Monday 19th to Wednesday 22nd
|
||||
of September, 2022 in Rome, Italy! It will be followed by the RomHack
|
||||
Camp on September 23-25, also in Rome.
|
||||
|
||||
Check out more information [here](https://www.battlemesh.org/BattleMeshV14).
|
||||
|
||||
We are writing this post as part of a public endorsement and support for
|
||||
"Wireless Battle of the Mesh - Building Community Networks for Fun and
|
||||
Non-Profit" not only for the efforts made by its community to advance the field
|
||||
of wireless mesh networking and foster the development of grass-roots community
|
||||
networks, but for their contribution to digital freedom rights movement,
|
||||
empowerment of peoples tech/net/media competency and a free and open civil
|
||||
society.
|
||||
|
||||
We aim to support the event by:
|
||||
|
||||
- helping to promote it
|
||||
- making it possible for our members to join the event
|
||||
|
||||
See you there hopefully!
|
Before Width: | Height: | Size: 60 KiB |
Before Width: | Height: | Size: 262 KiB |
Before Width: | Height: | Size: 189 KiB |
Before Width: | Height: | Size: 48 KiB After Width: | Height: | Size: 55 KiB |
Before Width: | Height: | Size: 120 KiB |
Before Width: | Height: | Size: 92 KiB |
Before Width: | Height: | Size: 496 KiB |