Perl-apparmor is obsolete in the apparmor community. No one is maintaining it. However, opensuse has to keep it to interact with yast, which is the main consumer of perl-apparmor. Getting rid of perl-apparmor would mean:
Creating a new interface (JSON) to interact with outside world (IOW, yast)
Modify yast-apparmor module to understand apparmors JSON context and reprogram in ruby, instead of using perl as a bridge.
This project is part of:
Hack Week 15
Activity
Comments
-
almost 8 years ago by goldwynr | Reply
Status update after Hackweek: https://github.com/goldwynr/yast-apparmor
Posted two patches to apparmor mailing list and got the response that creating a profile checking system inside yast would be very painful, just add a dumb window to update the profiles. JSON communications with tools would improve profiling using logprof.
Profiles are now sought using aa-status --json and displayed. Y2DIR=src /usr/sbin/yast profiles Note this requires the latest apparmor which has aa-status --json feature.
TODO: 1, Integrate profile display into apparmor tool to replace of "Configure" button in the Settings screen. 2. A dumb window for profile editing 3. Profile addition using aa-autodep 4. A new subtool for Logprofiling using aa-logprof --json
Similar Projects
Fix RSpec tests in order to replace the ruby-ldap rubygem in OBS by enavarro_suse
Description
"LDAP mode is not official supported by OBS!". See: config/options.yml.example#L100-L102
However, there is an RSpec file which tests LDAP mode in OBS. These tests use the ruby-ldap
rubygem, mocking the results returned by a LDAP server.
The ruby-ldap
rubygem seems no longer maintaned, and also prevents from updating to a more recent Ruby version. A good alternative is to replace it with the net-ldap
rubygem.
Before replacing the ruby-ldap
rubygem, we should modify the tests so the don't mock the responses of a LDAP server. Instead, we should modify the tests and run them against a real LDAP server.
Goals
Goals of this project:
- Modify the RSpec tests and run them against a real LDAP server
- Replace the
net-ldap
rubygem with theruby-ldap
rubygem
Achieving the above mentioned goals will:
- Permit upgrading OBS from Ruby 3.1 to Ruby 3.2
- Make a step towards officially supporting LDAP in OBS.
Resources
Recipes catalog and calculator in Rails 8 by gfilippetti
My wife needs a website to catalog and sell the products of her upcoming bakery, and I need to learn and practice modern Rails. So I'm using this Hack Week to build a modern store using the latest Ruby on Rails best practices, ideally up to the deployment.
TO DO
- Index page
- Product page
- Admin area -- Supplies calculator based on orders -- Orders notification
- Authentication
- Payment
- Deployment
Day 1
As my Rails knowledge was pretty outdated and I had 0 experience with Turbo (wich I want to use in the app), I started following a turbo-rails course. I completed 5 of 11 chapters.
Day 2
Continued the course until chapter 8 and added live updates & an empty state to the app. I should finish the course on day 3 and start my own project with the knowledge from it.
Hackweek 24
For this Hackweek I'll continue this project, focusing on a Catalog/Calculator for my wife's recipes so she can use for her Café.
Day 1