abeorch

u/abeorch@friendica.ginestes.es
36 posts · 310 comments

Recent posts

Recent comments

@Mountainaire I've used it a few times for me and family members. I got pneumonia, collapsed lung and spent a few weeks in hospital including intensive care. Walked away with Insurance covering everything including my private ensuite room and some pretty good hospital food to boot.

Had my dad in an ambulance for an overnight stay in hospital after passing out and falling in the shower.

@breadsmasher I wouldnt mind if they were required to include easily filtered keywords such a #ad or #closedsource or #selfpromotion or something like that.

I occasionally come across people who think they have an amazing product and when you engage they realise that its better to just opensource it.

Similarly having the opportunity to discuss their product with others in front of them can help people who might not realise their drawbacks...

So an update. It turns out that all the issues were actually to do with Postiz rather than Authentic. - I tried installing a few other apps and linking them to Authentik but I ran into a few issues. Then I took Postiz and tried turning off the Atuthentik authentication and then just getting it to work with native user accounts. This initially didn't work - it turned out that there were a few issues.

  1. The startup procedure for Poztiz actually left the backend API service not running properly. I had to run the docker compose, get all the other services running and then stop the postiz container specifically wait a bit more and then restart just that container. That got the API service running.

  2. Because I was just running it internally I didn't have SSL certificates configured and was just using http - consequently I had to introduce NOT_SECURED: "true" into the environment section of the Postiz service in the compose file and then repeat the process above. This resolved a silent error in my browser where cookies used to manage the authenticated browser session were discarded because I wasn't using SSL.

So success at least getting Postiz running. I am now going to step back, reconfigure it for Authentic retry.

I am going to guess that these issues might be relevant if you are running Postiz behind a reverse proxy (I'm not sure if this is being done with the docker compose set-up). I possibly also need to look at how much memory and CPU I have on my test VM.

I've posted similar details in Postiz Discord. If anyone else is using #Postiz and would like to exchange notes - please do drop me a mention. Always good to have other people to talk to about these things and share notes.

@brewery Oh cheers. Yeah I think I need to test setting up another app to confirm whether its Authentik or Postiz. The other app I am looking at is an open source core banking system so I think I'll leave that one for a while and as you suggest try something more straight forward.

I'm keen to get Postiz working because I belong to a sailing club and its a time vacuum posting updates all over the place.

I'm interested do you you anything for social listening - I'd like to pull together a few social feeds from Twitter, Instal, Facebook and provide them to the few of us that are working on keeping the club's profile up.

@geoma I think its more that you can run it across multiple compute instances - and for multiple organisations. So its supporting the case where your compute requirements have grown beyond one vm (or you want redundancy ) and where you have multiple organisations that you want to support multiple independent instances of the same (or different) suite of applications.