Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

293
active users

shakedown.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.4

#postgresql

1 post1 participant0 posts today
Public
DeManiak 🇿🇦

Some thoughts on my preliminary investigation of #Omeka ( omeka.org/classic/docs/Install ).

Built on pretty standard #LAMP stack.
No official docker image that I could find, so of course I built my own.
Which reminded me why I HATE php.

Anyway.

Some light testing (running locally).
Pretty simple to use (good).
No fancy ideas about creating "presentation" versions of items, and keeping the original upload "pristine". I am of two minds on this - for now, not a problem for me, but I can see how large archives might be problematic.

For example, a MOV file needs to be presented as a MP4 for widest audience. And you probably don't want to lose the original.
With Omeka that means some manual work on the admin side.

It support plugins and themes - I'm of two minds here also. Good way
to extend functionality and allow for customization, but my experience with such things are not good ito longterm stabililty and maintenance.

I'm also not super keen on #MySQL as the db, due to recent corruptions issues with my #Nextcloud instance (moved that to #PostgreSQL ).
BUT, this will be read heavy, so maybe not an issue - hard-ish to corrupt a db by reading from it.

The useage of #DublinCore at least means (I think) in theory, if I really want, I should be able to migrate to another Dublin Core compatible system if needed. So...good.

My verdict - I'm going to play with it some more.
Install some plugins etc, see what happens.
I'm also building up a test set of assets, in case I want to eval something else.

omeka.orgInstallation - Omeka Classic User Manual
#Selfhosted#DigitalArchiveManagement
Public *
Esk 🐌⚡💜

howdy, folks - it's been a bit since our last #hachyderm infra check in.

stuff in motion:

- ditching #terraform cloud & tf for #opentofu and #atlantis. we are just about to import our dev environment and put it through its paces.
- bringing #postgresql under ansible management. the team has been doing awesome work, and we've started to spin up dev nodes using the new playbooks. soon: production!
- moving #DNS zones away from AWS route 53. we chose bunny DNS as our provider and have been doing basic tests in dev. we'll likely prep our records for production this week with a plan for a cutover in one of the coming weekends.

and if you filled out our volunteer form and haven't heard from me in a bit - you're still on the list. we'll onboard a new batch of folks in the next couple of weeks.

:hachyderm: :blobfoxheartcute:

@hachyderm

#devops#sre#mastoadmin
Public *
Mark Gardner

#Microservices. Real-time #asynchronous processing. #PostgreSQL and #Redis integrations. And the best damn collection of well-tested #OpenSource libraries.

Your company is using the #Perl #programming language and ecosystem, even if you don’t know it.

So join Deriv and support @metacpan so that your systems can continue to run for the *next* 25 years: perl.com/article/why-deriv-sup

fosstodon.org/@metacpan/114162

Perl.comWhy Deriv Supports the Perl EcosystemSince 1997 Perl.com has published articles about the Perl programming language, its culture and community.
Public
Claire Giordano ✨

New episode of #TalkingPostgres #podcast 🎙️ (we're up to Ep25!)

Dawn Wages @BajoranEngineer: #Django dev, Python Software Foundation board chair, & author of upcoming book "Domain-driven Django"—joined the pod to chat about why so many Python developers Just Use Postgres

Give it a listen wherever you get your podcasts. And give it a boost 🚀!

Dawn is a gem & this conversation was FUN. #PostgreSQL #OpenSource #Python #Postgres

🎧 talkingpostgres.com/episodes/w

📺 youtu.be/leir3xJ4Klo?feature=s

Photo of Talking Postgres podcast guest Dawn Wages, where she joined to talk about Why Python developers just use Postgres
Public
Claire Giordano ✨

The LIVE recording for the #TalkingPostgres #podcast is happening on Wed 12 Mar at 10:00am PDT. Hope you can join us (or at least tell your database friends!) Boosts are always, always appreciated 🚀

This is Ep25 & the guest will be Dawn Wages @BajoranEngineer who is director of Community & Developer Relations at Anaconda—& will be talking about "Why Python developers just use Postgres"

#databases #python #django #OpenSource #PostgreSQL #Postgres

aka.ms/talkingpostgres-ep25-ca

Bio pic of Talking Postgres podcast guest Dawn Wages as well as podcast host Claire Giordano—plus the title of Ep25 which is "Why Python developers just use Postgres" and date/time of the Live Recording on Discord: Wed Mar 12th at 10:00am PDT
Public
Saustrup

One of the really long running issues we've been having with #mstdndk, has been #PostgreSQL WAL volumes constantly filling up and effectively killing the replicas one by one. I've got limited experience running this particular brand of database in a production environment, but I'm reading and tweaking and I think I may be on to something. I'm keeping a close eye on disk usage the next couple of days, but I'm cautiously optimistic. I'll keep you posted! 🙂

Continued thread
Public *
Thomas Munro

To be clear, their SysV and named POSIX semaphores do support shmem, but their unnamed POSIX semaphores (the ones that are initialised directly in memory without involving allocation up front with horrible SysV APIs or opening/mmap'ing via the file system) do not. The unnamed POSIX ones are much better: don't require messing with sysctls, don't live in a horrible system-wide namespace, don't leak, can be laid out efficiently in memory. #PostgreSQL would prefer to use them (as on other OSes).

Public
CM Harrington

Hey #Rails / #PostgreSQL folks:

I'm making an ActiveRecord .where query on an ltree column. I'm trying to do two things (2 different queries):

1: I want to get the immediate children of a given entry.

2. I want to get all the descendants of a given entry.

My descendants query seems to work, but my children query throws an error " invalid regular expression: quantifier operand invalid", so I'm clearly not doing it right:

What did I screw up?
#RubyOnRails

def children Forum.where("path ~ ?", "#{path}.*{1}") end (this is broken, and throws an error)
def descendants Forum.where("path ~ ?", "#{path}.") end (this appears to work, in that when I test it, I get what seems to be everything below the given path)
ExploreLive feeds
About