abeorch

@ abeorch @friendica.ginestes.es

Posts

19
Comments

212
Joined

2 yr. ago

2mo ago

[META] Are paid for, closed source projects, being advertised on this community, appropriate?
Jump
abeorch @friendica.ginestes.es 2mo ago
@breadsmasher I know there is that joke about online forums and the probablity of someone getting called a nazi heading toward one overtime - this is a sensitive topic but im less concerned about an occasional shill for a persons product than people getting rude and abusive to each other.. theres nothing worth that in this discussion..

2mo ago

[META] Are paid for, closed source projects, being advertised on this community, appropriate?

@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.

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.
Because I was just running it internally I didn't have SSL certificates configured and was just using http - consequently I had to introduce NOTSECURED: "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.