Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
freedombone
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Context Sensitive Group
freedombone
Repository graph
Repository graph
You can move around the graph by using the arrow keys.
839361d04cb2d5acf81589634a852fa509c9378c
Select Git revision
Branches
7
bashrc/stretch
buster
ci-dev
jessie
master
stockholm
stretch
default
protected
7 results
Begin with the selected commit
Created with Raphaël 2.2.0
23
Jan
22
21
20
19
18
17
16
15
14
13
12
11
10
9
8
7
6
5
4
2
31
Dec
30
29
28
26
23
20
19
18
17
16
15
12
11
10
9
8
7
6
5
4
3
1
30
Nov
29
28
27
26
25
24
23
22
20
19
15
12
11
10
9
8
7
6
5
3
2
1
30
Oct
29
28
27
26
25
24
23
15
14
13
menuconfig
menuconfig
Move to postgresql directory when doing backups
Permissions on npm directory
More explanation
Merge branch 'stretch' of https://github.com/bashrc/freedombone
Run at a lower frequency to avoid occupying the database too much
Don't send pleroma posts to blocked instances
Back to i min blocking updates
Leave notifications alone, they will expire anyway
backslash
Remove notifications for blocked users
Block within users table
Block on more fields
Include to field in pleroma blocking
root directory
Run pleroma blocking script after firewall entry
pleroma blocking script
Restoring lychee from backup
Bump koel commit
Change site onion address
Mumble advice
Check for fullchain
mumble certs on install
domain name variable for mumble
Update mumble certs during upgrades
Separate out mumble. It doesn't need to depend on prosody being installed
prosody modules in two directories
Only copy prosody modules if the directory exists
Scope
Ensure letsencrypt certs are used where appropriate
Upgrade prosody certs when possible
Simplify expire script
typo
Checking of months on pleroma expiry script
Simpler pleroma expire script
Don't close twice
Add php postgres module
Also read months
Expiry of pleroma posts
Loading