Updated strongswan config files and using a for loop for a more readable code
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Thu, Mar 5
I do not think this is an industry-standard solution. There's gap that's visually visible... Do more research.
Add route transition animations
Wed, Mar 4
In D3989#62108, @Chenani-MohamedAmine wrote:Added theme configuration in admin Settings tab (mode selector + toggleable checkbox) as requested.
Added theme configuration in admin Settings tab (mode selector + toggleable checkbox) as requested.
Final cleanup: satisfy dereckson feedback and fix file corruption
Final fix: remove ntpdate state from init.sls
Fix FreeBSD configuration based on dereckson feedback
Apply feedback: use YES (quotes) and add ntpd_sync_on_start
More detailed README.md
Changed the source path in carp.sls into : source: salt://roles/router/carp/files/carp.rc
This is out of scope and uses the wrong approach. Please rollback all changes and start over. I've renamed the differential for better clarity.
In D3992#61982, @dereckson wrote:Per https://cbea.ms/git-commit/ titles of your commit messages should be much shorter.
You can consider a global title then use current info as summary:
[New shorter title] Add fade transition on route changes. Fix scrollbar layout shift on IncidentHistory loading state.
In D3989#61878, @ieli wrote:The implementation uses a boolean dark class on the <html> element. For better flexibility, consider using a data-theme attribute instead of a boolean class. This allows each theme to define its own dark/light variants. Additionally, the toggle button should be hidden for mono themes (themes with only one palette). The useDarkMode composable should expose whether the theme is "toggleable", and the navbar should conditionally render the button based on this. Finally, theme configuration should be available in the admin side - the Settings tab in AdminDashboard.vue would be the appropriate place to add theme selection.
To deploy to all IntraNought VMs.
The flag hello_ipv6_ovh was missing in web-001, because in netbox the ipv6 was in /56 not in /64.
Virtually OK, but one critical flag missing from pillarize for ongoing IPv6 connectivity
For context, when we apply Salt configuration, it currently checks if ipv6-setup-tunnel is running.
@Duranzed As a follow-up for the Terminator plugin, that one could be interesting too.
Plugin works, but now we need to polish the two README files.
Configuration logic. Looks good to me.
Service part OK.
Per https://cbea.ms/git-commit/ titles of your commit messages should be much shorter.
Fixed the remaining issues (tailwind config, useDarkMode with data-theme, stray Z in test)
Tue, Mar 3
Add some changes : some flags where missing
Add canonical_public_ipv4 for Ysul
No link to a task in description?
OK for Wolfplex too.
In D3989#61933, @Chenani-MohamedAmine wrote:"Ref T2246"
Change the files motd for db-a-001 and db-b-001
- Added "View all" link in StatusPage when resolved incidents > 5
- Changed created_at to start_date in test mock data
- Moved IncidentHistory.test.js to views/__tests__/
- Added error logging in getById catch handler
- Added an init.sls pour strongswan
rename db-B-001 to db-b-001 across the repository
This change touches Wolfplex files. As such, administrative approval is needed from Wolfplex technical contact.
Standardize NTP configuration (T1223) - v2
Remove accidental file t