https://www.europesays.com/2178535/ 16 Milliarden Zugangsdaten: Kein neuer Leak, viele alte Daten #alt #Cybernews #Dataleak #deutschland #Elasticsearch #germany #IT #Nachrichten #Remix #security
https://www.europesays.com/2178535/ 16 Milliarden Zugangsdaten: Kein neuer Leak, viele alte Daten #alt #Cybernews #Dataleak #deutschland #Elasticsearch #germany #IT #Nachrichten #Remix #security
@edzob Self-hosted, using Docker on a pi4. I've spun up #NextCloud, #Collabora and #ElasticSearch in #Docker, running behind #Traefik. I'm currently looking at SSO options like Authelia and Authentik, as I have a few other services I'd like to expose (a few Nginx sites, either Gitlab or Forgejo, Immich, etc)
One for the #Elastic / #Elasticsearch folks out there. Elastic are offering their on-demand training for free at the moment which I've just discovered also includes access to their labs. The training is pretty solid (I've done a few paid ones in the past) but the lab access makes it super valuable. I am working through one of the certs now (I need to complete a cert to renew two of my current ones) but it might be useful for other #tech folks out there
Elasticsearch Engineer - https://www.elastic.co/training/elasticsearch-engineer
Data Analysis with Kibana - https://www.elastic.co/training/data-analysis-with-kibana
Elastic Observability Engineer - https://www.elastic.co/training/elastic-observability-engineer
Elastic Security for SIEM - https://www.elastic.co/training/elastic-security-for-siem
OpenSearch 3.0 ist da und bringt mehr Leistung und Skalierbarkeit
Während der OpenSearchCon Europe wurde Version 3.0 des Such-Frameworks veröffentlicht. OpenSearch indexiert schneller und geht sparsamer mit Daten um.
I'm excited to share my new piece on #AI agents in #elasticsearch labs. It has been fun building my first AI agents using AI SDK, #typescript and #elasticsearch, and this piece is the output.
If you want to learn what AI agents are and how you can build your 1st one in Typescript check it out!
https://www.elastic.co/search-labs/blog/ai-agents-ai-sdk-elasticsearch
Code is below :
https://github.com/carlyrichmond/travel-planner-ai-agent
Enjoy!
#getFedihired - Know #MongoDB and/or #ElasticSearch and/or GNU/Linux #sysadm ? Expecially if you know #Ansible and/or #python and #shell scripting
A couple US or India #WFH positions opening up for 24/7 support ( includes #weekend and #holiday shifts )
US roles are US daytimes, India roles are the other 16 hours of day
DM me if you're interested ( job listings coming soon )
We should also have some SRE and dev positions and a MongoDB DBA position soon
Harness is hiring Staff Software Engineer - Software Engineering Insights
#java #aws #azure #cicd #docker #elasticsearch #gcp #mysql #postgresql #sql
Mountain View, California
Full-time
Harness
Job details https://jobsfordevelopers.com/jobs/staff-software-engineer-software-engineering-insights-at-harness-io-oct-15-2024-18620e?utm_source=mastodon.world&utm_medium=social&utm_campaign=posting
#jobalert #jobsearch #hiring
#linux
#python
#django
#wagtail
#elasticsearch
Anyone here silly enough to have tried using elasticsearch with django/wagtail?
Are you silly enough to have tried migrating from mapper-attachments to ingest-attachment?
Are you silly enough to help me with a question?
Day 1 of running my own #fediverse instance has come and gone and so far so good.
Having access to everything under the hood, it's interesting watching the gears turn and the software work. Most interesting for me is seeing how much space is eaten up by media files that get shared out.
Obviously I only have a single day to base things off but day 1 ate up around 16 GB of storage. Thankfully all my media is pointing to #linode object storage so at least the storage is cheap. But it was definitely interesting to see how much space gets eaten up.
So far the initial hurdles have been around tuning #elasticsearch so it continues indexing at a reasonable pace without eating the server alive, and around starting to establish maintenance jobs that I can schedule as crontabs so the server can stay afloat while my life continues to be the busy thing that it is.
I'd definitely take suggestions from folks who are either running their own instances or have done so in the past. I've got #postgresql backups automated (both the creation and cleanup of) with PgAgent. Also running "rake mastodon:media:clear" as a nightly cronjob to periodically remove uploads that have not been attached to any status after a while, but that's kind of it.
While it's not at all my first rodeo with the care and feeding of a server, it is indeed my first rodeo running my own Mastodon instance so I'd happily take any articles folks have that they found helpful or just general advice if you have time to share.
Rolled out #Elasticsearch on https://Earth.Law today. If you're looking for a home on the #fediverse with robust #search capabilities, you can now search through post content, bookmarks, and historical discussions here with better accuracy and speed.
A small #Mastodon Instance focused on #EnvironmentalLaw, #ClimatePolicy, and related discourse.
New in the November 2024 issue: Joe Casad discusses when open source projects maintained by for-profit entities fall off the open source wagon
https://www.linux-magazine.com/Issues/2024/288/Welcome
#OpenSource #project #FOSS #MongoDB #Elasticsearch #Terraform #Confluent #Redmonk
what is the easiest way to run #elasticsearch and #kibana?
curl -fsSL https://elastic.co/start-local | sh
and this is what it looks like:
Elasticsearch is going back to the #AGPL open-source #license. They are saying that they can do that now because "market confusion" around Amazon's #Elasticsearch fork has gone away, but no details.
Anybody know details?
https://www.elastic.co/blog/elasticsearch-is-open-source-again
TL;DR #ElasticSearch is now triple-licensed. ELv2 [1], SSPL [2] and AGPLv3 [3]. So you need to sign a CLA (contributor license agreement), which unfortunately isn't publicly available, AFAICS [4]
(also also, they haven't yet updated the LICENSE.txt in their Github repo [5]. Read their announcement at [6] )
[1] https://www.elastic.co/licensing/elastic-license
[2] https://www.mongodb.com/legal/licensing/server-side-public-license
[3] https://www.gnu.org/licenses/agpl-3.0.en.html
[4] https://www.elastic.co/contributor-agreement
[5] https://github.com/elastic/elasticsearch/blob/main/LICENSE.txt
[6] https://www.elastic.co/blog/elasticsearch-is-open-source-again
I'm looking at alternatives for setting up #Opensearch for my Mastodon instance. Currently use #ElasticSearch on the same server & it's bogging me down
I either can spin something up on a new VPS or get a hosted solution
The pricing isn't clicking with me. For example, AWS bills by the hour
Anyone have experience with this? #MastoAdmin
Trying to figure out what it will cost me
self-hosted, use relays
Minimum CPU and memory for just me. Also, I use search a lot
current ES stats below.
Through the normal course of using Elasticsearch with Mastodon, within the bounds of the guidelines and trust,(https://docs.joinmastodon.org/admin/elasticsearch/) my current #ElasticSearch stats for my essentially single-user Mastodon instance right now are, saved 4.5 million public statuses, from 22K instances, 488K accounts and many, many tags.
What's your ES stats? #MastoAdmin
Selfhosted instance.
I am thinking of breaking #Postgres and #ElasticSearch to a separate server instead of increasing my current VPS resources.
I'll have two servers. My main, which will run Mastodon, and another that will have Postgres and ElasticSearch on it.
Will I benefit by doing this or should I just move ElasticSearch to its own server? What is the minimum CPU/ram I can get for the second server & what should I get?
Or, other thoughts welcomed.
#MastoAdmin
I've been an advocate for federated Flipboard.
Search for ActivityPub lately? It's all Flibboard posts, unrelated to ActivityPub on my #ElasticSearch enabled Mastodon instance.
Flipboard adds "utm_medium=activitypub" so any search for activitypub returns only Flipboard posts
The #ActivityPub hashtag works ok but plain text search is corrupted by their UTM. #search
Unless you #selfhost your own #mastodon instance, or you're a #mastoAdmin, you have likely taken #fullTextSearch for granted.
Behind search for masto is a resource-hungry #java application called #elasticSearch. Sure you might be able to get Masto to run on a #raspberrypi4, but you won't be running elastic search with it.
Having recently moved my instance to a much more powerful system, I now run ES, and WOW what a difference being able to search post makes! Soooo many times I wanted to reference a toot that had scrolled by but had no way of finding it. Now I do!
Even though I've put some serious resource limits on ES, it's bar none the most resource intensive service running (out of around 25).
Please consider sending a few bucks to the #MastodonAdmin of your instance. Better yet, if you can afford it, sign up for a monthly donation. They need it.