the creation of base .env file that stores global variables for the app
need to be automated, so it's created after composer install
automatically instead of issueing and additional command
A UI has been added for entering new sources and editing pre-existing
ones. No more having to edit the DB directly when wanting to add or
remove a source.
At some point the composer json got jacked, so that needed to be fixed
to update laravel to the latest.
also started putting in pieces for sources management through the UI
after the site is installed and the DB set up, there needed to be a way
to create the first account that will be used as the admin to access the
den, the admin section of tbs
the system makes a check to see if this account exists and if there
isn't one present, it shows the admin account set up screen on the
index. it goes away after the account is created.
Migrations were pretty much useless for database set up, so that needed
some attention to make setting up the project easier. Now, all necessary
tables can be created by running the `artisan migrate` command assuming
one has the database parameters set in the .env file
also added full text search capabilites through the database set up,
which the model itself can use to find locations, so the search has been
updated in the appropriate locations as well.
still need to add initial account set up and a form for adding sources
through the UI, but this was a big step towards letting anyone set up
their own version of tbs
a quick update to the composer file to have proper versioning and some
details about the project,
also updated the template to reflect the current version
locations needed another data point for notes to additional information
about instances that aren't covered by public comments, i.e. if the site
is still live, additional concerns, etc, so that's been added and the
appropriate template files added
also, public comments where not being included in the CSV exports, so that's
been patched as well
there was a reference to storing descriptions in the database that no
longer has a corresponding table since it was changed
just commenting it out for now because it will be implemented again at a
later date
the update process now compiles public comments from instance blocklists
and displays them, so the name of the table that stores these comments
has been changed so it's not confusing.
also made the appropriate changes on the backend and in the template
that shows that information
admin functions are not shown to member with incorrect roles, but added
a bit more padding in the controller itself to check if the role is
correct before running an admin action for a little extra security
now that editing member work, that process needed to be fleshed out by
adding an admin method to add new members as well. now new members can
be added by an admin
also changed the name of a blade file that wasn't following the template
naming convention
needed way to edit existing members info if needed, so simple ui was
created for admins of the site to change specific info, not including a
members avi or password.
also consolidated memeber action and ui into it's own controller for the
sake of clearer organization
the previous update cycle only showed the latest comment from Sources
concerning a specific instance
now all available comments are pulled from denylist data to be displayed
under Description on the front end
changed the the way files are uploaded to go into their own directory
called 'references' organized by location, identified by uuid. the
'references' directory was added to git ignore to those images are not
saved in the repo, since every install will have their own set of images
also updated reference links to be shown on the front end if they have
been added to a location
unnecessary links where moved from the admin member template since they
have been incorporated into the appropriate area.
a template for editing member account information has also been added.
The process for updating blocklists per source wasn't effecient, so it
has been rewritten to process each source individually before moving on,
relieving some processing load on the server and ensuring every source
comes back with data, even in the event it doesn't grab it the first
time.
also removed the recent list from the index page as the recently updated
list doesn't reflect what's been the last to get updated and changed the
theme color to match the current palette.
codebase was a version behind the latest laravel version, so all those
dependencies have been update to bring it up to speed
also added a small tweak to fix a firefox specific bug with rendering
CSS files
the csv exports for mastodon had some formatting issues that was making
importing problematic, so those issues have been fixed so importing the
doc is easier
The admin area needed to be reorganized as it was a bit all over the
place to accomodate new features.
And edit link was added to location detail pages so authorized members
can edit when necessary.
Form elements were loosened up a bit to give them a bit more breathing
room
The plumbing for editing location info has been updated, so that data
can be changed by authorized memebers. Also added a new data point for
locations to store archive links
part 2 will focus on setting up permissions and authorizations as well
as smoothing out adding new members and member roles. an edit link will
be added to locations, which will be visible for members with the
correct permissions
finally found the correct exception that captures a connect error when a
source url cannot be loaded, so it logs the error and just keep
executing the script.
Now automation can be enabled since the system knows how to handle
errors. Fuck. Yes.
The script for collection blocklist info was getting a little heavy, so
it's been split in two to make it more accessible and easier to
maintain. The first part collects data from current sources and stores
it for the second part of the script, which compiles all the data and
updated the database.
The Source model was expanded to track votes so block and silence counts
can be easily verified on the backend.
changed the function that retrieves a single location to decide what to
get based on the variable type, so it doesn't need to be two seperate
functions
The Location Controller was getting too heavy so an Update and
Maintenance service class was created to offload most of it's
functionality. Location upating was moved to LocationRepository
There was also a small issue with responsive list links not adapting
properly in Safari that was fixed
addded some preliminary url validation to make sure a source url is
still active.
the consolidation process is starting to get top heavy, so it's a stop
gap until a more effecient process can be created.
Adding total actions count to location data has made it possible to
simplify backend data queries, so the custom pagination was optimized
and location repositories have been cleaned up.
the front end controller has been cleaned up as well, which has resulted
in the appropriate template being polished up as well.
Added a new field to the locations table for total actions which will be
used to set the active state of location. this will result in data being
parsed and sorted easier instead of doing those calculations on the back
end, so DB queries will be simpler
also fixed actions counts for csv imports
Seperated data logic for locations and put it into its own repository
class for better organization and readability of controller classes.
Data methods are still simple so no need for an interface class just
yet, but will probably implement at a later date
Changed the appeal process so that each request is tracked in the
database to make reviewing and time limits easier to manage.
An email is still sent but it's just a notifcation to let the admin know
an appeal has been filed.
Hit the major friction points in the responsive UI. Still have some
polishing to do but there shouldn't be any show stoppers at this points.
Also moved some variable to the env so they can be changed easily when
necessary
Responsive styles are non-existent so it was time to get that sorted.
This first pass was just getting a feel for what can be done with
list items since that's one of the main components of the site.
Second pass will clean this up as well as the majority of text styling
so it all smoothly adapts.
Ha, or that's the plan anyway.
