#freedomboxdev — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #freedomboxdev, aggregated by home.social.
-
I've been working on:
Implementing an option to enable or disable daily run of diagnostics in FreedomBox.https://salsa.debian.org/freedombox-team/freedombox/-/merge_requests/2439
-
I've been working on:
Implementing an option to enable or disable daily run of diagnostics in FreedomBox.https://salsa.debian.org/freedombox-team/freedombox/-/merge_requests/2439
-
I've been working on:
Implementing an option to enable or disable daily run of diagnostics in FreedomBox.https://salsa.debian.org/freedombox-team/freedombox/-/merge_requests/2439
-
I've been working on:
Implementing an option to enable or disable daily run of diagnostics in FreedomBox.https://salsa.debian.org/freedombox-team/freedombox/-/merge_requests/2439
-
I've been working on:
Implementing an option to enable or disable daily run of diagnostics in FreedomBox.https://salsa.debian.org/freedombox-team/freedombox/-/merge_requests/2439
-
I started adding new diagnostic checks to #FreedomBox, focusing on essentials like firewall, users, and apache configurations. Next I will add a daily test for the most important diagnostic checks, and a notification for the administrator if anything fails.
-
I started adding new diagnostic checks to #FreedomBox, focusing on essentials like firewall, users, and apache configurations. Next I will add a daily test for the most important diagnostic checks, and a notification for the administrator if anything fails.
-
I started adding new diagnostic checks to #FreedomBox, focusing on essentials like firewall, users, and apache configurations. Next I will add a daily test for the most important diagnostic checks, and a notification for the administrator if anything fails.
-
I started adding new diagnostic checks to #FreedomBox, focusing on essentials like firewall, users, and apache configurations. Next I will add a daily test for the most important diagnostic checks, and a notification for the administrator if anything fails.
-
I started adding new diagnostic checks to #FreedomBox, focusing on essentials like firewall, users, and apache configurations. Next I will add a daily test for the most important diagnostic checks, and a notification for the administrator if anything fails.
-
Recently I have been focusing on anti-censorship tools for FreedomBox. I have a merge request to add Shadowsocks Server, which is mainly useful for getting around the GFW. Next focus will be having separate/isolated Tor instances for different use cases.
-
Recently I have been focusing on anti-censorship tools for FreedomBox. I have a merge request to add Shadowsocks Server, which is mainly useful for getting around the GFW. Next focus will be having separate/isolated Tor instances for different use cases.
-
Recently I have been focusing on anti-censorship tools for FreedomBox. I have a merge request to add Shadowsocks Server, which is mainly useful for getting around the GFW. Next focus will be having separate/isolated Tor instances for different use cases.
-
Recently I have been focusing on anti-censorship tools for FreedomBox. I have a merge request to add Shadowsocks Server, which is mainly useful for getting around the GFW. Next focus will be having separate/isolated Tor instances for different use cases.
-
A branch named "debian/bookworm" has been created in the FreedomBox git repository:
https://salsa.debian.org/freedombox-team/freedombox/-/tree/debian/bookwormAny bugfixes, translations, or documentation updates that are intended for the next Debian release will be added to this branch (after being merged as usual). This branch will be used to build packages containing these small updates, to be uploaded to Debian unstable (and eventually migrate to testing).
-
A branch named "debian/bookworm" has been created in the FreedomBox git repository:
https://salsa.debian.org/freedombox-team/freedombox/-/tree/debian/bookwormAny bugfixes, translations, or documentation updates that are intended for the next Debian release will be added to this branch (after being merged as usual). This branch will be used to build packages containing these small updates, to be uploaded to Debian unstable (and eventually migrate to testing).
-
A branch named "debian/bookworm" has been created in the FreedomBox git repository:
https://salsa.debian.org/freedombox-team/freedombox/-/tree/debian/bookwormAny bugfixes, translations, or documentation updates that are intended for the next Debian release will be added to this branch (after being merged as usual). This branch will be used to build packages containing these small updates, to be uploaded to Debian unstable (and eventually migrate to testing).
-
A branch named "debian/bookworm" has been created in the FreedomBox git repository:
https://salsa.debian.org/freedombox-team/freedombox/-/tree/debian/bookwormAny bugfixes, translations, or documentation updates that are intended for the next Debian release will be added to this branch (after being merged as usual). This branch will be used to build packages containing these small updates, to be uploaded to Debian unstable (and eventually migrate to testing).
-
(1/2)
In FreedomBox 22.26, the "restrict console logins" feature was removed, and replaced by firewall rules to prevent users from accessing local services. This is to prevent a local user from bypassing authentication of services which are proxied by the web server. -
(1/2)
In FreedomBox 22.26, the "restrict console logins" feature was removed, and replaced by firewall rules to prevent users from accessing local services. This is to prevent a local user from bypassing authentication of services which are proxied by the web server. -
(1/2)
In FreedomBox 22.26, the "restrict console logins" feature was removed, and replaced by firewall rules to prevent users from accessing local services. This is to prevent a local user from bypassing authentication of services which are proxied by the web server. -
(1/2)
In FreedomBox 22.26, the "restrict console logins" feature was removed, and replaced by firewall rules to prevent users from accessing local services. This is to prevent a local user from bypassing authentication of services which are proxied by the web server. -
Notes on FreedomBox App Components (1/4):
A FreedomBox app can have one or more components. There are two main categories of components: leader and follower. The leader components must all be enabled in order for the app to be considered enabled. On the other hand, the follower components will follow the state of the leader components, but if they fail for some reason, it does not affect the overall state of the app.
-
Notes on FreedomBox App Components (1/4):
A FreedomBox app can have one or more components. There are two main categories of components: leader and follower. The leader components must all be enabled in order for the app to be considered enabled. On the other hand, the follower components will follow the state of the leader components, but if they fail for some reason, it does not affect the overall state of the app.
-
My priorities for #FreedomBox development:
1. Improve the functional tests so we can catch more bugs.
2. Resume work on systemd sandboxing for security.
3. Package and integrate new apps.
#freedomboxdev #fossdev -
My priorities for #FreedomBox development:
1. Improve the functional tests so we can catch more bugs.
2. Resume work on systemd sandboxing for security.
3. Package and integrate new apps.
#freedomboxdev #fossdev -
Our Matrix channel for FreedomBox developers had a state corruption recently and is no longer usable.
We created a new Matrix channel at #freedomboxdev:synapse.sds-ip.de
Please migrate to this one.
The IRC channel #freedombox-dev on OFTC network is still intact.
-
Our Matrix channel for FreedomBox developers had a state corruption recently and is no longer usable.
We created a new Matrix channel at #freedomboxdev:synapse.sds-ip.de
Please migrate to this one.
The IRC channel #freedombox-dev on OFTC network is still intact.
-
Making another attempt at separating enabled/disabled apps. #freedomboxdev