These are public posts tagged with #dokuwiki. You can interact with them if you have an account anywhere in the fediverse.
Почему-то я не могу выбрать для себя инструменты и пользоваться ими.
Всё никак не могу выбрать инструмент для ведения своей knowledge base.
Сейчас использую #DokuWiki + #Logseq.
Но Logseq мне не нравится тем, что он на #Electron, а DokuWiki я почему-то решил вести на английском.
Вот и вчера весь вечер смотрел ролики про #OrgRoam. Хочу теперь туда переехать. Там можно и вики вести и дневничок писать. Вот только картинки не будет отображать, но не знаю нужны ли они мне.
Весь в раздумьях теперь...
@haraldgeyer @econetwork Not sure what about #dokuwiki . It seems to have an android version although its only in the beta. Haven't tried it yet.
https://play.google.com/store/apps/details?id=com.fabienli.dokuwiki&hl=de&pli=1
@splitbrain
Currently not looking for a comment system for my #dokuwiki installations, but I really like the name and the concept
Seit ich mein #Dokuwiki durch #QownNotes ersetzt habe ist meine Motivation Posts zu schreiben deutlich angestiegen. QownNotes macht es einen sehr leicht schnell mal einen Artikel zu erstellen.
Open source Markdown note taking for Linux, macOS and…
QOwnNotesLast weekend the Open Film Database (https://ofdb.cc) received another update, which included the migration from #WordPress (Blog) and #DokuWiki (Wiki) to #Drupal, front-end improvements for TV shows, improved cast editing, and more!
The #OFDb is a database for movies and TV shows with its data published under an open license (Open Database License). Everyone can participate and add more titles. The more the merrier!
Do you rely on DokuWiki and its plugins at your company?
There is now an easy way to contribute to the ongoing maintenance of the most important plugins and the overall DokuWiki ecosystem in general.
Read CosmoCode's announcement of their DokuWiki Business Plugin Partner Program at our forum:
https://forum.dokuwiki.org/d/22816-announcing-the-dokuwiki-business-plugin-partner-program
Community Discussions, Questions and Answers for the…
forum.dokuwiki.orgLooking for #patterns and #BestPractices of #UX for #interactive #climate change #education, #information and #inspiration.
#DokuWiki #infokiosk #SPInKa #TePeWu #ui #ux #help needed!
So, we are signing an agreement with city of #Gliwice, to set up a "#climate #infoshop" there (codename SPInKa).
We plan to start with an automated infokiosk, placed in public space for everyone to use.
Tech-wise it will be an old laptop with one or two displays (one touchscreen), running a browser in kiosk mode, serving local (federated) instance of dokuwiki (tentatively selected). It will be a prototype for the wholw network, all free and open licences ofc.
Now, we are looking for someone to help us create a front/template for such a kiosk, plus somoeonw to coordinate the "user experience" design.
If you are such person, please let us know. If you know one, let them know.
More details in this thread soon.
Here goes a shoutout to our friends from Climate Emergency…
szmer.infoHi #SelfHosted community. I've figured out a lot of my setup. I now have a new domain, laniesplace.us, just for #HomeServer stuff. It's set up through Porkbun with Dynu for #DDNS. I've now got #Traefik, #TailscaleVPN, #Linkding, #Forgejo, #Dokuwiki, Code-Server, #Portainer, #Netdata, #Watchtower, #Cockpit, #Pihole, #MiniFlux, #TheLounge, #Filebrowser, #UptimeKuma, and the #Homer dashboard service installed. I'm now trying to set up #Authelia so I can have single sign-on to my services. For some, it's working now, but I can't seem to get Linkding to work no matter what I do. This is on a #RaspberryPi 500 with 8 GB RAM and a 512 GB SD card, running #Stormux, which is based on #ArchlinuxARM. Can anyone help? I'll reply to this post with all my relevant config files in separate posts. What's happening is this: Linkding is supposed to be available at bookmarks.laniesplace.us. When I go there, I see a 401 unauthorized error and a link to sign into Authelia. Once I sign in, though, it redirects back to the page with the 401 error. I've been trying to figure this out for hours with no luck. Files will be in replies to this post.
#SelfHosting #Linux #HomeLab #RPi #RaspberryPi500 #RPi500
@selfhost @selfhosting @selfhosted @linux
Сегодня поставил #Navidrome на сервер. Теперь буду слушать музычку с него в браузере или в #Strawberry через #Subsonic API (ещё не пробовал).
Так же поставил #Gollum wiki вместо #Dokuwiki, т.к. это единственный известный мне вики движок который умеет работать с #org файлами. А мне сильно захотелось переехать на #orgmode раз я теперь #Emacs пользователь.
Dear friends of the BSD Cafe,
As 2024 comes to an end, it’s time to reflect on what we’ve built together during the first full year of life for BSD Cafe. Launched on 20 July 2023, this project has grown far beyond what I could have imagined. While I haven’t tracked full uptime data, I can confidently say that the downtime was less than 30 minutes overall - even though the main VM hosting our services moved multiple times (including a switch from a Proxmox hypervisor to bhyve on FreeBSD, for the sake of alignment with our mission). In a world filled with over-engineered HA systems, we’ve outperformed many “big-name” cloud providers. Not bad for a community project, right?
For me, this has been an incredible journey. The users here are not just participants - they’re collaborators, and their positivity has been inspiring. The content shared and created at BSD Cafe has been valuable not only to the BSD community but beyond. What truly sets BSD Cafe apart is the openness for dialogue and exchange. Whether it’s social media posts, Matrix discussions, repositories in our brew, or RSS feeds, people seem to genuinely appreciate what we create and the conversations we foster.
BSD Cafe is a journey - one that grows, evolves, and continues. Our goal isn’t endless growth (we’re a community, not a business) but rather to maintain a welcoming, inclusive space where everyone feels a sense of positivity and belonging. For me, opening any service with “bsd.cafe” in the domain brings joy and pride. That’s the spirit I’ve tried to convey, and I hope it resonates with all of you, whether you’re active BSD Cafe users or friends of the community.
Promoting self-hosting and #OwnYourData has, as a side effect, inspired some users to “go solo” with their own setups. But even then, they remain part of BSD Cafe - in spirit, in purpose, and in connection.
Here’s a look at what we’ve achieved together this year:
- mastodon.bsd.cafe: 370 total users
Active in the past month: 207
Active in the past six months: 286
- snac.bsd.cafe: 14 total users
Active in the past month: 7
- blendit.bsd.cafe: 61 registered users
- matrix.bsd.cafe: 23 users
- brew.bsd.cafe: 29 users - 80 repositories
- freshrss.bsd.cafe: 25 users
- miniflux.bsd.cafe: 11 users
- press.bsd.cafe: 9 users
- myip.bsd.cafe: Constantly used by various users
- wiki.bsd.cafe: Could use a bit more love and content, but it fulfills its role as a functional homepage.
- tube.bsd.cafe: Still in testing - Peertube 7.0 update is on the way.
For detailed stats from our reverse proxy and general router (excluding media services, which generate most traffic but are handled via caching reverse proxies), you can check here - updated hourly: https://netstats.bsd.cafe
The journey of BSD Cafe continues, and I look forward to seeing where 2025 will take us. Together, we’ve built something special - something driven by passion, shared purpose, and a little bit of the BSD magic that makes all of this possible.
Here’s to a new year full of joy, serenity, and connection. Thank you for being part of this adventure.
Wishing you all a fantastic 2025 - and THANK YOU!
Stefano
#BSDCafe #BSDCafeServices #BSDCafeAnnouncements #BSDCafeUpdates #Fediverse #HappyNewYear #Mastodon #Snac #snac2 #lemmy #matrix #dokuwiki #forgejo #freshrss #miniflux #wallabag #peertube #FreeBSD #OpenBSD #NetBSD #RunBSD #BSD
Which #wiki #farm? We have a #Debian #VPS, where, among others, we wish to have a wiki farm to provide platforms for our various projects, internal and external.
The short list is:
- #Xwiki, with its native farming system, high modularity and and groupware flavour.
- #DokuWiki which is simpler and has a dedicated Farmer plugin.
I am looking for some insight from maintainer/developer perspective, as we will need a lot of customisation, automated workflow, export/import and other bells and whistles. Also, resource intensity?
Please kindly flood me with your opinions.
Long post
FTR: Why the .phtml extension, you ask?
The idea (if you check the "old" version), the only files which are NOT loaded in the iFrame, are the .php files.
this allows for a DokuWiki type (hardly!) convenience sort of, using that template.phtml file i suppose
#dokuwiki
@goodthinkhunting klingt so als bräuchtest du ein PKM :) Ich persönlich hab für die Fam ein #DokuWiki aufgesetzt (wo z.B. alle Verträge, Anleitungen, Wohnungs-Stuff, Geschenkideen usw. gesammelt werden), auf Arbeit benutze ich #Logseq (ohne Sync) und für mein persönliches Zeug #vimwiki (siehe Screenshot), wenn du ein Cross-device Sync (gegen $$) brauchst kannst du dir auch mal #Obsidian angucken.